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

PlotCode,locationName,,

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:

-----

SELECT ""PlotID"", ""Line"", count(DISTINCT census_date) AS census_date_count

FROM ""SALVIAS"".organisms

WHERE ""Line"" IS NOT NULL AND census_date IS NOT NULL

GROUP BY ""PlotID"", ""Line""

HAVING count(DISTINCT census_date) > 1

-----"

Line,subplot,,

Ind,individualCode,,"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."

tag1,tag,/_alt/2,"The second tag supercedes the first. 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."

x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"

y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"

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

coll_number,recordNumber,/_alt/1,Brad: Map instead as for voucher_string

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

coll_firstname,recordedBy_givenName,,Brad: See comment above

det_by,identifiedBy,,

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

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

name_status,OMIT,,"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."

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

infra_rank_1,taxonRank,,

infra_ep_1,infraspecificEpithet,,

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

OrigFamily,originalFamily,,Brad: OMIT

OrigGenus,originalGenus,,

OrigSpecies,originalSpecificEpithet,,Brad: OMIT

temp_dbh,diameterBreastHeight_cm,,"Assuming units based on the units for intercept_cm, which measures the same dimension"

PlotID_index,OMIT,,Placeholder column created by MySQL to PostgreSQL translation

tmp_del_index,OMIT,,Placeholder column created by MySQL to PostgreSQL translation

tmp_PlotObsID_index,OMIT,,Placeholder column created by MySQL to PostgreSQL translation