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

Text metadata display is incompatible with DOI best practices for content landing pages #3754

Open
ehbedford opened this issue May 30, 2024 · 0 comments

Comments

@ehbedford
Copy link

UW has received our first request to mint a DOI for one of our journal articles, which in theory we are happy to do. However, DOI best practices state that DOIs should resolve to a landing page, rather than the content itself. While metadata for the article does appear in the 'About this text' popup, there is no ability to link to it as its own page - I can only link to the content itself.
For the future, it would be ideal to be able to create a landing page for texts like we are able to do for resources, but instead of linking to outside files it would link to the manifold text itself. Yes, there is an ugly workaround where we can create a Link resource with a URL pointing to the text. But resources are supposed to be their own entities that exist in context with the texts, and in cases where there are actual resources associated with a project it would introduce significant confusion for the reader if both real and workaround entries were displayed in the Resources section.

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

No branches or pull requests

1 participant