Revision 4857
Added by Aaron Marcuse-Kubitza almost 12 years ago
| new_terms.csv | ||
|---|---|---|
| 1 |
Accession Number |
|
| 2 |
Accuracy |
|
| 3 |
Barcode |
|
| 4 |
Collect Date |
|
| 5 |
Format |
|
| 6 |
Full Taxon Name |
|
| 7 |
Lat (-=S) |
|
| 8 |
Long (-=W) |
|
| 9 |
SeriesName |
|
| 10 |
Typology |
|
| 1 |
Accession Number,occurrenceID,, |
|
| 2 |
Accuracy,coordinateUncertaintyInMeters,, |
|
| 3 |
Barcode,catalogNumber,, |
|
| 4 |
Collect Date,dateCollected,, |
|
| 5 |
Format,preparations,, |
|
| 6 |
Full Taxon Name,scientificName,, |
|
| 7 |
Lat (-=S),verbatimLatitude,"/_replace:[""\?$""=]/value", |
|
| 8 |
Long (-=W),verbatimLongitude,"/_replace:[""\?$""=]/value", |
|
| 9 |
SeriesName,collectionCode,, |
|
| 10 |
Typology,typeStatus,, |
|
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.