Revision 4574
Added by Aaron Marcuse-Kubitza over 12 years ago
| VegBIEN.csv | ||
|---|---|---|
| 19 | 19 |
individualCount,/location/locationevent/taxonoccurrence/aggregateoccurrence/count, |
| 20 | 20 |
convertednotes,/location/locationevent/taxonoccurrence/aggregateoccurrence/notes, |
| 21 | 21 |
notes,/location/locationevent/taxonoccurrence/aggregateoccurrence/notes, |
| 22 |
collectorNumber,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/collectionnumber/_alt/1,
|
|
| 22 |
collectorNumber,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/collectionnumber, |
|
| 23 | 23 |
catalogNumber,"/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/specimenreplicate/catalognumber_dwc/_if[@name=""if indirect voucher""]/else", |
| 24 | 24 |
collectionCode,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/specimenreplicate/collectioncode_dwc/_join/1,Brad: Not sure if mapping correct. DwC element; code for entire collection; often same as InstitutionCode; Aaron: Combining with InstitutionCode to create collection name |
| 25 | 25 |
institutionCode,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/specimenreplicate/institution_id/party/organizationname, |
| 26 |
collectorNumber,/location/locationevent/taxonoccurrence/authortaxoncode/_alt/1/_alt/1,
|
|
| 26 |
collectorNumber,/location/locationevent/taxonoccurrence/authortaxoncode/_alt/1, |
|
| 27 | 27 |
scientificName,/location/locationevent/taxonoccurrence/authortaxoncode/_alt/2/_alt/2, |
| 28 | 28 |
identifiedBy,/location/locationevent/taxonoccurrence/taxondetermination[!isoriginal]/*_id/party/givenname/_namePart/first, |
| 29 | 29 |
identifiedBy,/location/locationevent/taxonoccurrence/taxondetermination[!isoriginal]/*_id/party/middlename/_namePart/middle, |
Also available in: Unified diff
mappings/Veg+-VegCore.csv: Removed recordNumber/_alt and recordNumber redirection mappings so that Veg+-VegCore.csv contains only renamings, not business logic. Note that removing the global ordering of these fields does not affect the datasources which contain multiple recordNumber synonyms because they either have a custom ordering or one field is duplicated or unused.