Skip to content
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

Open
debpaul opened this issue Mar 18, 2021 · 6 comments
Open

How "taxonomically homogenous" for dwc class = Organism? #171

debpaul opened this issue Mar 18, 2021 · 6 comments
Labels
new term - MaterialSample term - Organism Pertaining to a term organized in the Organism class.

Comments

@debpaul
Copy link
Contributor

debpaul commented Mar 18, 2021

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.

@debpaul debpaul added new term - MaterialSample term - Organism Pertaining to a term organized in the Organism class. labels Mar 18, 2021
@albenson-usgs
Copy link

Why not use eventID to associate the occurrences together?

@debpaul
Copy link
Contributor Author

debpaul commented Mar 19, 2021

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").

@andersfi
Copy link

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?

@tucotuco
Copy link
Member

tucotuco commented Mar 19, 2021 via email

@albenson-usgs
Copy link

Is the discussion here relevant for the problem you're trying to solve? From my perspective it seems like associatedOrganisms is intended for animals that form behavioral groups and associatedOccurrences is intended for a more general use case of occurrences linked together in some way. It's a bit confusing because ecological datasets are de facto associated occurrences but I never use that term so it does seem like some clarity on use cases for when to use that term would be helpful. Also from my reading of the two terms (which have the exact same definitions except for the word "occurrence"/"organism") that you can include the relationship in associatedOccurrences the same as you would for associatedOrganisms.

@tucotuco
Copy link
Member

Related to this discussion, I have added an issue (tdwg/dwc#324) about the inconsistency of the dwc:associatedOccurrences term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new term - MaterialSample term - Organism Pertaining to a term organized in the Organism class.
Projects
None yet
Development

No branches or pull requests

4 participants