Skip to content
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

Tabular File from Ingest Included in Bag - not original Uploaded File #8449

Closed
shlake opened this issue Feb 23, 2022 · 1 comment · Fixed by #8901
Closed

Tabular File from Ingest Included in Bag - not original Uploaded File #8449

shlake opened this issue Feb 23, 2022 · 1 comment · Fixed by #8901

Comments

@shlake
Copy link
Contributor

shlake commented Feb 23, 2022

What steps does it take to reproduce the issue? When does this issue occur?
Using Bagit API.

  • What happens?
    The resultant "bag" contains the tabular ingested file .tab. The manifest-md5.txt has the md5 of the original file, not the included .tab file.

  • What did you expect to happen?
    Expected that the original data file be "bagged" not the ingested tabular file.

Which version of Dataverse are you using?
V5.9

@shlake
Copy link
Contributor Author

shlake commented Aug 5, 2022

This is still a problem in V5.11.1 with BagIt export.....

The resultant bag contains the ingested tabular file NOT the original file. Yet the manifest-md5 file has the MD5 for the original file.

It was my understanding that the original file should be bagged not the ingested one.

pdurbin added a commit to GlobalDataverseCommunityConsortium/dataverse that referenced this issue Aug 9, 2022
pdurbin added a commit to GlobalDataverseCommunityConsortium/dataverse that referenced this issue Aug 10, 2022
Also allow strings as setting keys because
:BagItLocalPath isn't in the usual enum.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant