Revision 4857
Added by Aaron Marcuse-Kubitza almost 12 years ago
| new_terms.csv | ||
|---|---|---|
| 1 |
AuthorOfScientificName |
|
| 2 |
CatalogNO |
|
| 3 |
CollectionCD |
|
| 4 |
GBIFFamilyOriginal |
|
| 5 |
GBIFGenusOriginal |
|
| 6 |
InstitutionCD |
|
| 7 |
LastDateModified |
|
| 8 |
LatestDateCollected |
|
| 9 |
MaximumElevationInMeter |
|
| 10 |
MinimumElevationInMeter |
|
| 11 |
ScientificNameOriginal |
|
| 1 |
AuthorOfScientificName,scientificNameAuthorship,, |
|
| 2 |
CatalogNO,catalogNumber,, |
|
| 3 |
CollectionCD,collectionCode,, |
|
| 4 |
GBIFFamilyOriginal,verbatimFamily,, |
|
| 5 |
GBIFGenusOriginal,verbatimGenus,, |
|
| 6 |
InstitutionCD,institutionCode,, |
|
| 7 |
LastDateModified,dcterms:modified,, |
|
| 8 |
LatestDateCollected,dateCollected,, |
|
| 9 |
MaximumElevationInMeter,maximumElevationInMeters,, |
|
| 10 |
MinimumElevationInMeter,minimumElevationInMeters,, |
|
| 11 |
ScientificNameOriginal,verbatimScientificName,, |
|
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.