...
Data Files
The data files (or, the payload of a bag) in the BagIt spec are all the files found under the data directory. If there are orphaned files (those not found in the manifest, but exist in the data directory), a bag is deemed to be invalid.
...
Tag files are all those in that exist outside of the data directory. The bagit.txt and bag-info.txt files are standard and we follow the same requirements as in the bagit BagIt specification for them.
manifest-sha256.txt
...
- We require the existence of a tagmanifest, which contains the digest of each tag file and the manifest.
- This lets us validate not only the tag files but also the manifest we were given.
- When doing bagging ourselves, we create this only if each file in the manifest has been validated
bag-info.txt
- Required for UCSD deposits.
Information listed should come from the UCSD depositor SLA.
No Format Source Organization: Organization Address: Contact Name: Contact Phone: Contact Email:bag command will add
No Format Payload-Oxum: 163450283.76 Bagging-Date: 2017-10-05 Bag-Size: 155.9 MB
Optional Tag Files
DuraspaceDuracloud Bridge:
- manifest-md5.txt
- content-properties.json
- .collection-snapshot.properties
DPN:
- dpn-tags/dpn-info.txt
- Possible other node related tag files
Each optional file is digested and added to the tagmanifest. DPN has its own constraints on the dpn-info.txt file which we conform toValidation on optional files is not currently supported.
Unaccepted Tag Files
- fetch.txt files are not accepted into Chronopolis (although legacy examples may exist)
...