Open jerroydmoore opened 9 years ago
Thanks Jerry.
The execute bit is set on multichecksum.py on my version of the repo, so I'm surprised that it was unset on yours. Any more info you can give me would help track it down.
The data
directory is a requirement under the IETF draft of the specs, so not keeping your data in data
would not conform to the specs. See: https://tools.ietf.org/html/draft-kunze-bagit-10#section-2.1.2
Additionally, the manifest file must live at manifest-<alg>.txt
, where alg
is one of SHA1 or MD5. This is also part of the spec: https://tools.ietf.org/html/draft-kunze-bagit-10#section-2.1.3
Initiating a new bag is pretty easy. You can see how to do it in the examples/newbag.py
file.
Let me know if I can be any more help.
After installing pybagit via pip, I get the following error
After flipping the execute bit ON for multichecksum.pyc and multichecksum.py, it is able to proceed, but fails with the following:
I'm not sure how to initiate a new bag after reading the docs. It looks like it could work with existing bags, but I haven't tried it.
Additionally, is there a way to customize the data directory? I don't want all my contents living in /mycontents/data. I would like to leave my contents undisturbed as other processes require it. I would however, like a manifest file to live at mycontents/file.manifest.
Additionally, here is my PoC: