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:
Are you thinking about creating a pull request for this issue?
Not at this time
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:
Are you thinking about creating a pull request for this issue?
Not at this time