dsp-api

dsp-api copied to clipboard

Different people often have the same name. It would be helpful if each Knora user could have an ORCID to uniquely identify them:

https://orcid.org/

But that's again the subject of the metadata related to the project, dataset and researcher involved in a project. This matter has never been settle. See here: https://github.com/LaDHUL/Knora-projects-metadata/blob/master/knora-metadata-V1.ttl.

I think this should be tested/reviewed/improved and maybe extended. However, the ORCID was already there :)

Can we start small and add things gradually, when we’re sure they’re needed? I think the argument for ORCID is pretty clear, but I’m not sure about some of the other things in that proposal.

Well, that's exactly this: a proposal. But, as a data provider, we are going to need a lot more metadata to describe our projects/data.

See here, for example:

• https://datacatalogue.cessda.eu/detail?q=%22UK-Data-Service__2525%22
• https://forsbase.unil.ch/project/study-public-overview/15406/0/
• https://schema.datacite.org/meta/kernel-4.0/

@benjamingeer yes, can be easily added. Even something like this should be possible:

GET /admin/users/orcid/[orcIdentifier]

The project metadata issue #566 is still open. We (and by that I mean myself) never had time to work on it.

Bouncing back on ORCID, here are some recommendation for using ORCID in repositories (and updating ORCID accounts based on data hosted in a repository itself): https://orcid.org/blog/2019/02/27/recommendations-using-orcid-repositories

It may be of interest.