Generate DOIs for templates using DataCite

[martinjoconnor]

Generate DOIs for templates using DataCite

[graybeal]

Waaait. your visual is the Publish action, but the thing that makes CEDAR artifacts publicly visible is Enable OpenView. Currently, there is no dialog when that option is selected.

[martinjoconnor]

Ooops - you are right. Will correct.

[graybeal]

Note that typically people who generate DOIs think of the DOI as the primary identifier of the Digital Object (DO). (That was more or less the stated purpose of DOIs.) So in some sense, it competes with the CEDAR identifier as the primary identifier of the CEDAR artifact. I don't think this is a major issue, most people/projects will pick one and not the other consistently, and DOI doesn't enforce/expect that interpretation.

Nonetheless, it's worth being aware that the CEDAR identifier will resolve (should resolve?) to an actual entity inside CEDAR, if the user has permission. Whereas the DOI will resolve to the CEDAR OpenView of the entity, which in turn lets you access the CEDAR entity (again, if you have permission).

Do we need to question our assumption that the DOI should resolve to the public view of the CEDAR artifact? The DOI documentation says a DOI "takes you to one or more current URLs or other services related to a single resource", whereas Wikipedia says it should resolve to "the information object to which the DOI refers.", and in CrossRef they resolve DOIs to "a response page containing no less than complete bibliographic information about the target content". So I guess we get to decide what these DOIs that we create will resolve to.

One option would be for CEDAR to be smart enough to test a CEDAR identifier to see if the user has access to it; and if they do not, send them to a publicly viewable page, assuming it exists. Then if we require all DOI'd CEDAR entities have OpenView enabled, all DOIs would resolve to the internal CEDAR view for people with access, and the public view for others.

In the end that may be more confusing than good—it's making the resolution target consistent, but creating slightly inconsistent behavior for some cases for a CEDAR user.