Avoiding duplicate DOIs when a dataset has a pre-existing DOI

[Sean-Stilwell]

Hi all,

We've set up this extension in our test environment and have been trying it out for a bit now. Some of our datasets already have DOIs and we don't want new ones to be created when we update them (or in some cases when adding new datasets). I saw #4 which I think is relevant, but is there currently a way to indicate that we don't want a new DOI for a given dataset?

Thanks in advance.

[alycejenni]

There's no nice way of doing it, but I can definitely give you some workarounds (assuming your existing DOIs are with Datacite as well)!

A new DOI should only be created for a package if there's no record of one in the doi table. If you already have a published DOI for a dataset, you could add it to that table manually (with published=true).
If you're adding a new dataset that already has a DOI, creating it in draft or private modes will prevent it getting a DOI. Once it's created, you can add the new package ID to the doi table (as above) and then set it to active/public.

Implementing a way to ignore certain datasets might be something we want to do in future, but we don't have any plans for it at the moment.