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 RORs used to describe the affiliations of authors and other contributors of datasets published in Dataverse repositories, to help users find datasets more easily.
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
We might do this by extending the design pattern we've used to increase the number of ORCIDs used to describe the names of dataset authors, particularly for datasets in repositories whose managers let users create accounts and datasets : A user can add an ORCID to their account, so that that ORCID is added to the datasets they create.
So a user might also add a ROR to describe their affiliation, and that ROR is added to fields of datasets they create, like the Author Affiliation field.
This might be done by applying Dataverse's controlled vocabulary functionality to the Affiliation field on the account creation page, so that as users start typing, the field suggests names from the ROR database. And when the user chooses a suggested name, Dataverse adds that ROR to the account creator's affiliation.
Any open or closed issues related to this feature request?
Screenshots
The form that users of the JSF version of Dataverse see when creating Dataverse accounts, which includes a field for the account creator's affiliation.
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 RORs used to describe the affiliations of authors and other contributors of datasets published in Dataverse repositories, to help users find datasets more easily.
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
We might do this by extending the design pattern we've used to increase the number of ORCIDs used to describe the names of dataset authors, particularly for datasets in repositories whose managers let users create accounts and datasets : A user can add an ORCID to their account, so that that ORCID is added to the datasets they create.
So a user might also add a ROR to describe their affiliation, and that ROR is added to fields of datasets they create, like the Author Affiliation field.
This might be done by applying Dataverse's controlled vocabulary functionality to the Affiliation field on the account creation page, so that as users start typing, the field suggests names from the ROR database. And when the user chooses a suggested name, Dataverse adds that ROR to the account creator's affiliation.
Any open or closed issues related to this feature request?
Screenshots
The form that users of the JSF version of Dataverse see when creating Dataverse accounts, which includes a field for the account creator's affiliation.
