You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: