SpeciesFileGroup / taxonworks

Workbench for biodiversity informatics.
http://taxonworks.org
Other
85 stars 25 forks source link

[Bug]: collectionCode and basisOfRecord in DwC Imported dataset not present in DarwinCore output for TW CO #3994

Open debpaul opened 1 month ago

debpaul commented 1 month ago

Steps to reproduce the bug

1. Using DwC Importer
2. One column is collectionCode (from Darwin Core)
3. This property and its values do not show up in the Darwin Core view of CO in TW.
4.  Same for basisOfRecord
...

Screenshot

image

Expected behavior

Upon upload of a dataset that includes the collectionCode column, that this term and the values provided would be in the Darwin Core output that one sees in Browse CO.

Work done here by Davide Dal Pos to test the DwC Importer Where: Sandbox, https://sandbox.taxonworks.org, project = UCF Collection - The Bug Closet Which DwC Importer dataset? either Final2 and Final_parsing

Additional Screenshots

No response

Environment

Sandbox

Sandbox Used

sandbox

Version

fbfe6cb54

Browser Used

No response

LocoDelAssembly commented 1 month ago

Do we actually have a place for that @mjy? The importer is not importing that (although it can as data attribute), however the exporter has no collectionCode. The closest thing I now TW supports is looking up identifiers of type Identifier::Local::CatalogNumber (hopefully only one of them) and assume that the namespace's short name is the collectionCode (not always the case).

debpaul commented 1 month ago

@LocoDelAssembly I guess we could put them in as data attributes? dwc:basisOfRecord (or similar) will be needed as we publish different types of data (field/human observation data, paleo, biological specimens, etc).

LocoDelAssembly commented 1 month ago

You may import as data attributes by following https://docs.taxonworks.org/guide/import.html#mappings-to-dwc-predicates (only <term> part needs to be in column name). This is a project-wide setting, not something you set up on every import.