Missing DOIs

[Guanwen Zhang]

Hi

We have two files in our dataverse which have DOIs  minted. However, somehow, these

two DOIs are not registered with datacite.org. Thus, when user click the links to URL containing these two DOIs, the redirect won't happen.

I am wondering if it is safe to create the DOIs in the datacite account manually, and providing metadata there. 

or 

if there is a way from the dataverse application to do it? We are using dataverse version 4.20.

your insights are highly appreciated.

[Philip Durbin]

I believe the "Mint a PID for a File That Does Not Have One" API is what you're looking for: https://guides.dataverse.org/en/4.20/admin/dataverses-datasets.html#mint-a-pid-for-a-file-that-does-not-have-one

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/2e9f0ac8-0077-4cb8-94f3-f87d08ef6bcdn%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[danny...@g.harvard.edu]

Thanks Phil. 

Henry - apologies for my incorrect response earlier over support email. I was looking for the PID reservation API call in the 4.20 docs and didn't find it, but these other APIs were available pre-5.0 and should be able to help you. 

- Danny

[John Huck]

Hi Phil,

I believe Henry meant to say that we have two published datasets that were somehow not registered with DataCite. Will the "Mint a PID for a File That Does Not Have One" API work for datasets as well as files?

Thanks,

John

--

John Huck, MLIS

Metadata Librarian / University of Alberta Library / he/him/his

ᐊᒥᐢᑲᐧᒋᐋᐧᐢᑲᐦᐃᑲᐣ / Amiskwaciwâskahikan / Edmonton

The University of Alberta respectfully acknowledges that we are situated on Treaty 6 territory, traditional lands of First Nations and Métis people.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/9c995ab5-3469-4ccc-aea9-2f2bf8a22689n%40googlegroups.com.

[Philip Durbin]

Ah, in that case you probably want "Send Dataset metadata to PID provider" from the same page: https://guides.dataverse.org/en/4.20/admin/dataverses-datasets.html#send-dataset-metadata-to-pid-provider

"Forces update to metadata provided to the PID provider of a published dataset. Only accessible to superusers."

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAPG0r%2Beoq4Km2mktwoH1hNDLgn7e%2BALHhF0e3%3DgXaQJiNgbn%3Dw%40mail.gmail.com.

[John Huck]

Thanks, Phil. We had looked at that. I wasn't sure if it would work, because there would be no metadata record with DataCite to modify with these unregistered items, but we hadn't tested this out to see if it would fail or not.

John

--

John Huck, MLIS

Metadata Librarian / University of Alberta Library / he/him/his

ᐊᒥᐢᑲᐧᒋᐋᐧᐢᑲᐦᐃᑲᐣ / Amiskwaciwâskahikan / Edmonton

The University of Alberta respectfully acknowledges that we are situated on Treaty 6 territory, traditional lands of First Nations and Métis people.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8F%2BZ4xntwTyLtwwc58PyOr-dr6fyX8j13fm%3DBPSf3nchQ%40mail.gmail.com.

[Philip Durbin]

Should work. If not, please let us know! :)

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAPG0r%2BcodW2X2053vM9yxpKEqVd1mrujZ4Ufq9d7iCaTe35ynQ%40mail.gmail.com.

[John Huck]

OK, we'll give that a shot. Thanks, Phil!

John

--

John Huck, MLIS

Metadata Librarian / University of Alberta Library / he/him/his

ᐊᒥᐢᑲᐧᒋᐋᐧᐢᑲᐦᐃᑲᐣ / Amiskwaciwâskahikan / Edmonton

The University of Alberta respectfully acknowledges that we are situated on Treaty 6 territory, traditional lands of First Nations and Métis people.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8EszYQ-Ah%3Daeh7BQ_t6siesKLvQjQDPBsNytbw%2BjpUOgg%40mail.gmail.com.