BasisOfRecord,,Brad: OMIT? See http://rs.tdwg.org/dwc/terms/index.htm#basisOfRecord for definition of this term.

CatalogNumber,,"Brad: Not sure if mapping correct. Nick, is there an element for institutional accession codes in VegX?; Aaron: This can't be used as the accession code (primary key) because some rows don't have a value for it"

ContinentOcean,,Brad: OMIT

DateLastModified,,"Brad: Mapping to VegX is incorrect. I think is this merely an internal timestamp indicated when record last modified, not necessarily when determination (taxon name) last modified. Probably we should omit this field, although might be useful for updating changed records from this source."

IndividualCount,,Brad: OMIT; not relevant for DwC plant specimen data.

JulianDay,,Brad: OMIT

PreparationType,,Brad: OMIT

PreviousCatalogNumber,,Brad: OMIT

RelatedCatalogItem,,Brad: OMIT

RelationshipType,,Brad: OMIT

TimeOfDay,,Brad: OMIT

TypeStatus,,Brad: OMIT (?). Indicates whether this specimen served as type for taxon name. Probably not relevant for BIEN

key,,Brad: OMIT; I'm pretty sure this is a temporary artificial ID generated at time of export.

origrecord_id_stems,,

stem_id,,

tmp_del,,

AccessCode,,

ElevSource,,

Habitat,,

MethodCode,,

PrecipSource,,

PrimOwnerID,,

RevisionComments,,

SiteName,,

TempSource,,

bearing,,

lat_long_accuracy,,

lat_string,,

long_string,,

new_world,,

orig_filename,,

plot_administrator,,

plot_notes,,

pol1_type,,

pol2_type,,

recensused,,"Brad: This is a 0/1 value, internal to SALVIAS. 1 indicates that a  plot has >1 set of values, from different census events.; Aaron: Different censuses are distinguished in organisms data by different census_no values"

tmp_del,,

topography_desc,,

vegetation_1,,

vegetation_2,,

PlotID,/*_id/locationevent/authoreventcode,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."

height_m,/aggregateoccurrence/*_id/plantobservation/overallheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob

tag2,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode/_alt/1,"Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."

tag1,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode/_alt/2,"Brad: Another type of code, typically a number, used by the original data provider to indicate an individual tree. These are numbers on physical tags attached to the tree. Tag2 Is the same thing, only used if the first tag was lost. Obviously not a good system as it's possible a tree tag could be lost and changed more than once."

ht_first_branch_m,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=heightFirstBranchM]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob

temp_dbh,/aggregateoccurrence/*_id/plantobservation/stemobservation/diameter,

x_position,/aggregateoccurrence/*_id/plantobservation/stemobservation/xposition,"Brad: Correct for VegBank. I'm not so sure for VegX. Let's ask Nick about this. These are important, fundamental values of many tree plots, and should be accommodated within VegX."

y_position,/aggregateoccurrence/*_id/plantobservation/stemobservation/yposition,Brad: See comment above for x_position

NoInd,/aggregateoccurrence/count,"Brad: Incorrect for VegX. This is a count of number of indiiduals for an *aggregate* observation. For VegBank, I'm not sure. Not exactly the same as stemCount. An individual tree could have 3 stems but would still only count as 1. We need to check with Bob on this."

cover_percent,/aggregateoccurrence/cover,

intercept_cm,"/aggregateoccurrence/definedvalue[*_id/userdefined[tablename=aggregateoccurrence,userdefinedname=interceptCm]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Incorrect for VegBank This is an aggregate observation. Used in line-intercept methodology only, describes the point along centerline at which an individual intercepts the center line of the plot. Used to determin relative abundance."

census_no,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=censusNo]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Assigned by SALVIAS. 1 for first plot, then 2, 3, etc. I can't recall if we even have repeat censuses in SALVIAS. Probably not."

Habit,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=habit]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Incorrect for VegBank, correct for VegX. This is growth form (tree, shrub, herb, etc.). It is an observation of a trait."

Ind,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=individualCode]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Code, if any, used by the data provider to indicate an individual tree. Scope is unknown, although typically this value is unique only within plot, or sometimes only within subplot."

DetType,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=voucherType]]:[@fkey=tableRecord_ID]/definedvalue","Brad: A SALVIAS value referring to the relationship between the voucher specimen and the observation. Affect how the identification of the specimen(latin name) is transferred to the observation. 'direct'=voucher specimen was collected from this same tree; they are one and the same individual. 'indirect'=voucher specimen was collected for a different individual, but the original data provider confirmed that this is the same species. 'default'=basically same as 'indirect'. 'uncollected'=no voucher specimen, data provider  asserted that this was the name but was unable to collect. The main different is that with 'direct', 'indirect', and 'default', the scientific name can be updated automatically based on the name attached to the specimen voucher (assuming you have a link to that data, presumably from a herbarium database. Whereas, if det_type='uncollected', the name can never change because there is no specimen."

coll_number,/specimenreplicate:[*_id/reference]/catalognumber_dwc,Brad: Incorrect. Map instead as for voucher_string

census_date,/specimenreplicate:[*_id/reference]/collectiondate/_*/date,

coll_firstname,/specimenreplicate:[*_id/reference]/verbatimcollectorname/_name/first,Brad: See comment above

coll_lastname,/specimenreplicate:[*_id/reference]/verbatimcollectorname/_name/last,"Brad: Correct for VegBank. This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick."

auth,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Authority]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",Brad: Incorrect. This is the author of the scientificName. The should be a place for this in the taxonomic name elements of VegB and VegX. Let's discuss.

Family,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Family]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",

Genus,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Genus]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",

Species,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Species]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",

infra_rank_1,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Subspecies]/*_id/plantconcept/_name/first",

infra_ep_1,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Subspecies]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/_name/last",

cfaff,"/taxondetermination[*_id/role/rolecode=identifier,!*_id/plantconcept]/definedvalue[*_id/userdefined[tablename=taxondetermination,userdefinedname=cfAff]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Not sure where this goes. Indicator of identification uncertainty. 'cf.'=similar to the species listed, 'aff.'=related to the species list, but not the same. You'll need to check with Bob and with Nick where these go in VegX and VegBank."

Notes,"/taxondetermination[*_id/role/rolecode=identifier,!*_id/plantconcept]:[determinationtype=Author,iscurrent=true]/notes",

OrigFamily,"/taxondetermination[*_id/role/rolecode=identifier,*_id/plantconcept/plantstatus/plantlevel=Family]:[determinationtype=Author,isoriginal=true,iscurrent=true]/*_id/plantconcept/*_id/*/plantname",Brad: OMIT

OrigSpecies,"/taxondetermination[*_id/role/rolecode=identifier,*_id/plantconcept/plantstatus/plantlevel=Species]:[determinationtype=Author,isoriginal=true,iscurrent=true]/*_id/plantconcept/*_id/*/plantname",Brad: OMIT

PlotObsID,"/{aggregateoccurrence/*_id/plantobservation/authorplantcode,specimenreplicate:[*_id/reference]/sourceaccessioncode}","Brad: Neither is correct; this is just an internal ID for table plotObservations. However, it has the important property of uniquely identifying an ""observation"", which is an individual tree, in the case of an individual observation, or a records of a species with an associated count of individuals or measurement of percent cover, in the case of aggregate observations. Not sure where to store this. Main point is that it is not part of the original data, but an auto_increment added later."

def cmp_nulls_last(*row_pair):

    def repl(val):

        if val == '': val = () # sorts > ''

        return val

    return cmp(*map(lambda row: map(repl, row), row_pair))

    rows.sort(lambda *row_pair: cmp_nulls_last(*map(get_sort_by, row_pair)))

PlotID,/*_id/locationevent/authoreventcode,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."

height_m,/aggregateoccurrence/*_id/plantobservation/overallheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob

tag2,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode/_alt/1,"Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."

tag1,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode/_alt/2,"Brad: Another type of code, typically a number, used by the original data provider to indicate an individual tree. These are numbers on physical tags attached to the tree. Tag2 Is the same thing, only used if the first tag was lost. Obviously not a good system as it's possible a tree tag could be lost and changed more than once."

ht_first_branch_m,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=heightFirstBranchM]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob

temp_dbh,/aggregateoccurrence/*_id/plantobservation/stemobservation/diameter,

x_position,/aggregateoccurrence/*_id/plantobservation/stemobservation/xposition,"Brad: Correct for VegBank. I'm not so sure for VegX. Let's ask Nick about this. These are important, fundamental values of many tree plots, and should be accommodated within VegX."

y_position,/aggregateoccurrence/*_id/plantobservation/stemobservation/yposition,Brad: See comment above for x_position

NoInd,/aggregateoccurrence/count,"Brad: Incorrect for VegX. This is a count of number of indiiduals for an *aggregate* observation. For VegBank, I'm not sure. Not exactly the same as stemCount. An individual tree could have 3 stems but would still only count as 1. We need to check with Bob on this."

cover_percent,/aggregateoccurrence/cover,

intercept_cm,"/aggregateoccurrence/definedvalue[*_id/userdefined[tablename=aggregateoccurrence,userdefinedname=interceptCm]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Incorrect for VegBank This is an aggregate observation. Used in line-intercept methodology only, describes the point along centerline at which an individual intercepts the center line of the plot. Used to determin relative abundance."

census_no,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=censusNo]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Assigned by SALVIAS. 1 for first plot, then 2, 3, etc. I can't recall if we even have repeat censuses in SALVIAS. Probably not."

Habit,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=habit]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Incorrect for VegBank, correct for VegX. This is growth form (tree, shrub, herb, etc.). It is an observation of a trait."

Ind,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=individualCode]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Code, if any, used by the data provider to indicate an individual tree. Scope is unknown, although typically this value is unique only within plot, or sometimes only within subplot."

DetType,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=voucherType]]:[@fkey=tableRecord_ID]/definedvalue","Brad: A SALVIAS value referring to the relationship between the voucher specimen and the observation. Affect how the identification of the specimen(latin name) is transferred to the observation. 'direct'=voucher specimen was collected from this same tree; they are one and the same individual. 'indirect'=voucher specimen was collected for a different individual, but the original data provider confirmed that this is the same species. 'default'=basically same as 'indirect'. 'uncollected'=no voucher specimen, data provider  asserted that this was the name but was unable to collect. The main different is that with 'direct', 'indirect', and 'default', the scientific name can be updated automatically based on the name attached to the specimen voucher (assuming you have a link to that data, presumably from a herbarium database. Whereas, if det_type='uncollected', the name can never change because there is no specimen."

coll_number,/specimenreplicate:[*_id/reference]/catalognumber_dwc,Brad: Incorrect. Map instead as for voucher_string

census_date,/specimenreplicate:[*_id/reference]/collectiondate/_*/date,

coll_firstname,/specimenreplicate:[*_id/reference]/verbatimcollectorname/_name/first,Brad: See comment above

coll_lastname,/specimenreplicate:[*_id/reference]/verbatimcollectorname/_name/last,"Brad: Correct for VegBank. This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick."

auth,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Authority]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",Brad: Incorrect. This is the author of the scientificName. The should be a place for this in the taxonomic name elements of VegB and VegX. Let's discuss.

Family,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Family]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",

Genus,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Genus]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",

Species,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Species]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/*_id/*/plantname",

infra_rank_1,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Subspecies]/*_id/plantconcept/_name/first",

infra_ep_1,"/taxondetermination[*_id/role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Subspecies]:[determinationtype=""Computer (automated)"",iscurrent=true]/*_id/plantconcept/_name/last",

cfaff,"/taxondetermination[*_id/role/rolecode=identifier,!*_id/plantconcept]/definedvalue[*_id/userdefined[tablename=taxondetermination,userdefinedname=cfAff]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Not sure where this goes. Indicator of identification uncertainty. 'cf.'=similar to the species listed, 'aff.'=related to the species list, but not the same. You'll need to check with Bob and with Nick where these go in VegX and VegBank."

Notes,"/taxondetermination[*_id/role/rolecode=identifier,!*_id/plantconcept]:[determinationtype=Author,iscurrent=true]/notes",

OrigFamily,"/taxondetermination[*_id/role/rolecode=identifier,*_id/plantconcept/plantstatus/plantlevel=Family]:[determinationtype=Author,isoriginal=true,iscurrent=true]/*_id/plantconcept/*_id/*/plantname",Brad: OMIT

OrigSpecies,"/taxondetermination[*_id/role/rolecode=identifier,*_id/plantconcept/plantstatus/plantlevel=Species]:[determinationtype=Author,isoriginal=true,iscurrent=true]/*_id/plantconcept/*_id/*/plantname",Brad: OMIT

PlotObsID,"/{aggregateoccurrence/*_id/plantobservation/authorplantcode,specimenreplicate:[*_id/reference]/sourceaccessioncode}","Brad: Neither is correct; this is just an internal ID for table plotObservations. However, it has the important property of uniquely identifying an ""observation"", which is an individual tree, in the case of an individual observation, or a records of a species with an associated count of individuals or measurement of percent cover, in the case of aggregate observations. Not sure where to store this. Main point is that it is not part of the original data, but an auto_increment added later."

PlotID,//locationevent/authoreventcode,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."

height_m,//plantobservation/overallheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob

tag2,//stemobservation/authorstemcode/_alt/1,"Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."

tag1,//stemobservation/authorstemcode/_alt/2,"Brad: Another type of code, typically a number, used by the original data provider to indicate an individual tree. These are numbers on physical tags attached to the tree. Tag2 Is the same thing, only used if the first tag was lost. Obviously not a good system as it's possible a tree tag could be lost and changed more than once."

ht_first_branch_m,"//stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=heightFirstBranchM]]/definedvalue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob

temp_dbh,//stemobservation/diameter,

x_position,//stemobservation/xposition,"Brad: Correct for VegBank. I'm not so sure for VegX. Let's ask Nick about this. These are important, fundamental values of many tree plots, and should be accommodated within VegX."

y_position,//stemobservation/yposition,Brad: See comment above for x_position

NoInd,//aggregateoccurrence/count,"Brad: Incorrect for VegX. This is a count of number of indiiduals for an *aggregate* observation. For VegBank, I'm not sure. Not exactly the same as stemCount. An individual tree could have 3 stems but would still only count as 1. We need to check with Bob on this."

cover_percent,//aggregateoccurrence/cover,

intercept_cm,"//aggregateoccurrence/definedvalue[*_id/userdefined[tablename=aggregateoccurrence,userdefinedname=interceptCm]]/definedvalue","Brad: Incorrect for VegBank This is an aggregate observation. Used in line-intercept methodology only, describes the point along centerline at which an individual intercepts the center line of the plot. Used to determin relative abundance."

census_no,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=censusNo]]/definedvalue","Brad: Assigned by SALVIAS. 1 for first plot, then 2, 3, etc. I can't recall if we even have repeat censuses in SALVIAS. Probably not."

Habit,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=habit]]/definedvalue","Brad: Incorrect for VegBank, correct for VegX. This is growth form (tree, shrub, herb, etc.). It is an observation of a trait."

Ind,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=individualCode]]/definedvalue","Brad: Code, if any, used by the data provider to indicate an individual tree. Scope is unknown, although typically this value is unique only within plot, or sometimes only within subplot."

DetType,"/definedvalue[*_id/userdefined[tablename=taxonoccurrence,userdefinedname=voucherType]]/definedvalue","Brad: A SALVIAS value referring to the relationship between the voucher specimen and the observation. Affect how the identification of the specimen(latin name) is transferred to the observation. 'direct'=voucher specimen was collected from this same tree; they are one and the same individual. 'indirect'=voucher specimen was collected for a different individual, but the original data provider confirmed that this is the same species. 'default'=basically same as 'indirect'. 'uncollected'=no voucher specimen, data provider  asserted that this was the name but was unable to collect. The main different is that with 'direct', 'indirect', and 'default', the scientific name can be updated automatically based on the name attached to the specimen voucher (assuming you have a link to that data, presumably from a herbarium database. Whereas, if det_type='uncollected', the name can never change because there is no specimen."

coll_number,//specimenreplicate/catalognumber_dwc,Brad: Incorrect. Map instead as for voucher_string

census_date,//specimenreplicate/collectiondate/_*/date,

coll_firstname,//specimenreplicate/verbatimcollectorname/_name/first,Brad: See comment above

coll_lastname,//specimenreplicate/verbatimcollectorname/_name/last,"Brad: Correct for VegBank. This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick."

auth,"/taxondetermination[rolecode=computer,plantlevel=Authority]/*_id/plantconcept/*_id/*/plantname",Brad: Incorrect. This is the author of the scientificName. The should be a place for this in the taxonomic name elements of VegB and VegX. Let's discuss.

Family,"/taxondetermination[rolecode=computer,plantlevel=Family]/*_id/plantconcept/*_id/*/plantname",

Genus,"/taxondetermination[rolecode=computer,plantlevel=Genus]/*_id/plantconcept/*_id/*/plantname",

Species,"/taxondetermination[rolecode=computer,plantlevel=Species]/*_id/plantconcept/*_id/*/plantname",

infra_rank_1,"/taxondetermination[rolecode=computer,plantlevel=Subspecies]/*_id/plantconcept/_name/first",

infra_ep_1,"/taxondetermination[rolecode=computer,plantlevel=Subspecies]/*_id/plantconcept/_name/last",

cfaff,"/taxondetermination[rolecode=identifier]/definedvalue[*_id/userdefined[tablename=taxondetermination,userdefinedname=cfAff]]/definedvalue","Brad: Not sure where this goes. Indicator of identification uncertainty. 'cf.'=similar to the species listed, 'aff.'=related to the species list, but not the same. You'll need to check with Bob and with Nick where these go in VegX and VegBank."

Notes,/taxondetermination[rolecode=identifier]/notes,

OrigFamily,"/taxondetermination[rolecode=identifier,plantlevel=Family]/*_id/plantconcept/*_id/*/plantname",Brad: OMIT

OrigSpecies,"/taxondetermination[rolecode=identifier,plantlevel=Species]/*_id/plantconcept/*_id/*/plantname",Brad: OMIT

PlotObsID,"/{aggregateoccurrence/*_id/plantobservation/authorplantcode,specimenreplicate/sourceaccessioncode}","Brad: Neither is correct; this is just an internal ID for table plotObservations. However, it has the important property of uniquely identifying an ""observation"", which is an individual tree, in the case of an individual observation, or a records of a species with an associated count of individuals or measurement of percent cover, in the case of aggregate observations. Not sure where to store this. Main point is that it is not part of the original data, but an auto_increment added later."

BasisOfRecord,,Brad: OMIT? See http://rs.tdwg.org/dwc/terms/index.htm#basisOfRecord for definition of this term.

CatalogNumber,,"Brad: Not sure if mapping correct. Nick, is there an element for institutional accession codes in VegX?; Aaron: This can't be used as the accession code (primary key) because some rows don't have a value for it"

ContinentOcean,,Brad: OMIT

DateLastModified,,"Brad: Mapping to VegX is incorrect. I think is this merely an internal timestamp indicated when record last modified, not necessarily when determination (taxon name) last modified. Probably we should omit this field, although might be useful for updating changed records from this source."

IndividualCount,,Brad: OMIT; not relevant for DwC plant specimen data.

JulianDay,,Brad: OMIT

PreparationType,,Brad: OMIT

PreviousCatalogNumber,,Brad: OMIT

RelatedCatalogItem,,Brad: OMIT

RelationshipType,,Brad: OMIT

TimeOfDay,,Brad: OMIT

TypeStatus,,Brad: OMIT (?). Indicates whether this specimen served as type for taxon name. Probably not relevant for BIEN

key,,Brad: OMIT; I'm pretty sure this is a temporary artificial ID generated at time of export.

PLOT_ID,,"Brad: This is artificial internal database ID; a unique identifier within SALVIAS DB to each plot, within the table plotMetadata."

holdridge_life_zone,,

life_zone_code,,

observation_type,,"Brad: SALVIAS internal metadata indicating whether the record represents an individual or aggregate observation. Rather than storing, use to decide where to store in VegX.; Aaron: VegX aggregateOrganismObservation table is missing many fields available in individualOrganismObservation, so we're mapping to individualOrganismObservation regardless of observation type"

recensused,,"Brad: This is a 0/1 value, internal to SALVIAS. 1 indicates that a  plot has >1 set of values, from different census events.; Aaron: Different censuses are distinguished in organisms data by different census_no values"

PLOT_ID,,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."

collector_code,,Brad: OMIT

comments,,Brad: OMIT

