Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curator, Depositor
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 making it possible for users to add ORCIDs to most types of accounts, except ORCID accounts of course. See user guides section and pull request that added this functionality. Then when they create datasets, Dataverse adds those ORCIDs to the dataset deposit forms' Author fields.
We'd like to increase the number of users who add ORCIDs to their accounts, particularly before they create datasets, so that those ORCIDs are added to the datasets they create, increasing the number of datasets where ORCIDs are used to describe who's contributed to the datasets.
What existing behavior do you want changed?
This is existing behavior for users of the JSF version of Dataverse and may not (or may not yet) reflect existing behavior of users of the Modern UI
While a user is creating an account, the form lets them add their ORCID, so that they don't have to first create an account, and then add an ORCID to it.
This might be done by applying Dataverse's controlled vocabulary functionality to fields on the account creation page, although currently the page has two name fields, one for given name and one for family name, and we've usually used the controlled vocabulary functionality to look up terms as users type them in single fields.
Resolving this issue could also let users more easily add names that are organizations and wouldn't have given names and family names.
We might do this by changing the two name fields on the account creation page to a single name field, or by adding some interaction that lets users change the two name fields to a single name field.
We might also experiment with ways to use the controlled vocabulary functionality to have fields on Dataverse forms suggest terms from the ORCID database when the user wants to add a person's name or from the ROR database when the user wants to add an organization's name. See gdcc/dataverse-external-vocab-support#58
Any open or closed issues related to this feature request?
Screenshots
The form users of the JSF version of Dataverse see when creating accounts, which includes a field for given name and a field for family name.
Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curator, Depositor
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 making it possible for users to add ORCIDs to most types of accounts, except ORCID accounts of course. See user guides section and pull request that added this functionality. Then when they create datasets, Dataverse adds those ORCIDs to the dataset deposit forms' Author fields.
We'd like to increase the number of users who add ORCIDs to their accounts, particularly before they create datasets, so that those ORCIDs are added to the datasets they create, increasing the number of datasets where ORCIDs are used to describe who's contributed to the datasets.
What existing behavior do you want changed?
This is existing behavior for users of the JSF version of Dataverse and may not (or may not yet) reflect existing behavior of users of the Modern UI
While a user is creating an account, the form lets them add their ORCID, so that they don't have to first create an account, and then add an ORCID to it.
This might be done by applying Dataverse's controlled vocabulary functionality to fields on the account creation page, although currently the page has two name fields, one for given name and one for family name, and we've usually used the controlled vocabulary functionality to look up terms as users type them in single fields.
Resolving this issue could also let users more easily add names that are organizations and wouldn't have given names and family names.
We might do this by changing the two name fields on the account creation page to a single name field, or by adding some interaction that lets users change the two name fields to a single name field.
We might also experiment with ways to use the controlled vocabulary functionality to have fields on Dataverse forms suggest terms from the ORCID database when the user wants to add a person's name or from the ROR database when the user wants to add an organization's name. See gdcc/dataverse-external-vocab-support#58
Any open or closed issues related to this feature request?
Screenshots
The form users of the JSF version of Dataverse see when creating accounts, which includes a field for given name and a field for family name.
