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

fgdc Contact Name with ORCID #109

Closed
stansmith907 opened this issue Aug 17, 2017 · 2 comments
Closed

fgdc Contact Name with ORCID #109

stansmith907 opened this issue Aug 17, 2017 · 2 comments

Comments

@stansmith907
Copy link
Contributor

The Alaska Science Center's practice of is attaching ORCID to contact name raises a few issues:

  • If a contact is to be reused elsewhere in the metadata record it must always have the same name, e.i. have the ORCID attached and in the same format. Because FGDC does not support contact IDs I must match contacts by contact name. Any variation in name will result in a new contact.
  • ORCID is being attached to the name because it is deemed important. However, I probably should not try and pluck it from the name field to create a contact identifier since this is not a universal or wise convention to attach supportive information to the name field. If we want to preserve ORCID we should find another method.
@dwalt
Copy link
Collaborator

dwalt commented Aug 18, 2017

I don't know of any other way to record ORCIDs in FGDC. We would not continue this practice in ISO. I think it is perfectly fine to leave the ORCID attached to the name as contact name. We use ORCID consistently, but this is not a universal practice in USGS. They are trappable within a string by the use of parenthesis to encapsulate the id.

@stansmith907
Copy link
Contributor Author

I'm okay with ASC to using the name field as they wish. But do not plan to scan it for ORCID as the FGDC reader is for a broad audience and will try to stay true to the standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants