Should users be able to modify the study global identifier when 1st creating a study?

[Eleni Castro]

Hi Dataverse Community,

We are reviewing the current Dataverse functionality in preparation for the release of 4.0 and would like your feedback on the following:

Currently, users creating a study in Dataverse are able to manually modify part of the Study Global Identifier prior to saving the study (see screenshot below of version 3.6.2). 

Do you think there are any benefits for users to be able to manually put in a different global study ID (will be called Dataset Identifier in 4.0) or should the system just automatically generate / mint one for them? We already have an Other Identifier element that users can put in a different identifier that corresponds to the same study.

Thanks for any feedback you can offer.

Cheers,

Eleni

-- 

Eleni Castro
Research Coordinator, Data Acquisition and Archiving, Data Science
IQSS, Harvard University
http://www.iq.harvard.edu/people/eleni-castro 

[Jon Crabtree]

Eleni

We used that feature to sync our legacy id numbers that had useful meaning. 

As you say we could have used the other id but we did not use that option years ago when we moved to the VDC then DVN

I can see arguments either way

Jon

--
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/8a7af41a-69b2-42ef-821f-f06ab67da54e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[August Muench]

I think it should be retained so long as it doesn't cause a problem with uniqueness. Like bit.ly custom links. 

I also conceptualize "Other ID" as linking to extant links. In that regard, a user modifying this field is probably looking for new, custom link that they couldn't easily/immediate/on publication any other way. 

[Jon Crabtree]

Eleni

We used that feature to sync our legacy id numbers that had useful meaning. 

As you say we could have used the other id but we did not use that option years ago when we moved to the VDC then DVN

I can see arguments either way

Jon

On Apr 17, 2014, at 10:47 AM, Eleni Castro <posix...@gmail.com> wrote: