SALVIAS,VegBIEN:/locationevent,Comments

plot_area_ha,/*_id/location/area,"Brad: Area in hectares. Is there any way to store units?; Aaron: VegX plot area annotation says ""Total area of the plot in square meters."" so units are fixed"

plot_code,/*_id/location/authorlocationcode,Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)

elev_m,/*_id/location/elevation/_alt/1,Brad: Mean elevation in meters. This is a constrained decimal value; is there no place for this in VegX other than verbatimElevation? Check with Nick.

country,"/*_id/location/locationplace(/*_id/namedplace[placesystem=""area|country|territory""])/placename",

pol1,"/*_id/location/locationplace(/*_id/namedplace[placesystem=""region|state|province""])/placename",Brad: No; pol1=stateProvince

major_geo,/*_id/location/locationplace(/*_id/namedplace[placesystem=continent])/placename,

pol2,/*_id/location/locationplace(/*_id/namedplace[placesystem=county])/placename,Brad: No pol2=countyParish

locality_description,/*_id/location/locationplace/*_id/namedplace/placedescription,"Brad: No; this is free text description of locality where plot was situated, same as for DwC. Not a description of vegetation. Most likely='namedPlace.placeDescription' in VB; not sure about VX, again need to ask Nick where locality descriptions live in VX"

lat_decimal,/*_id/location/reallatitude,

long_decimal,/*_id/location/reallongitude,

slope_aspect,/*_id/location/slopeaspect,

slope_gradient,/*_id/location/slopegradient,

elev_max_m,"/*_id/location/{elevation/_alt/2/_avg/max,elevationrange/_range/to}",

elev_min_m,"/*_id/location/{elevation/_alt/2/_avg/min,elevationrange/_range/from}",

project,/*_id/project/projectname,

precip_mm,"/definedvalue[*_id/userdefined[tablename=locationevent,userdefinedname=precipitationMm]]:[@fkey=tableRecord_ID]/definedvalue",

temp_c,"/definedvalue[*_id/userdefined[tablename=locationevent,userdefinedname=temperatureC]]:[@fkey=tableRecord_ID]/definedvalue",

plot_methodology,/methodnarrative,

date_finish,/obsenddate/_*/date,

date_start,/obsstartdate/_*/date,

soil_acidity,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilAcidity]]:[@fkey=tableRecord_ID]/definedvalue",

soil_base,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilBase]]:[@fkey=tableRecord_ID]/definedvalue",

soil_Ca,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilCalcium]]:[@fkey=tableRecord_ID]/definedvalue",

soil_C,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilCarbon]]:[@fkey=tableRecord_ID]/definedvalue",

soil_cation_cap,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilCationCap]]:[@fkey=tableRecord_ID]/definedvalue",

soil_conductivity,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilConductivity]]:[@fkey=tableRecord_ID]/definedvalue",

soil_Mg,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilMagnesium]]:[@fkey=tableRecord_ID]/definedvalue",

soil_N,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilNitrogen]]:[@fkey=tableRecord_ID]/definedvalue",

soil_P,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilPhosphorus]]:[@fkey=tableRecord_ID]/definedvalue",

soil_K,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilPotassium]]:[@fkey=tableRecord_ID]/definedvalue",

soil_Na,"/soilobs:[soilhorizon=unknown]/definedvalue[*_id/userdefined[tablename=soilObs,userdefinedname=soilSodium]]:[@fkey=tableRecord_ID]/definedvalue",

clay_percent,/soilobs:[soilhorizon=unknown]/soilclay,

organic_percent,/soilobs:[soilhorizon=unknown]/soilorganic,

pH,/soilobs:[soilhorizon=unknown]/soilph,"Brad: For all these soil variables, how do we store information on method, units. Seems like an ontological structure would be more appropriate (measurementName, measurementValue, measurementUnits, measurementMethod). Same as BIEN traits table. Something to discuss."

sand_percent,/soilobs:[soilhorizon=unknown]/soilsand,

silt_percent,/soilobs:[soilhorizon=unknown]/soilsilt,

soil_texture,/soilobs:[soilhorizon=unknown]/soiltexture,

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,,** No join mapping for ->/*s/communityDetermination[*ID]/communityConcepts/communityConcept/name ** 

life_zone_code,,** No join mapping for ->/*s/communityDetermination[*ID]/communityConcepts/communityConcept/commonName ** 

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"

SALVIAS,VegBIEN:/taxonoccurrence,Comments

subplot,/*_id/locationevent/*_id/location/authorlocationcode,

plot_code,/*_id/locationevent/*_id/location/parent_id/location/authorlocationcode,"Brad: Same as plotCode, above"

census_date,/*_id/locationevent/obsstartdate/_date/year,

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

stem_height_m,/aggregateoccurrence/*_id/plantobservation/overallheight,"Brad: Same as for height, but applies to individuals stems, not trees. Rare."

stem_tag1,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode,"Brad: Same as tag1 & tag2, but applied to individual stems. I'm still not clear how to distinguish between methods which tag only individuals trees, and those which tag individual stems."

stem_tag2,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode,Brad: see above

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

basal_diam,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=basalDiameter]]:[@fkey=tableRecord_ID]/definedvalue",

stem_canopy_form,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=canopyForm]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Should also be userDefined for VegBank. 

stem_canopy_position,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=canopyPosition]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Should also be userDefined for VegBank. 

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

stem_height_first_branch_m,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=heightFirstBranchM]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Should also be userDefined for VegBank. Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare."

stem_liana_infestation,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=lianaInfestation]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Should also be userDefined for VegBank. 

stem_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

no_of_individuals,/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."

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

det_type,"/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

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

specific_authority,"/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",

specific_epithet,"/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",

cf_aff,"/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",

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

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

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

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