The resource DOI field in the item form allows you to put in any DOI and does not check if the DOI resolves to anything. It might be the right choice not to verify the DOI at this stage as someone may forget to update their item when the resource DOI is minted in the future.
It looks inelegant though for the published version of the item to have a link (on the right) that doesn't resolve when someone clicks on it.
I suggest that the resolution of the DOI is verified before a hyperlink is shown to the public.
One of the first things we're looking at after the FOR code migration is references and links, so this is good timing. I will add this to the conversation.
If functionality is implemented as Alastair describes (add a non-resolving resource DOI, publish an item, link is continually checked and only shown until it resolves), I would be ok with changes to the existing behavior. I would not be in favor of any other implementation because we routinely work with authors who are in the last stages of getting their article published. The journal will provide a non-resolving DOI that we add to the published record. The link won't resolve for a few days but it will work once the journal publishes the article. Because some journals want the data published before the article, adding all the needed info to a dataset in one step allows us to wrap up a data publication while minimizing the number of back-and-forth communications with authors, asking whether the article has been published.