Revision 4857
Added by Aaron Marcuse-Kubitza almost 12 years ago
new_terms.csv | ||
---|---|---|
1 |
AgeClass |
|
2 |
CatalogNumberNumeric |
|
3 |
GenBankNum |
|
4 |
GeorefMethod |
|
5 |
HorizontalDatum |
|
6 |
IdentificationModifier |
|
7 |
LatLongComments |
|
8 |
OriginalCoordinateSystem |
|
9 |
RelatedCatalogedItems |
|
10 |
TimeCollected |
|
11 |
Tissues |
|
12 |
VerbatimCollectingDate |
|
1 |
AgeClass,lifeStage,, |
|
2 |
CatalogNumberNumeric,catalogNumber,/_alt/1, |
|
3 |
GenBankNum,associatedSequences,"/_label[label=""GenBank""]/value", |
|
4 |
GeorefMethod,georeferenceProtocol,, |
|
5 |
HorizontalDatum,UNUSED,, |
|
6 |
IdentificationModifier,identificationQualifier,, |
|
7 |
LatLongComments,georeferenceRemarks,, |
|
8 |
OriginalCoordinateSystem,verbatimSRS,, |
|
9 |
RelatedCatalogedItems,relatedResourceID,/_alt/2,Used only when OtherCatalogNumbers is NULL |
|
10 |
TimeCollected,eventTime,, |
|
11 |
Tissues,UNUSED,, |
|
12 |
VerbatimCollectingDate,dateCollected,/_alt/0, |
Also available in: Unified diff
input.Makefile: Maps validation: %/new_terms.csv: Include the entire map spreadsheet row, so that each new term is listed together with its mapping. This facilitates adding new mappings to mappings/Veg+-VegCore.csv directly from any new_terms.csv. Note that the use of `sort -u` (in lib/mappings.Makefile) causes multiline comments to be separated, leading to spurious lines for each multiline comment line.