Task - DwC Dashboard - option to include biological associations extension

[mjy]

No description provided.

[seltmann]

@debpaul @mjy Just moving our prior email conversation here for better tracking

Jan 31, 2023
Katja wrote:

Istvan (and perhaps soon Elijah) will be using TaxonWorks to manage and share specimen information for the Big-Bee project. Tommy mentioned that TW is presently not exporting the associatedTaxa field in its Darwin Core archive. The Big-Bee project stated that we would specifically share those data because bee labels have a lot of host plant information. We are going from the DwC to GloBI, aligning with the RO, and then creating a published version of all bee hosts.

I am reaching out to understand how this field can be shared via TaxonWorks in the near future if it is not already.

There are also some possible cool things here too. Many bee labels have more information than just the taxon name of a plant. Many say "visits" or "visits flowers of" or "collect oil from." In Symbiota, we add as a key:value pair in the associatedTaxa field (i.e., visits: Enceilia).

Matt wrote:
Timely, I'm working on the last complex bits of our new BiologicalAssociations filter right now.

Issue tracking for this specific request is here: #2554. Let's please move discussion there so we don't lose this in an email thread.

To catch you up, we use basically a full ontology for BiologicalAssociations behind the scenes - https://docs.taxonworks.org/develop/Data/models.html#biological-association. For example you can define range, domain for your relationships etc.

IIRC you sent me what we need to do re creating a ResourceRelationship table for this data. My gut feeling is we will have issues with DwC not supporting domain/range concepts (they are the missing bit in the ongoing conversation that recently popped up on the GBIF tracker recently IMO), but other than that it should be straightforward.

Implementation wise this is medium-long term, i.e. mid to late in your grant I suspect.

Alternatively, if people are not parsing their relationships then they should be able to use whatever data-attributes they want on CollectionObjects or CollectingEvents (see docs for concept definition). There is currently a bug in the dump that's preventing them getting out to DwC, but that will be fixed shortly.

[seltmann]

Hey @mjy I noticed you closed this related issue. Anything new to report or is it ready for export?

[mjy]

@seltmann the 1:1 mapping (you type in this field, you get that typing back out) is done. The full DwC extension (this issue), is not.

[seltmann]

@mjy thanks for the update Matt. I dont fully understand the progress report. I am sure it is a much bigger feature than able to explain in a few sentences, but I am assuming that is about adding associatedTaxa locally, in an instance of TaxonWorks and it will be added correctly to the model? Just curious more than anything, dont worry if you dont have the time to explain the entire thing,
Katja

[mjy]

@seltmann sorry for confusion. I took the opportunity to add some documentation to docs.taxonworks.org to try and better answer this properly.

See https://docs.taxonworks.org/guide/Manual/annotation.html and in particular, for this use case https://docs.taxonworks.org/guide/Manual/annotation.html#data-attributes.

Let me know if this helps, if it doesn't we'll keep refining it. Thanks!