Prevent publishing of Dataset when global id is not registered

[sekmiller]

When a dataset is created we attempt to register a global id (for 4.0 we are supporting EZID as a provider). In the create dataset command we set a globalIdCreateTime if we successfully register the global id. the plan is to periodically resubmit - or to do so manually.

@eaquigley - what should the user see if they try to publish a dataset without a registered global id.

Also, how should we reflect this in the sample citation that we show in the dataset page when it is in draft?

[eaquigley]

@sekmiller I think the user should receive a pop up message that informs them the DOI hasn't been registered so they cannot publish yet. My one question would be, how does a user get their DOI registered if it hasn't done so automatically? I don't want to leave a user hanging.

[sekmiller]

Publish will attempt to register an unregistered dataset. If that fails the dataset will not be published.

Issue remains with posting the error message to the dataset page.

[sekmiller]

Because of the need for a dataset owner to know the DOI identifier prior to publishing and the possibility that an identifier that is unique in the database may exist in the EZID server, I implemented a "Register Dataset" Button. This allows a user to register the dataset prior to publishing (remember this only happens if the registration does not occur at create - if EZID is down at create time)

[kcondon]

This is working as described. Closing