Difference between revisions of "Bag ingest"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
==Requirements== | ==Requirements== | ||
*All standard Bagit checks are run: verifyvalid, checkpayloadoxum, verifycomplete, verifypayloadmanifests, verifytagmanifests. | *All standard Bagit checks are run: verifyvalid, checkpayloadoxum, verifycomplete, verifypayloadmanifests, verifytagmanifests. | ||
| − | *The BagIt checks should generate log files that will be added to the ''logs'' directory of the transfer | + | *The BagIt checks should generate log files that will be added to the ''logs'' directory of the transfer. |
| − | *The BagIt file manifest ( | + | *The BagIt file manifest (manifest-sha512.txt) will be placed in the '' metadata'' directory of the transfer. |
| + | *The other BagIt files (bag-info.txt, bagit.txt, tagmanifest-md5.txt) will be placed in a ''logs/BagIt'' directory. | ||
*No new PREMIS events are required. The BagIt checks will be recorded as a fixity check in PREMIS. | *No new PREMIS events are required. The BagIt checks will be recorded as a fixity check in PREMIS. | ||
Revision as of 11:29, 12 April 2012
Main Page > Development > Development documentation > Bag ingest
Feature description
Archivematica accepts transfers packaged in accordance with the Bagit specification.
Requirements
- All standard Bagit checks are run: verifyvalid, checkpayloadoxum, verifycomplete, verifypayloadmanifests, verifytagmanifests.
- The BagIt checks should generate log files that will be added to the logs directory of the transfer.
- The BagIt file manifest (manifest-sha512.txt) will be placed in the metadata directory of the transfer.
- The other BagIt files (bag-info.txt, bagit.txt, tagmanifest-md5.txt) will be placed in a logs/BagIt directory.
- No new PREMIS events are required. The BagIt checks will be recorded as a fixity check in PREMIS.
Workflow
In this workflow diagram, the white ovals are manual steps and the grey ovals are automated steps.
