Assigning a DataCite DOI to a Dataverse

[Courtney Mumma]

Hi all,

One of our institutional liaisons has a researcher asking if she can assign a DataCite DOI to a dataverse. The dataverse has several datasets within it with their own DOIs, but she would prefer to have a citation and DOI at the dataverse level collectively. Has anyone done this?

We also have the option of assigning a DOI externally out of the institution's own DataCite account, but it wouldn't have the same prefix as the other DOIs in the TDR Dataverse, so we'd prefer to avoid that option.

Thank you in advance,

Courtney

Courtney C. Mumma, MAS/MLIS (she/her/hers)

Deputy Director, Texas Digital Library

[Philip Durbin]

Hi Courtney,

There is no support in Dataverse for Persistent ID (PIDs such as DOIs or Handles) at the dataverse level. They can only be assigned at the dataset level (required) and the file level (optional).

That said, to support file level PIDs we moved the necessary database columns (protocol, authority, and identifier) from the "dataset" table to the "dvobject" table which is shared between dataverses, datasets, and files. I've highlighted these fields in the attached screenshot from http://phoenix.dataverse.org/schemaspy/latest/tables/dvobject.html

The thinking was that we anticipated the day would come that someone would ask, "Can we have DOIs at the dataverse level?" I guess today is that day. :)

Please feel free to create an issue about this at https://github.com/IQSS/dataverse/issues because I'm pretty sure one doesn't already exist.

Thanks,

Phil

--
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 post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAKx6RmtXE-OajMU0y%2BWPkv0_%3DsPhO30pNgyLy8xtV539w%3DOHcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

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

[Durand, Gustavo]

One of the challenged to assigning a PID for a dataverse is that the contents may continue to change. We currently, have the same issue with datasets, but have the plan to add PIDs for dataset versions to address that. There is no concept of versioning for dataverses (nor do I think we want one).

That doesn't mean we can't decide to add them (as Phil pointed out, it was a future consideration when moving the PID columns in the db, but something we would need to be aware of when implementing / documenting.

Gustavo

On Thu, Jun 6, 2019 at 11:12 AM Durbin, Philip <philip...@harvard.edu> wrote:

Hi Courtney,

There is no support in Dataverse for Persistent ID (PIDs such as DOIs or Handles) at the dataverse level. They can only be assigned at the dataset level (required) and the file level (optional).

That said, to support file level PIDs we moved the necessary database columns (protocol, authority, and identifier) from the "dataset" table to the "dvobject" table which is shared between dataverses, datasets, and files. I've highlighted these fields in the attached screenshot from http://phoenix.dataverse.org/schemaspy/latest/tables/dvobject.html

The thinking was that we anticipated the day would come that someone would ask, "Can we have DOIs at the dataverse level?" I guess today is that day. :)

Please feel free to create an issue about this at https://github.com/IQSS/dataverse/issues because I'm pretty sure one doesn't already exist.

Thanks,

Phil

On Thu, Jun 6, 2019 at 10:17 AM Courtney Mumma <courtne...@gmail.com> wrote:

--

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 post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAKx6RmtXE-OajMU0y%2BWPkv0_%3DsPhO30pNgyLy8xtV539w%3DOHcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

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

--
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 post to this group, send email to dataverse...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8EMv42wHbTjyB_Fi2%3DEcM7U6zhM14gh2%2B-duR_H5QFjxg%40mail.gmail.com.

[James Myers]

Courtney,

FWIW: As a manual option, I think you could also mint a DOI using your Dataverse DataCite credentials and prefix directly at doi.datacite.org. That would keep it consistent and ‘ready’ for when dataverses can have DOIs recorded in Dataverse itself. I think the only caveat to this is that you should check the Dataverse for the existence of the DOI you pick before you go ahead and mint it – with DataCite, DOIs aren’t registered until publication so in rare cases you may find a draft dataset DOI matching your choice. Just searching for the prefix plus unique part of the DOI in Dataverse search would do this (e.g. in QDR I search for ‘F6XBZC8A’ for example where the prefix if F6).

 

-- Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8EMv42wHbTjyB_Fi2%3DEcM7U6zhM14gh2%2B-duR_H5QFjxg%40mail.gmail.com.

[Courtney Mumma]

Thanks all -- and, yes, Phil, I'll create the ticket so we have a formal record in github. Jim - what you describe is the approach I took, but it's not an entirely elegant solution.

C

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/SN6PR04MB3808FDCAA55F0C4FFAB0746EBF170%40SN6PR04MB3808.namprd04.prod.outlook.com.

[Sherry Lake]

Hi Courtney,

Maybe not exactly what the researcher wants, but MIT (using Harvard's Dataverse) has created a "series" data set.

One example:

Indonesia. Departemen Perindustrian, 2017, "Statistik Industri *series record*", https://doi.org/10.7910/DVN/QBUWQD, Harvard Dataverse, V1

This dataset does not have any files. The description has links to the datasets that have the files. Since the series is a dataset, it gets a DOI.

--

Sherry

[Courtney Mumma]

Interesting approach, Sherry - thank you for sharing. I'll pass along that info to the TDR liaisons.

See you soon!

Courtney

--

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 post to this group, send email to dataverse...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/da81c3ab-7ab0-4698-b69b-a5e9897370f2%40googlegroups.com.

[Philip Durbin]

Courtney, thanks for opening this "DOI at the dataverse level" issue: https://github.com/IQSS/dataverse/issues/5930

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAKx6Rms15h7zpd-J6K%3DH%2Bs3OGtzX%3DEfJsdz0o6cB-iJGx6ZETw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Philipp at UiT]

This issue was just discussed at the Dataverse Community Meeting 2021.

At DataverseNO, we have minted DOIs for some sub-collections manually through DataCite Fabrica (https://doi.datacite.org/). Then we add a reference including this DOI to the description field of the sub-collection. Here you see an example: https://doi.org/10.18710/AJ4S-X394.

Best,

Philipp, UiT/DataverseNO