basal_diam,basalDiameter,

stem_canopy_form,canopyForm,

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

collector_code,collector_code,Brad: OMIT

cover_percent,coverPercent,

census_date,eventDate,"This is for the subplot, not the organism, as all organisms in a subplot have the same value for it. The following query returns no rows:

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

family,family,

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

genus,genus,

stem_height_m,height/_alt/1,"Brad: Same as for height, but applies to individuals stems, not trees. Rare."

height_m,height/_alt/2,

cf_aff,identificationQualifier,"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."

ind_id,ind_id,Brad: OMIT

no_of_individuals,individualCount,"Brad: 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."

OBSERVATION_ID,individualID,"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."

infra_ep_1,infraspecificEpithet,

stem_liana_infestation,lianaInfestation,

PLOT_ID,locationID,

x_position,organismX,"Brad: These are important, fundamental values of many tree plots"

plot_code,plotName,

tag2,previousTag/_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."

individual_code,recordNumber,"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."

coll_firstname,recordedBy.givenName,Brad: See comment above

coll_lastname,recordedBy.surName,"Brad: 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."

specific_authority,scientificNameAuthorship,Brad: This is the author of the scientificName.

species_status,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."

specific_epithet,specificEpithet,

notes,stemNotes,

subplot,subplot,

tag1,tag/_alt/1,"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."

infra_rank_1,taxonRank,

orig_family,verbatimFamily,Brad: OMIT

habit,verbatimGrowthForm,"Brad: This is growth form (tree, shrub, herb, etc.). It is an observation of a trait."

orig_species,verbatimSpecificEpithet,Brad: OMIT

intercept_cm,volumeCanopy,"Brad: 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."

det_type,voucherType,"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."