Sip Format

SIP format in general

Every SIP to be consumed by ARCLib must respect following general rules:

• SIP is a .zip file which contains exactly one root folder and no files
• SIP must either contain a metadata file with Authorial ID of the SIP expressible using XPath 3.1 or the explicit linkage file (see ingest workflow)

The ability to support various SIP formats is based mainly on the ARCLib sip profiles.

SIP with one main METS file

Most of the currently supported SIP formats contains one main METS file which describes the whole package and contains (in addition to the descriptive and administrative metadata) checksums for all files. In this case, the packageType JSON config of the Fixity checker is set to METS.

SIP with multiple METS files (or with no METS files)

If the SIP package does not contain one main METS file describing the whole package, it may still be persisted into ARCLib, however the Fixity checker task may be limited as it can't extract checksums from the main metadata file. One possible solution is to wrap the input package into BAGIT format. See the Fixity checker documentation for more information.