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

Check whether what we say about DOIs in _Resource identifier_ and _Resource locator_ makes sense. #59

Open
PeterParslow opened this issue May 18, 2021 · 3 comments
Assignees
Labels
Elements Issue that primarily affects the GEMINI elements

Comments

@PeterParslow
Copy link
Contributor

There is a further mention of DOI in Additional information, but that is for citing the other document that contains the additional info.

@PeterParslow PeterParslow added the Elements Issue that primarily affects the GEMINI elements label May 18, 2021
@PeterParslow
Copy link
Contributor Author

For Resource identifier Guidance 4 says:
"Where present, a DOI should be recorded as a resource identifier, with the codespace being doi. If a DOI landing page is also available, then include this using an Anchor."

For Resource locator, Guidance 3 says:
"The URL of a DOI landing page should be given as a Resource locator with a CI_OnlineFunctionCode value of "information"."

Although potentially ambiguous, I read this as saying:

If your resource has a DOI & the DOI has a landing page, give it in two places: as an Anchor within the Resource identifier code sub-element AND as a Resource locator with function = information.

Do we agree that this makes sense, and that therefore no change is required?

@archaeogeek
Copy link
Member

@KoalaGeo to strengthen guidance 4 for Resource Identifier

@KoalaGeo
Copy link

KoalaGeo commented Sep 4, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Elements Issue that primarily affects the GEMINI elements
Projects
Status: For review
Development

No branches or pull requests

3 participants