Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
What inspired the request?
We want to increase the amount of ORCIDs used to describe authors and other contributors of datasets published in Dataverse repositories, to help users find datasets more easily.
One way we've done this, particularly for repositories whose managers let users create accounts and datasets, is by using the controlled vocabulary functionality (https://github.com/gdcc/dataverse-external-vocab-support) to redesign the Author Name and Affiliation fields on Harvard Dataverse's deposit form, and to encourage managers of other repositories using the Dataverse software to use the controlled vocabulary functionality to do the same.
We'd like to increase the number of users who use these redesigned fields in such a way that Dataverse is able to record each authors' ORCIDs and RORs. Through benchmarking, usability tests and unsolicited user feedback we've seen many cases where depositors have chosen what they typed into the field instead of choosing the "right" name that the field suggested, or the name we'd like them to choose so that Dataverse records an ORCID or ROR, because they didn't know that they could include other information, like the affiliation of the person they want to add as an author. So they added what they typed instead.
What existing behavior do you want changed?
A redesign of the Author Name and Affiliation fields so that more depositors are aware that they can search using more than the names of the people and organizations they want to add as authors and author affilations.
Any open or closed issues related to this feature request?
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
What inspired the request?
We want to increase the amount of ORCIDs used to describe authors and other contributors of datasets published in Dataverse repositories, to help users find datasets more easily.
One way we've done this, particularly for repositories whose managers let users create accounts and datasets, is by using the controlled vocabulary functionality (https://github.com/gdcc/dataverse-external-vocab-support) to redesign the Author Name and Affiliation fields on Harvard Dataverse's deposit form, and to encourage managers of other repositories using the Dataverse software to use the controlled vocabulary functionality to do the same.
We'd like to increase the number of users who use these redesigned fields in such a way that Dataverse is able to record each authors' ORCIDs and RORs. Through benchmarking, usability tests and unsolicited user feedback we've seen many cases where depositors have chosen what they typed into the field instead of choosing the "right" name that the field suggested, or the name we'd like them to choose so that Dataverse records an ORCID or ROR, because they didn't know that they could include other information, like the affiliation of the person they want to add as an author. So they added what they typed instead.
What existing behavior do you want changed?
A redesign of the Author Name and Affiliation fields so that more depositors are aware that they can search using more than the names of the people and organizations they want to add as authors and author affilations.
Any open or closed issues related to this feature request?
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?