search

LibraryOfCongress / bagger

The Bagger application packages data files according to the BagIt specification.
Other
120 stars 19 forks source link

suggested feature enhancement to future version of Bagger #17

Closed houzanme1 closed 8 years ago

houzanme1 commented 8 years ago

This is just a suggested feature enhancement: When a created bag is tempered with such as deleting a few files from the "data" folder, Bagger correctly identifies the files that are missing and lists them upon bag validation. That's very helpful in identifying exactly where the issues are.

Now the suggested feature: Suppose the Hash values (MD5 or SHAx) are tempered with, either in the manifest-.txt and/or the tagmanifest-.txt files, it would be helpful to know exactly which files are affected that are in the "data" folder.

The idea is to not reject a whole bag when one or two items are tempered with or became corrupt.

johnscancella commented 8 years ago

@houzanme1 Please provide an example of the expected behavior as it is not exactly clear what you are suggesting. For example: given a bag that has one file corrupt in its data directory when bagger is used to verify it lists the one file that is corrupt. Or: step 1 - create a bag step 2 - modify manifest-MD5.txt changing one of the hashes and save step 3 - open bag in bagger step 4 - verify bag expected output - bagger displays only files that are corrupt.

johnscancella commented 8 years ago

Bagger 2.4 already does this, see screenshot screen shot 2016-02-05 at 2 47 43 pm

houzanme1 commented 8 years ago

My apologies, John. That is the same outcome I got this time. So, you are right, it does correctly list the files tempered with. Perhaps I looked at a different result. Tibaut

johnscancella commented 8 years ago

@houzanme1 no problem, it happens!