search

tdwg / mids

11 stars 7 forks source link

MIDS Element - 11. CollectingAgent #22

Open RBGE-Herbarium opened 3 years ago

RBGE-Herbarium commented 3 years ago
Information Element Name CollectingAgent
Modified 2023/12/14
Label Collecting Agent
Definition A list (concatenated and separated) of names of people, groups, or organizations responsible for recording the original Occurrence.
Purpose For many biological collections the collector in combination with collectingNumber has been used as an identifier for the specimen in literature. It also helps in the identification and validation of the collecting location.
Applicable standard(s)/recommendation(s) It is recommended to include a verbatim version of the name as it appears on the label. The primary collector or observer, especially one who applies a collecting identifier (recordNumber), should be listed first. It is also strongly recommended to include people identifiers such as ORCID, Wikidata (See mids:CollectorID).
Examples Carl Linnaeus (https://www.wikidata.org/wiki/Q1043)
Required Yes (Biological)
Constraints
Element specification status under discussion
Notes none
samleeflang commented 1 year ago

ABCD mapping Could have multiple agents in one unit abcd:gathering/agents/gatheringAgent/0/person/fullName Alternatively the "Free text alternative for individual Agent" can be used. abcd:gathering/agents/gatheringAgent/0/person/agentText I would argue that the values from these fields need to be concatenated to a single value following the recommendation above. For example Fricke, Ronald | Troschel, Hans-Julius

There is also a general field with "Free text representation or concatenated version of those responsible for collecting or recording" abcd:gathering/agents/gatheringAgentsText

This is also what GBIF uses in their mapping. However, they only map the first name and don't concatenate multiple names. See this example

wouteraddink commented 1 year ago

I also think these should be concatenated, it is basically one agent and the agent is a group of people in this case. There is e.g. no need for storing individual provenance related to the collecting event for each person in the group.

Wouter

Op ma 27 feb. 2023 13:52 schreef Sam Leeflang @.***>:

ABCD mapping Could have multiple agents in one unit abcd:gathering/agents/gatheringAgent/0/person/fullName Alternatively the "Free text alternative for individual Agent" can be used. abcd:gathering/agents/gatheringAgent/0/person/agentText I would argue that the values from these fields need to be concatenated to a single value following the recommendation above. For example Fricke, Ronald | Troschel, Hans-Julius

There is also a general field with "Free text representation or concatenated version of those responsible for collecting or recording" abcd:gathering/agents/gatheringAgentsText

This is also what GBIF uses in their mapping https://github.com/gbif/pipelines/blob/f3aafc446e98b939c8290e2795aac3dd5aec890a/sdks/tools/archives-converters/src/main/resources/mapping/indexMapping_abcd_2_0_6.properties . However, they only map the first name and don't concatenate multiple names. See this example https://www.gbif.org/occurrence/2865018838

— Reply to this email directly, view it on GitHub https://github.com/tdwg/mids/issues/22#issuecomment-1446272776, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADAUXSRAFMEBNKMOVEIVZDWZSPQNANCNFSM4WKLN35A . You are receiving this because you are subscribed to this thread.Message ID: @.***>

emhaston commented 1 year ago

Updated to rename to RecordedBy since it maps exactly to DWC term.