Bethany Seeger (Jan 07 2026 at 22:09): Bethany Seeger (Jan 07 2026 at 22:09):Hello,
(dataverse 6.6)
We just uploaded/ingested some material into a new collection. When we published it, we are seeing a License/Data Use Agreement (DUA) popup in the previewer section of a files page - even when it's a CC0 file. We did put some material in the "Restricted Files + Terms of Access" section - putting the word "Public" in "Terms of Access for Restricted File".
Does putting anything in this field made the "Request Access" active?
I'm sure we've made some metadata error along the way -- just not sure what it was and how to fix it.
Here's a record: https://dataverse.yale.edu/dataset.xhtml?persistentId=doi:10.60600/YU/TY05NA&version=1.0
Here's the terms of use config page:
Ideally we would not get a pop up for a DUA at all for anything in this collection (even the non CC0 records).
Thoughts?
Thanks in advance!
Bethany Seeger (Jan 07 2026 at 22:16):noting I saw this email thread: https://groups.google.com/g/dataverse-community/c/vXxyexUASoI/m/oqIHv1xpBAAJ
Not sure if it is still applicable or not.
Philip Durbin 🚀 (Jan 08 2026 at 14:49):Yes, the popup is normal in this case. There are terms that must be agreed to before the file can be previewed.
"If a preview tool for a specific file type is available, the preview will be created and will display automatically, after terms have been agreed to or a guestbook entry has been made, if necessary." -- https://guides.dataverse.org/en/6.9/user/dataset-management.html#file-previews
Bethany Seeger (Jan 08 2026 at 14:56):Thanks, Phil. So technically speaking, anytime you put anything in the "Terms of Access for Restricted Files", you'll get the popup? (regardless of actual license type)
The UI won't let me take out the popup via the edit terms page (it's grayed out). How can I clear that "Terms of Access for Restricted Files" field?
Philip Durbin 🚀 (Jan 08 2026 at 14:58):Right, same for downloads, not just previews. The popup will be shown.
Philip Durbin 🚀 (Jan 08 2026 at 14:59):Hmm, I see what you mean, how it's grayed out:
Philip Durbin 🚀 (Jan 08 2026 at 15:05):Seems like a bug. Can you reproduce it on https://demo.dataverse.org ?
Bethany Seeger (Jan 08 2026 at 15:21):I just tried this out there and not sure if it worked or not. I did this manually -- created the dataset and choose CC0, then added a few files. The txt file preview is failing, so I can't tell if it would have shown a popup:
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/0BEISU
When I look at the terms of the dataset, I do see the same boxes grayed out -- and I didn't change anything there. Maybe this is normal? Maybe I'm just missing something...
Philip Durbin 🚀 (Jan 08 2026 at 15:23):Not sure. I asked in Slack and Jim had this suggestion:
"One possibility: Those a greyed when there are no restricted files. Perhaps a bug to not let you clear it, but the work-around would be to mark a file restricted, make the change, and then unrestrict it."
Bethany Seeger (Jan 08 2026 at 15:30):Ok - that makes sense -- just tried it out on our staging server and it worked.
So the system thinks the files are unrestricted, but because we put a string in that terms field, the system also thinks we need the popup.
Because they are not restricted, those fields are grayed out and we can't edit them.
Philip Durbin 🚀 (Jan 08 2026 at 15:30):Sounds like a bug, right? Do you mind opening an issue?
Bethany Seeger (Jan 08 2026 at 15:31):Was just typing about that -- yeah it does sound like a bug - a minor one. I'll open an issue. Thanks so much for your help.
Philip Durbin 🚀 (Jan 08 2026 at 15:32):No problem! Thanks to Jim for the workaround!
Philip Durbin 🚀 (Jan 09 2026 at 16:22):Thanks for creating https://github.com/IQSS/dataverse/issues/12080 !
Bethany Seeger (Jan 09 2026 at 16:23):Thanks for noting it here -- I meant to come back and do that, and then forgot because I did it at the end of the day.
Philip Durbin 🚀 (Jan 09 2026 at 16:25):That's what unread messages are for. :smile:
Julian Gautier (Jan 12 2026 at 13:54):Hey all.
Would it also be possible to adjust the Native API endpoint that Bethany used to remove or reduce the chance that datasets can get in this state, where there's something in the "Terms of Access for Restricted File" field but there's no restricted files? Maybe if the dataset doesn't have restricted files, but there's anything in the "Terms of Access for Restricted File" field, the API endpoint returns an error that the dataset has no restricted files, so the "Terms of Access for Restricted File" field must be blank?
@Bethany Seeger, you wrote that ideally people wouldn't see a pop up for a DUA at all for anything in this collection (even the non CC0 records). Could you write more about why you'd prefer that people didn't see a popup when they try to preview a file in a dataset in this collection?
Philip Durbin 🚀 (Jan 12 2026 at 13:57):@Julian Gautier yes, good idea
Bethany Seeger (Jan 14 2026 at 14:11):Hi Julian - I think tweaking that API call is a good idea, to prevent this scenario.
I'd like to talk with the stakeholder more about the popup and then will get back to you. I want to make sure I underestand what she expected before representing it here. Thanks!
Last updated: Apr 03 2026 at 06:08 UTC