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. | ||
− | + | *Archivematica differentiates between mandatory and optional bag elements so that if optional elements are not present the bag does not fail the verification micro-service. | |
− | *The BagIt checks | + | *The BagIt checks generate log files that will be added to the ''logs'' directory of the transfer. |
− | *The BagIt file manifest (manifest-sha512.txt) | + | *The BagIt file manifest (manifest-sha512.txt) is 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. | *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 | + | *No new PREMIS events are required. The BagIt checks are recorded as a fixity check in PREMIS. |
==Workflow== | ==Workflow== |
Revision as of 16:53, 2 April 2015
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.
- Archivematica differentiates between mandatory and optional bag elements so that if optional elements are not present the bag does not fail the verification micro-service.
- The BagIt checks generate log files that will be added to the logs directory of the transfer.
- The BagIt file manifest (manifest-sha512.txt) is 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 are 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.