Custom code for dataverse.harvard.edu and an issue tracker for the IQSS Dataverse team's operational work, for better tracking on https://github.com/orgs/IQSS/projects/34
5
stars
1
forks
source link
HDV deposit validations: some validations to help with management of HDV production #281
In brainstorming ways to help prevent publishing of nondata deposits, some validations that would assist the curation team in reviewing content to meet our already limited data deposit guidelines
1- when a dataset deposit only contains one file--prevent publishing, send it for review (established collections should not have this validation)
2-when a dataset deposit contains "only one" file, and that file is a "pdf" - prevent publishing, send it for review ((established collections should not have this validation)
3 - Are we able to discern automatically when an author deposits more than one dataset into root and send a prompt that ask them to "pause deposits" and create a collection?
In brainstorming ways to help prevent publishing of nondata deposits, some validations that would assist the curation team in reviewing content to meet our already limited data deposit guidelines
1- when a dataset deposit only contains one file--prevent publishing, send it for review (established collections should not have this validation) 2-when a dataset deposit contains "only one" file, and that file is a "pdf" - prevent publishing, send it for review ((established collections should not have this validation) 3 - Are we able to discern automatically when an author deposits more than one dataset into root and send a prompt that ask them to "pause deposits" and create a collection?