Betsy Gunia (Feb 27 2026 at 21:28): Betsy Gunia (Feb 27 2026 at 21:28):Hello,
I have a dataset where over 50 people contributed to the manuscript :scream: . The depositor hasn't directly asked me to include all the authors, but as far as I can tell, there isn't a limit on number of author entries, correct? Even if there isn't a limit on the total number of authors, I would imagine there are practical reasons that one would not enter all 50 authors. If anyone has advice on this topic and what a practical limit on the number of authors should be, please let me know.
Philip Durbin 🚀 (Feb 27 2026 at 21:57):@Katie Mika opened an issue about this: #8909
Philip Durbin 🚀 (Feb 27 2026 at 22:00):She created a dataset with something like 200 authors on the beta server but I think we had to rebuild that server so that dataset is gone (or I can't find it). @Katie Mika if your script is still lying around, please let me know. :smile:
Anyway, the datasets look a little weird with that many authors. :sweat_smile:
Philip Durbin 🚀 (Feb 27 2026 at 22:00):But yeah, there's no limit.
Katie Mika (Mar 04 2026 at 19:18):Sorry for the long delay! I don't have a script handy, but I definitely used easyDataverse: https://github.com/gdcc/easyDataverse. I'm not a wizard programmer, and found that making direct API requests (via the python requests library) I kept getting the json payload format wrong for all authors file and just gave up. Jan created a great "getting started" notebook with info about loading and updating datasets here: https://github.com/gdcc/easyDataverse/blob/main/examples/EasyDataverseBasics.ipynb
Philip Durbin 🚀 (Mar 04 2026 at 19:19):Gotcha, no worries. I just remember the authors having fun names. :smile:
Katie Mika (Mar 04 2026 at 19:20):But as far as practical reasons to limit authors - I felt like there was no need to. Sure things look a little funny and metadata files are a little long, but I thought it was better to just let everyone get listed. Isn't that the point of technology!
Philip Durbin 🚀 (Mar 04 2026 at 19:33):Exactly!
Betsy Gunia (Apr 11 2026 at 01:48):Circling back on this topic. So, it sounds like the advice is to include all the authors since the system can handle it.
My only concern is that the citation will be incredibly long, and as far as I am aware, there isn't a way to have an "et al." in the citation field. Is that correct?
Philip Durbin 🚀 (Apr 11 2026 at 12:15):From an API perspective, it seems to be all or nothing: https://guides.dataverse.org/en/6.10.1/api/native-api.html#get-citation
Betsy Gunia (May 05 2026 at 21:11):Just an update on datasets with a ludicrous number of authors. While Dataverse handles the addition of many authors just fine, as expected, the ORCID lookup feature struggles to include the ORCID for the latter authors (~50).
The dataset that I used for the screen shot is currently on our demo site, which is not on the public internet. My systems admin said it is a browser/java script issue.
.
Any advice on how to get the ORCIDs to display? If the answer is to put in a ticket :smile: does the dataset in question need to be publicly accessible first?
Julian Gautier (May 05 2026 at 21:24):Hey Betsy. I can't answer most of those questions, but about making the dataset publicly accessible, I think it might be helpful to instead share the Dataverse JSON export of that test dataset you made. That might be enough to help another developer reproduce what you're seeing, by using that Dataverse JSON export to create a dataset on their local machine or on Demo Dataverse.
Betsy Gunia (May 05 2026 at 21:32):Great! We will put in a ticket later this week and include the JSON export file.
Philip Durbin 🚀 (May 12 2026 at 12:54):@Betsy Gunia thanks for opening this issue: ORCID External Vocabulary Script Fails During Long Author Lists #12392
Last updated: May 30 2026 at 09:11 UTC