IQSS / IQSS/dataverse

ORCID External Vocabulary Script Fails During Long Author Lists

Open
#12,392 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

The issue
We are working with some astronomers to migrate their datasets from their existing data repository to our own Johns Hopkins Research Data Repository. They are sunsetting their current repository. We first migrated the datasets to our demo instance, which is not on the public internet. We noticed that for the datasets with over 50 authors, after we saved a dataset and went to the metadata tab, we get this funky formatting with ORCIDs.
Some of these astronomical datasets have close to 100 authors!

I've uploaded to this ticket the JSON file for this dataset on our demo instance. I haven't published it on the production instance yet.

Which version of Dataverse are you using?
v. 6.7.1 build 1955-8e18f64

JohnsHopkinsDemoDataverse_ORCID_DisplayProblem.json

Any related open or closed issues to this bug report?
Not that I could find. But I did post the issue on Zulip: #community > Limit on Authors for a dataset

Screenshots:

Image

Are you thinking about creating a pull request for this issue?
Not at this time

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the attached JohnsHopkinsDemoDataverse_ORCID_DisplayProblem.json to reproduce the metadata-tab formatting problem with a dataset containing more than 50 authors on Dataverse 6.7.1. Trace the ORCID external-vocabulary handling and verify that long author lists display correctly without the reported formatting issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.