Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Person ORCID field? #8

Closed
Freymaurer opened this issue Mar 21, 2024 · 4 comments
Closed

Person ORCID field? #8

Freymaurer opened this issue Mar 21, 2024 · 4 comments
Assignees

Comments

@Freymaurer
Copy link

Currently we have no field in Person (and here) to represent ORCID.

I suggest using identifier, but there might be more appropriate fields.

@floWetzels
Copy link
Collaborator

I think @HLWeil's suggestion in #16 could also be applied here.

@stuzart
Copy link
Collaborator

stuzart commented May 14, 2024

for the workflow ro crate we use identifier for the ORCID, e.g.

{
      "@id": "https://orcid.org/0000-0001-8875-7304",
      "@type": "Person",
      "name": "Thomas Roetzer-Pejrimovsky",
      "identifier": "https://orcid.org/0000-0001-8875-7304"
    }

@floWetzels
Copy link
Collaborator

Yes, that's a good option. It fits with Lukas' suggestion on PubMedIDs or DOIs. Since identifier allows for PropertyValue objects, we can use them to specify that it is an identifier of type ORCID:

{
  "@id": "https://orcid.org/0000-0001-8875-7304",
  "@type": "Person",
  "name": "Thomas Roetzer-Pejrimovsky",
  "identifier": {
    "propertyID": "ORCID",
    "value": "0000-0001-8875-7304"
  }
}

To me, it doesn't really matter which option w choose.

@floWetzels
Copy link
Collaborator

Fixed by PR #19

@github-project-automation github-project-automation bot moved this to Done in ARCStack Jun 21, 2024
@HLWeil HLWeil removed the Status: Needs Triage This item is up for investigation. label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

5 participants