search

nfdi4plants / Swate

Excel Add-In for annotation of experimental data and computational workflows.
https://swate-alpha.nfdi4plants.org
MIT License
31 stars 6 forks source link

[Feature Request] Setup of DPBO purls #324

Closed Hannah-Doerpholz closed 3 months ago

Hannah-Doerpholz commented 10 months ago

Is your feature request related to a problem? Please describe. In issue #321 is was reported that purls for DPBO are currently not working. A possible workaround is described here.

Describe the solution you'd like Currently, purls are constructed like this:"https://obolibrary.org/obo/" + "DPBO_0000035". Since the purl domain /obo/ does not belong to us we need to adjust the purls accordingly. My suggestion is to construct purls like this "http://purl.org/nfdi4plants/ontology/dpbo#" + "DPBO_0000035". I have already set up the redirect to our github file for any links in the mentioned domain (nfdi4plants/ontology/dpbo). Adding the hash after the domain name and then the accession is crucial to make the purls work.

Describe alternatives you've considered Adding individual redirects for all terms is not suitable as the DPBO is a transient ontology meant to keep terms temporarily before suggesting them to external ontologies.

Additional context Once we have a similar terminology search tool like nfdi4chem set up (https://terminology.nfdi4chem.de/ts/), which has been requested if I am not mistaken, we should redirect there.

Freymaurer commented 3 months ago

Can you give me an update on this issue? Is this also something TS4TIB does?

Hannah-Doerpholz commented 3 months ago

So, I have created all purls for the terms that are currently in DPBO. The ontology repo now also has an automated workflow that creates new purls whenever new DPBO terms are added to the .obo file. The purl checker + creation runs every Saturday once per week, since it takes a while to run. The purls are created at the InternetArchive's purl service and are formatted like this: http://purl.org/nfdi4plants/ontology/dpbo/DPBO_0000001 . They open the link to that term in the TIB service. If the links could be created in swate in this format, we can use this. That would (from our current understanding) be the easiest way at the moment to solve this issue.