I’m getting close to having Crossref accepting DOI deposits for our three initial collection types (books, journal issues, conferences) and working on the user-facing part of this. I’m trying to figure out what we need to support here before I get too deep into building it, so without further ado here’s a proposed user flow for getting a DOI for a collection (this would be launched from the Metadata tab of the
I’m thinking this logic would be encapsulated into a small textfield/button combination widget (which itself has hooks to launch confirmation and eventually Crossref login dialogs). Ideally once this works for collections I’d like to port it over to the pub-level DOI pane.
After thinking about this for a bit, I’m not sure whether we want to support the ability to just put a completely custom DOI into the metadata field. I can see why we’d want to do this, in case the PubPub version of a collection is mirroring some other canonical version. But in the absence of supporting metadata about the collection, it’s not clear whether we can actually use this DOI in the Crossref deposit for the collection’s constituent pubs. We might have to pull down that metadata from Crossref, which sounds like a completely separate can of worms.
So what does everyone think — am I missing anything or am I good to build this?