Auto-population of author names on new dataset does not bring up orcid nor ROR

[Frank smutniak]

When creating a new dataset the author name is pre populated but without orcid and ROR. If the user is required to type in a name then orcid and ROR will render properly as we do have CVocConf set up.  We are running 6.10.1. Is there any way to suppress auto-population so the author is forced to start typing a name and affiliation or is there a better way to handle this?

thanks

[James Myers]

Not currently. You can configure so that users can associate their ORCID with their account. If they do that, Dataverse will autopopulate with their ORCID.

--  Jim

Get Outlook for Android

---

From: dataverse...@googlegroups.com <dataverse...@googlegroups.com> on behalf of Frank smutniak <fsmu...@gmail.com>
Sent: Friday, April 17, 2026 11:05:54 AM
To: Dataverse Users Community <dataverse...@googlegroups.com>
Subject: [Dataverse-Users] Auto-population of author names on new dataset does not bring up orcid nor ROR

 

When creating a new dataset the author name is pre populated but without orcid and ROR. If the user is required to type in a name then orcid and ROR will render properly as we do have CVocConf set up.  We are running 6.10.1. Is there any way to suppress auto-population so the author is forced to start typing a name and affiliation or is there a better way to handle this?

thanks

--
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 view this discussion visit https://groups.google.com/d/msgid/dataverse-community/70f4f489-1cce-42cb-abd9-e0178eb7176bn%40googlegroups.com.

[Julian Gautier]

Hey Frank,

Just reposting what I shared in the Zulip thread you started:

Some of the design challenges you've described are also included in an evaluation that my colleagues and I and other folks in the Dataverse community shared in a Google Doc in another Google Groups thread last August, especially in two tables in the "Next Steps" section that lists reasons why a Dataverse repository might not have recorded ORCIDs and RORs for author names:

"The Harvard Dataverse repository filled the Author Name field with information from the user’s account, that account didn't include an ORCID, and the user didn’t know they could use the field to find and select the name from the field’s suggestions so that the repository would include a ORCID"

"The Harvard Dataverse repository filled the Author Affiliation field with information from the user’s account, user accounts don’t include RORs, and the user didn’t know they could use the field to find and select the organization from the field’s suggestions so that the repository would include a ROR"

The report builds on usability testing and benchmarking we did for Harvard Dataverse, but it's really helpful to hear that folks managing other Dataverse repositories have noticed similar things.

I'm pushing in the coming months to revisit and iterate on these designs, in an effort we'll be tracking in the GitHub issue at https://github.com/IQSS/dataverse-pm/issues/473 as part of our NIH-funded work at Harvard, and it would be incredibly valuable for us to collaborate 🙏

I'll also be talking more about this in one of the Thursday presentations during the Dataverse Community Meeting, in case you and other folks reading will be in Barcelona 🏖️