Bagging


Bag Structure


\----[custom_tag_dir]/

    |    [custom tag files]

Manifests

Tag Manifests

Custom Tag Files

As of March 29, 2016, we preserve all tag files, except bagit.txt, which will be recreated when you restore a bag. Custom tag files may be in any format, including binary. We will not try to parse them, but we will validate their checksums if they are listed in the tag manifests.

Required Tag Files

bagit.txt 


This is requited by the BagIt specification, and should contain the following:


BagIt-Version:  0.97

Tag-File-Character-Encoding:  UTF-8

bag-info.txt file


Valid APTrust bags MUST contain a bag-info.txt file with the following fields, which may be blank:


Source-Organization:  This should be the human readable name of the APTrust partner organization.

Bagging-Date: as per specification using ISO 8601 UTC format.

Bag-Count:  as per specification

Internal-Sender-Description:  [Optional] Human readable description of the contents of the bag.

Internal-Sender-Identifier:  [Optional] Internal or alternate identifier used at the senders location.


This file MAY contain additional fields.

aptrust-info.txt


This file MUST be present and MUST contain the following tag fields.


Title:  Human readable title for searching and listing in APTrust.

Access:  One of three enumerated access conditions.  [“Consortia”, “Restricted”, “Institution”]


Note on Bag Serialization


Bags serialize for use by APTrust must use TAR as their serialization format, MUST not use compression and MUST follow the file and folder naming restrictions as well as end with the .tar extension.


Note on Bag Size

Initially bags sent to APTrust should be limited to 250 GB for the final tarred bag.  Space available for temporary file processing puts a practical limit on total bag sizes in APTurst.  We expect this limit to grow over time but the initial performance data will help determine the final limits for the service.


Updated on Apr 1, 2016 by Andrew Diamond (Version 5)