Open ManonGros opened 5 months ago
@ManonGros from our conversation earlier this is what I got.
A csv can have one or multiple columns. There is no mandatory columns. CSVs can be sparsely populated (one row can be completely filled, and the next one only a few of the columns).
Some of the columns will be multivalue fields (e.g. pipe separated preparations).
Yes that's exactly that.
For the multivalued fields, I would be in favour of supporting the ones that are already supported in the occurrence index: recordedBy but not support everything multivalue. Alternatively, we can also say we don't support multiple values and force people to upload each value in a separate row.
Essentially, this is the difference between this mapping: swisscollnet_dwcltc_2a8835ad-4a2e-43df-b976-f924f76fe628.csv and this one swisscollnet_ALTERNATIVE_dwcltc_part2_2a8835ad-4a2e-43df-b976-f924f76fe628.csv.
Is scientific name and country multi value? I ask because they are interpreted and adds hierarchies. And that would make them different from the occurrence index
country and scientificName aren't multivalue in the occurrence index and I don't think they should be in the collection descriptors either (it would be a headache).
In the context of exploring the implementation of the roadmap item 2: https://scientific-collections.gbif.org/road-map#2-support-structured-collection-descriptors, here are some actual data which would feed into the collection descriptors.
The fields that are mapped to a Darwin Core or Latimer core term are prefaced with
dwc:
orltc:
(for exampledwc:country
). I didn't map everything but tried to get a bit of everything across the examples.Num. Databased
andNum. Imaged
** I left the quantitative values unmapped because I wasn't sure how best to do it. The Latimer core recommendation is to use https://tdwg.github.io/ltc/terms/#MeasurementOrFact_MeasurementOrFact with a definition for each measurement. It doesn't easily fit into those flat tables and each source has its own metrics. It would be quite difficult to combine everything (check the examples provided).
As a side note many fields that I mapped to
ltc:objectClassificationName
should/would be using the DISSCO topicCategory vocabulary (https://docs.google.com/document/d/19OPyOm9VF2qfI3M6RmJPvRfo8JlZ3tt0II05aGCyBHQ/edit)