ORCID (and maybe ROR) not displaying correctly in metadata tab

[Bryan Gee]

Hi folks, curious if anyone else has noticed an issue where an ORCID-linked account is not displaying the name, even though the name appears in both the dataset citation and when I go into editing mode to look:

We have noticed this for many datasets in the Texas Data Repository (6.10.1, running the CVOC for ORCID and ROR) (e.g., https://dataverse.tdl.org/dataset.xhtml?persistentId=doi:10.18738/T8/VIYPFJ) as of late last week, and this seems to extend to datasets that were not published recently (e.g., https://dataverse.tdl.org/dataset.xhtml?persistentId=doi:10.18738/T8/R9MSCP) - I don't know whether it matters how an ORCID was linked (CVOC vs. manual) so much as the CVOC is enabled.

I was trying to see if this was an issue in other installations and found that at least Harvard (e.g., https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/BQ9QPB) and QDR (e.g., https://data.qdr.syr.edu/dataset.xhtml?persistentId=doi:10.5064/F6E1OMLI) look fine, while DataverseNO also seems to have problems with the ROR display (e.g., https://dataverse.no/dataset.xhtml?persistentId=doi:10.18710/WCUCTF)

Thanks in advance!

Bryan

[Betsy]

Hi Bryan, 

We noticed this exact behavior on Tuesday, August 4th as well (6.10.1, running the CVOC for ORCID but not ROR). It was definitely working fine for us on Monday August 3rd. Our systems admin reconfigured the CvocConf settings and restarted the production instance, but the issue persisted. We were flummoxed! 

Thanks for reaching out to the Dataverse Community about it. Hopefully knowing that other instances have the same issue, will help pinpoint the problem. 

Betsy

Johns Hopkins University

https://archive.data.jhu.edu/

[James Myers]

All,

 

Sorry for the outage. I believe this is because I reorganized the dataverse-external-vocab-support repository which broke sites that were relying on getting the scripts from gdcc.github.io. I’ve temporarily restored scripts at their old location in the /scripts/js sub-folder to fix this.

 

To avoid the issue going forward, the recommended practice is to install the external vocabulary scripts locally.

 

The repository now includes deploy scripts that make local deployment simpler. See https://github.com/gdcc/dataverse-external-vocab-support/blob/main/README.md#deployment .

 

 

-- Jim

 

 

More details: When Dataverse is configured to run a script like those for ORCID/ROR, the fields from Dataverse itself are hidden (hence no author name appearing), with the expectation that the script will do its job and display the enhanced fields (e.g. author with ORCID link, etc.) When the script is not available, due to misconfiguration or, in this case, the script no longer being available from the source web server, or if a bug is introduced into the copy at the repository, the second step doesn’t happen.

 

In addition to not recommending using the hosted versions at in production, the scripts in the original locations have a warning header. Going forward, we expect the scripts in the /services subfolders to be the only ones getting bug fixes, internationalization, etc.

 

/***********************************************************************************

* WARNING: These are legacy copies of scripts now hosted under the /services folder.

*

* THEY WILL NOT BE MAINTAINED AND MAY DISAPPEAR WITHOUT NOTICE.

*

* You are advised to not use them or configure to use any scripts hosted at gdcc.github.io/dataverse-external-vocab-support

* except for testing.

*

* The current scripts, which are being maintained and updated, are under the /services directory.

* To use them, follow the new local download/install instructions in the repository readme.

*/

 

FWIW: We have been supporting use of the dataset-previewers from gdcc.github.io and are doing the extra work there to assure that old versions are never changed/moved/removed to avoid production issues. The community could potentially do this for the external vocabulary scripts as well, but no one has implemented this or agreed to support doing it long term.

 

 

 

From: 'Betsy' via Dataverse Users Community <dataverse...@googlegroups.com>
Sent: Thursday, August 6, 2026 8:51 AM
To: Dataverse Users Community <dataverse...@googlegroups.com>
Subject: [Dataverse-Users] Re: ORCID (and maybe ROR) not displaying correctly in metadata tab

 

Hi Bryan, 

 

We noticed this exact behavior on Tuesday, August 4th as well (6.10.1, running the CVOC for ORCID but not ROR). It was definitely working fine for us on Monday August 3rd. Our systems admin reconfigured the CvocConf settings and restarted the production instance, but the issue persisted. We were flummoxed! 

Thanks for reaching out to the Dataverse Community about it. Hopefully knowing that other instances have the same issue, will help pinpoint the problem. 

 

Betsy

Johns Hopkins University

https://archive.data.jhu.edu/

 

On Wednesday, August 5, 2026 at 4:51:33 PM UTC-4 brya...@austin.utexas.edu wrote:

Hi folks, curious if anyone else has noticed an issue where an ORCID-linked account is not displaying the name, even though the name appears in both the dataset citation and when I go into editing mode to look:

We have noticed this for many datasets in the Texas Data Repository (6.10.1, running the CVOC for ORCID and ROR) (e.g., https://dataverse.tdl.org/dataset.xhtml?persistentId=doi:10.18738/T8/VIYPFJ) as of late last week, and this seems to extend to datasets that were not published recently (e.g., https://dataverse.tdl.org/dataset.xhtml?persistentId=doi:10.18738/T8/R9MSCP) - I don't know whether it matters how an ORCID was linked (CVOC vs. manual) so much as the CVOC is enabled.

I was trying to see if this was an issue in other installations and found that at least Harvard (e.g., https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/BQ9QPB) and QDR (e.g., https://data.qdr.syr.edu/dataset.xhtml?persistentId=doi:10.5064/F6E1OMLI) look fine, while DataverseNO also seems to have problems with the ROR display (e.g., https://dataverse.no/dataset.xhtml?persistentId=doi:10.18710/WCUCTF)

Thanks in advance!

Bryan

--
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/c32ebd3f-4231-44b7-b7be-33e9af38d959n%40googlegroups.com.