fam_status,,Brad: OMIT. This will be determined later by using TNRS.

gen_status,,Brad: OMIT. This will be determined later by using TNRS.

ind_id,,Brad: OMIT

species_status,,"Brad: OMIT. Except, note that if species_status=3, this indicate that name is a morphospecies and not a standard latin name. Not exactly sure how to use this in BIEN, but could be useful during the name-scrubbing process with TNRS."

voucher_string,,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."

AccessCode,,

ElevSource,,

Habitat,,

MethodCode,,

PrecipSource,,

PrimOwnerID,,

RevisionComments,,

SiteName,,

TempSource,,

bearing,,

lat_long_accuracy,,

lat_string,,

long_string,,

new_world,,

orig_filename,,

plot_administrator,,

plot_notes,,

pol1_type,,

pol2_type,,

recensused,,"Brad: This is a 0/1 value, internal to SALVIAS. 1 indicates that a  plot has >1 set of values, from different census events.; Aaron: Different censuses are distinguished in organisms data by different census_no values"

tmp_del,,

topography_desc,,

vegetation_1,,

vegetation_2,,

BasisOfRecord,,Brad: OMIT? See http://rs.tdwg.org/dwc/terms/index.htm#basisOfRecord for definition of this term.

CatalogNumber,,"Brad: Not sure if mapping correct. Nick, is there an element for institutional accession codes in VegX?; Aaron: This can't be used as the accession code (primary key) because some rows don't have a value for it"

ContinentOcean,,Brad: OMIT

DateLastModified,,"Brad: Mapping to VegX is incorrect. I think is this merely an internal timestamp indicated when record last modified, not necessarily when determination (taxon name) last modified. Probably we should omit this field, although might be useful for updating changed records from this source."

IndividualCount,,Brad: OMIT; not relevant for DwC plant specimen data.

JulianDay,,Brad: OMIT

PreparationType,,Brad: OMIT

PreviousCatalogNumber,,Brad: OMIT

RelatedCatalogItem,,Brad: OMIT

RelationshipType,,Brad: OMIT

TimeOfDay,,Brad: OMIT

TypeStatus,,Brad: OMIT (?). Indicates whether this specimen served as type for taxon name. Probably not relevant for BIEN

key,,Brad: OMIT; I'm pretty sure this is a temporary artificial ID generated at time of export.

PLOT_ID,,"Brad: This is artificial internal database ID; a unique identifier within SALVIAS DB to each plot, within the table plotMetadata."

holdridge_life_zone,,

life_zone_code,,

observation_type,,"Brad: SALVIAS internal metadata indicating whether the record represents an individual or aggregate observation. Rather than storing, use to decide where to store in VegX.; Aaron: VegX aggregateOrganismObservation table is missing many fields available in individualOrganismObservation, so we're mapping to individualOrganismObservation regardless of observation type"

recensused,,"Brad: This is a 0/1 value, internal to SALVIAS. 1 indicates that a  plot has >1 set of values, from different census events.; Aaron: Different censuses are distinguished in organisms data by different census_no values"

PLOT_ID,,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."

collector_code,,Brad: OMIT

comments,,Brad: OMIT

fam_status,,Brad: OMIT. This will be determined later by using TNRS.

gen_status,,Brad: OMIT. This will be determined later by using TNRS.

ind_id,,Brad: OMIT

species_status,,"Brad: OMIT. Except, note that if species_status=3, this indicate that name is a morphospecies and not a standard latin name. Not exactly sure how to use this in BIEN, but could be useful during the name-scrubbing process with TNRS."

voucher_string,,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."

AccessCode,,

ElevSource,,

Habitat,,

MethodCode,,

PrecipSource,,

PrimOwnerID,,

RevisionComments,,

SiteName,,

TempSource,,

bearing,,

lat_long_accuracy,,

lat_string,,

long_string,,

new_world,,

orig_filename,,

plot_administrator,,

plot_notes,,

pol1_type,,

pol2_type,,

recensused,,"Brad: This is a 0/1 value, internal to SALVIAS. 1 indicates that a  plot has >1 set of values, from different census events.; Aaron: Different censuses are distinguished in organisms data by different census_no values"

tmp_del,,

topography_desc,,

vegetation_1,,

vegetation_2,,