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

[ehbedford]

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.

[northgardner]

This is a challenge for using Manifold for journal publishing. The best practices linked to above by @ehbedford are from DataCite. DataCite is one of two major DOI registration agencies used for textual works in North America. The other is Crossref, through which NYU Libraries offers DOIs. Crossref's guidelines for landing pages are very similar to DataCite's, but do not specify that the fulltext content cannot appear on the landing page. I actually think that DataCite would allow for this too—see a DataCite blog post where they write that for blog posts, "the landing page for the DOI also contains the fulltext of the post." The important point is that the DOI should not resolve to a PDF or data file, but rather to a web page that serves at the landing page.

The main points from these two sets of guidelines are the same:

1. The landing pages should contain the full bibliographic information: so that the user can verify they have been delivered to the correct item
2. The landing page should contain the DOI
3. The landing page should provide a way to access the item/content

To make Manifold compatible with these guidelines, there would have to be a way to display the bibliographic metadata directly at the text/article level—ideally at the top of the page.

I'm afraid this issue may limit Manifold's use for journals for some publishers, including us.