NHMDenmark / DanSpecify

Important files regarding the Danish instance of the Specify database system for collections digitisation and management, plus placeholder for issue tracking. Guidelines, manuals and other kinds of documentations will be gathered on the wiki.
3 stars 3 forks source link

Færøskealger database import (Rigsarkivet - deadline june 2024) #253

Open FedorSteeman opened 1 year ago

Sosannah commented 6 months ago

First version of the dataset has arrived, with the following message: FaroeAlgaeExport (003).xlsx

"Data is a part of the general algae herbarium database, so I do not want it to be some sort of separate dataset. When Specify is able to be used as a daily working tool for live datasets, the rest of the algae data should be in the same structure .

You can probably figure the data structure out from the data; the Faroese data are relatively uncomplicated. Kodenr is collectors number, I think it is the only one that are not self-explanatory. In this dataset and all other following from me, the Musnr = museum number, is the important unique identifier, the number on the specimens. This has to be the number presented as the specimen identifier to outside users. You are welcome to give it an NHMD number, but this is only to be an internal used number, not a published number. And the number is all of it, C-A-123456, not just the ciphers! I do not need to be able to print labels for this part of data, so you do not need to set up a label layout yet, but I shall send you an example of how a label should look like in general for my collections, so you can get that into specify. "

Sosannah commented 6 months ago

Suggested task: creating a new collection for the Algal herbarium in Specify, (like the Vascular Plants and and the Biocultural Collections) under the same Botany discipline.

Interpretation of fields: • MusnrCorr – alternative catalogue number • Land - Country • Lokalitet - Locality • Koordinat - Coordinates • Dybde – Depth (in m) • Artnavn – Scientific name • Corrdato – Collection date • Leg - Collector • Kodenr – Collector number • Det – Determiner

Suggestion regarding to unique identifier: Keeping the Musnr as a unique identifier the same way it exists now (C-A-123456) as an alternative catalogue number. Assigning NHMD numbers to the objects. As it’s not a viable option to use the NHMD number only internally, we should publish them as well, along with the Musnr, just like we did with the type specimens.

Label: noted. We’ll create a template, when we'll get input.

Further questions: • Aren’t there any second determinations in this dataset? • Wouldn’t you like to add storage information to the occurrences? • Aren’t there any references this time? • What are the preparation types of these objects? • Any field notes to register? • Any type specimen within the dataset? • Could you provide higher taxonomy for these species or should we gather the information?

Sosannah commented 4 months ago

The dataset was imported (after cleaning and standardization).

GBIF - publishing

In GBIF, a static dataset of our Algae collection is already available, which need to be retired first, before we can publish the dynamic version (every update in Specify is published within a week to GBIF). Though, the static dataset complies a much larger dataset (108.699 occurrences) than we have in Specify (10.145 occurrences) – not only the ones collected in Faroe islands.

We have (at least) two options:

  1. We can remove the corresponding records from static dataset and publish the dynamic one.
  2. Or, we wait for retiring the static dataset until we import all algae records into Specify.

In case of the second option we can keep the GBIF identifiers of the single records and support the needs for citations and data linking.

The second option was accepted by Christian L.