Support CURIE lookup #229

New issue

Open

opened 2025-10-13 08:22:03 +00:00 by mih · 3 comments

mih commented

2025-10-13 08:22:03 +00:00

(Migrated from github.com)

Right now, for each record the "Persistent identifier" is presented as a fully resolved URI, e.g. something like https://scicrunch.org/resolver/RRID:SCR_016124.

It would be good, to give users the ability to know about a schema-compliant CURIE too. Arguably, this is the more relevant format for people looking to cite a record.
For the example above, I click on the "View RDF button" would reveal rrid:SCR_016124 -- but this require sophisticated prior knowledge to understand.

The use case needing support here is people using shacl-vue to look up relevant instances to cite in scripts aiming to submit records programmatically.

Right now, for each record the "Persistent identifier" is presented as a fully resolved URI, e.g. something like `https://scicrunch.org/resolver/RRID:SCR_016124`. It would be good, to give users the ability to know about a schema-compliant CURIE too. Arguably, this is the more relevant format for people looking to cite a record. For the example above, I click on the "View RDF button" would reveal `rrid:SCR_016124` -- but this require sophisticated prior knowledge to understand. The use case needing support here is people using shacl-vue to look up relevant instances to cite in scripts aiming to submit records programmatically.

mih commented

2025-10-21 08:11:21 +00:00

(Migrated from github.com)

I find this to be a major inconvenience in the absence of a proper curation workflow helper.

jsheunis commented

2025-10-27 15:34:33 +00:00

(Migrated from github.com)

Would it solve the problem to just show the PID in CURIE format rather than fully resolved URI? Or are you also saying that, in addition to that, we should also have some UI component that allows users to view and filter through current namespaces (and their CURIEs) known to the deployment? I recall that a previous (long time ago) version of shacl-vue had such a component, which also allows users to add more namespaces and CURIEs. I could bring that back?

Would it solve the problem to just show the PID in CURIE format rather than fully resolved URI? Or are you also saying that, in addition to that, we should also have some UI component that allows users to view and filter through current namespaces (and their CURIEs) known to the deployment? I recall that a previous (long time ago) version of `shacl-vue` had such a component, which also allows users to add more namespaces and CURIEs. I could bring that back?

mih commented

2025-10-28 04:52:13 +00:00

(Migrated from github.com)

We I need is the pid that dumpthings want me to use to retrieve the record (or update). I cannot know if that is curie or resolved. In my personal use these are all curies, though.

I need not have more complex namespace tools.

We I need is the pid that dumpthings want me to use to retrieve the record (or update). I cannot know if that is curie or resolved. In my personal use these are all curies, though. I need not have more complex namespace tools.