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

add orcid and ror to namespaces #41

Merged
merged 2 commits into from
Sep 23, 2022
Merged

Conversation

timothypage
Copy link
Contributor

We talked a while ago about using this codelist as the dropdown for the Contact > External Identifiers namespace (which translates to ISO 19115 partyIdentifier namespace) and adding orcid and ror to this list.

@timothypage timothypage self-assigned this Aug 25, 2022
@dwalt
Copy link

dwalt commented Aug 26, 2022

This may need some conversation, possibly with users. Looking here: https://info.orcid.org/brand-guidelines/#the-orcid-name and here: https://ror.org/display-guidelines/ and the pattern of usage in the codelist, It might look something like this:

  • orcid.org | ORCID | "desc"
  • ror.org | ROR | "desc"

This scheme would allow building a pathname from the code and the number, without interpreting the coding. Hilmar may have some ideas on this.

@hmaier-fws
Copy link
Contributor

I concur with @dwalt. Based on the maintaining organization guidelines and consistency with other items in the code list, I would recommend:

  • {code: "orcid.org", codeName: ORCID, description: "ORCID identifier"}
  • {code: "ror.org", codeName: ROR, description: "Research Organization Registry identifier"}

This also closes #36

Since we're updating the list we should also add:

  • {code: "spatialreference.org", codeName: SR-ORG, description: "Coordinate reference system from SpatialReference.org database"}

The above was identified by and would also close #35

@timothypage timothypage merged commit 06c072e into master Sep 23, 2022
@mikegiddens mikegiddens deleted the feature/ror-orcid-namespaces branch March 1, 2023 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants