Add ORCID into Persistent identifiers?

[yarikoptic]

New to shacl-vue here... it is very cool, well done @jsheunis . Trying it out on https://psychoinformatics-de.github.io/shacl-vue/?sh%3ANodeShape=dlsocial%3APerson , I wondered how come ORCID is not available there for Persistent identifier ?

another question from a greedy me - is there a way to fetch some metadata based on persistent identifier provided (e.g. from ORCID record - the names etc)?

[jsheunis]

Hey @yarikoptic ! Great to see you here :)

Good questions.

how come ORCID is not available there for Persistent identifier

This should be possible in different ways. As you can see the persistent identifier field can be a URI or CURIE. So technically you can add the full orcid url in the URI field. If you're asking why ORCID doesn't exist in the dropdown as one of the CURIEs to select from, this is because of two reasons:

1. ORCID as a prefix is not defined by the schema that drives the form generation process, nor by the config that allows for adding arbitrary prefixes.
2. I haven't added (or rather, brought back) the functionality for a user to edit/add prefixes (see relates issue for the TRR379 deployment: https://hub.datalad.org/datalink/annotate-trr379-demo/issues/3)

Also, another way to add an ORCID for a specific person record would be to add it as a related object in the Identifier field, see for example the record here: https://annotate.trr379.de/s/demo/?sh%3ANodeShape=dlsocial%3APerson

another question from a greedy me - is there a way to fetch some metadata based on persistent identifier provided (e.g. from ORCID record - the names etc)?

Not currently no, but this is definitely part of the envisioned functionality. This would need some translation steps between the fetched metadata format and the schema underlying the specific shacl-vue deployment.

Thanks for trying things out! Happy to get more feedback/requests, since we're in the phase of development where that can have great impact.

[yarikoptic]

ORCID as a prefix is not defined by the schema that drives the form generation process

and the schema is the http://github.com/psychoinformatics-de/datalad-concepts , but what particular file(s) are in play here to e.g. suggest to include ORCID? (I would assume src/things/unreleased.yaml for the next release?)

❯ git grep ADMS.*http
src/distribution/unreleased.yaml:  ADMS: http://www.w3.org/ns/adms#
src/identifiers/unreleased.yaml:  ADMS: http://www.w3.org/ns/adms#
src/things/unreleased.yaml:  ADMS: http://www.w3.org/ns/adms#
src/things/v1.yaml:  ADMS: http://www.w3.org/ns/adms#

[jsheunis]

There could be multiple sources from which the orcid prefix could be introduced. The general approach for datalad-concepts is to serve as a set of general schemas that are then imported by other more domain-specific schemas. As an example, see https://hub.trr379.de/q02/concepts.trr379.de/src/branch/main/src/base/unreleased.yaml (deployed here: https://concepts.trr379.de/), which includes the orcid prefix as it is useful in the research domain in which that consortium operates. Ironically, that inclusion of the prefix in the base schema is not the technical reason why the prefix persists into the shacl-vue deployment, but this is because of a LinkML-shacl-export limitation (you can see that the prefix is not included in the shacl export at: https://concepts.trr379.de/s/base/unreleased.shacl.ttl). The TRR379 schema drives the shacl-vue deployment at https://annotate.trr379.de/s/demo. If you look for example at @mih's Person record and open the editing form, you will see that the orcid prefix is available in the persistent identifier dropdown. This is because , to deal with the LinkML prefix export limitation, shacl-vue supports specifying arbitrary prefixes via configuration, see: https://hub.datalad.org/datalink/annotate-trr379-demo/src/branch/main/config.json#L53. Which highlights another source of including prefixes :)