AIP structure

Main Page > Development > Development documentation > AIP structure

In progress.

Name

The AIP name is composed of the following:

1. Either the name of the original transfer if no new name has been assigned to the SIP upon formation or the name of the SIP or SIPs created from the transfer and
2. a UUID assigned during SIP formation

example: Images-aebbfc44-9f2e-4351-bcfb-bb80d4914112

"Images" is the name assigned by the user and "aebbfc44-9f2e-4351-bcfb-bb80d4914112" is the UUID generated during SIP formation.

Directory Structure

Figure 1 AIP directory - top level

BagIt documentation

• The AIP is packaged in accordance with the Library of Congress Bagit specification (PDF, 84KB) In Figure 1, the BagIt files are bag-info.txt, bagit.txt, manifest-sha512.txt and tagmanifest-md5.txt.

Data

Figure 2 AIP data directory

The data directory consists of the METS file and three folders: logs, metadata and objects.(See Figure 2)

• Logs: contains normalization log, malware scan log, and submission documentation extraction log generated during SIP creation. (See Figure 3 below)
• Metadata: contains a folder containing logs from each transfer that makes up the SIP. The METS file for each transfer's original order is contained within the log file for the transfer (see bottom of page at METS for Archivematica transfer).(See Figure 4 below) More information about the contents of the "transfer" file(s) and screenshots in Transfer section below.
• Objects: contains original objects, normalized objects and submission documentation. If there were any lower level directories within the SIP, that directory structure is maintained. (See Figure 5 below)

• METS file containing the full PREMIS implementation (see PREMIS metadata for original file, PREMIS metadata: normalized files, PREMIS metadata: events, and PREMIS metadata: rights

Figure 3 Logs folder content in Data

Figure 4 Metadata folder content in Data

Figure 5 Objects folder content in Data

The Transfer folder

Figure 6 Transfer(s) within the transfer folder. Note: This is a SIP made from one transfer, but it could contain many transfers that make up a SIP.

Figure 7 Contents of a single transfer. Note: there could be one or many transfers that make up a SIP

Figure 8 Contents of the logs folder within a single transfer

Figure 9 Submission Documentation folder for a single transfer