-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How "taxonomically homogenous" for dwc class = Organism? #171
Comments
Why not use |
Okay, but what about listing the taxa and trying to say was was found with what using associatedOrganisms or associatedTaxa? I am planning to recommend using eventID and parentEventID since in this case people do re-visit the same site multiple times. Can associatedOrganisms be used in this case (hence wanting to know more about "taxonomically homogeneous"). |
We make frequent use of combination of eventID to document ecological datasets where the sampling process and which organisms have been collected together are crucial information - e.g. our Limnic freshwater invertebrate collection . Also lot of use of parentEventID to document hierarchical sampling designs it kind of works. Tetraonid line transect surveys as example, but at least GBIF does not recognize events without occurrences so that you have to go to the raw DwC-A to see the structure. As for associatedOrganism, my interpretation of the examples given was more that this was of the type "sibling of", "mother of" etc. which perhaps could better document using Resource Relationships? |
I would be good to understand your use case better - what is actually
happening during the collecting event. I think I understand the part of
wanting to capture explicitly the associations of other taxa collected
simultaneously, for which associated taxa does sound right. The part that
is confusing is the taxonomic homogeneity question. Can you not capture the
distinct taxa in separate Occurrence rows for some reason?
…On Fri, Mar 19, 2021 at 4:33 AM Anders G. Finstad ***@***.***> wrote:
We make frequent use of combination of eventID to document ecological
datasets where the sampling process and which organisms have been collected
together are crucial information - e.g. our Limnic freshwater
invertebrate collection
<https://www.gbif.org/dataset/33591b80-0e31-480c-82ce-2f57211b10e6> .
Also lot of use of parentEventID to document hierarchical sampling designs
it kind of works. Tetraonid line transect surveys
<https://www.gbif.org/dataset/6a948a1c-7e23-4d99-b1c1-ec578d0d3159> as
example, but at least GBIF does not recognize events without occurrences so
that you have to go to the raw DwC-A to see the structure.
As for associatedOrganism, my interpretation of the examples given was
more that this was of the type "sibling of", "mother of" etc. which perhaps
could better document using Resource Relationships?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#171 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQ7257VYYX57D6SNQLC7LTEL435ANCNFSM4ZNQZ7NQ>
.
|
Is the discussion here relevant for the problem you're trying to solve? From my perspective it seems like |
Related to this discussion, I have added an issue (tdwg/dwc#324) about the inconsistency of the dwc:associatedOccurrences term. |
Greetings. Enter, a mapping conundrum.
Given: I note that the definition for DwC Organism Class = A particular organism or defined group of organisms considered to be taxonomically homogeneous.
Question: For a material sample event where all objects collected / observed = freshwater mussels -- is that taxonomically homogenous enough?
Why? In order to decide if I might use dwc:associatedOrganisms with a relationship from an ontology that would let me express found with or collected with for all the taxa involved (assuming such a term exists in RO or similar). And then I might include a note in dwc:organismRemarks to state collected at same site, same event.
OR
Do I stick with dwc class = Occurrence and the corresponding field: dwc:associatedTaxa
Thanks for insights.
The text was updated successfully, but these errors were encountered: