-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request/Idea: BagIt Support - Add automatic checksum validation on upload #8608
Comments
@shlake - FWIW: my understanding right now is that the import is for vanilla Bags (in particular, no OAI-ORE file describing the dataset), not ones generated by Dataverse (which have the issue you describe and also contain file metadata that is not in a vanilla Bag.) |
We had a first attempt at the UI to provide feedback to the users when uploading BagIt packages.
Here is an screenshot for when we find errors in the checksums: |
Created a draft PR to start the conversation about the implementation. |
A demo of the functionality and a AWS environment has been shared with a group from the |
The final implementation is ready for review. PR: #8677 |
Overview of the Feature Request
Add automatic checksum validation if the file uploaded to Dataverse is in BagIt format.
Upon file upload, we will detect if it is a Bag and perform file checksums against the Bag manifest.
If there are checksum errors, we will display a warning message to the end-user.
UI changes still to be discussed.
What kind of user is the feature intended for?
Curator and Depositor
What inspired the request?
As part of the Harvard Data Commons project there is a requirement to add support for BagIt. The first iteration is to simply inspect the manifest files and perform a file validation when a new deposit is made.
What existing behavior do you want changed?
We want to enhanced the upload functionality to add the file validation based on the BagIt manifest.
Any brand new behavior do you want to add to Dataverse?
No
Any related open or closed issues to this feature request?
N/A
The text was updated successfully, but these errors were encountered: