...
The structure of the AIP will look similar to this example below:
| Code Block |
|---|
AvalonCollection-76dd330d-bc61-4182-b339-04c3d8f78cc4 |
...
├── bag-info.txt |
...
├── bagit.txt |
...
├── data |
...
│ ├── logs |
...
│ │ ├── fileFormatIdentification.log |
...
│ │ ├── filenameCleanup.log |
...
│ │ └── transfers |
...
│ │ └── AvalonCollection-252f53a9-0bad-4fb1-931e-012fac618167 |
...
│ │ └── logs |
...
│ │ ├── fileFormatIdentification.log |
...
│ │ └── filenameCleanup.log |
...
│ ├── METS.76dd330d-bc61-4182-b339-04c3d8f78cc4.xml |
...
│ ├── objects |
...
│ │ ├── assets |
...
│ │ │ ├── agz3068a.wav |
...
│ │ │ ├── lunchroom_manners_512kb.mp4 |
...
│ │ │ ├── lunchroom_manners_512kb.mp4.structure.xml |
...
│ │ │ ├── lunchroom_manners_512kb.mp4.vtt |
...
│ │ │ ├── OrganClip.high.mp4 |
...
│ │ │ ├── OrganClip.low.mp4 |
...
│ │ │ └── OrganClip.medium.mp4 |
...
│ │ ├── Demo_Manifest.csv |
...
│ │ ├── metadata |
...
│ │ │ └── transfers |
...
│ │ │ └── AvalonCollection-252f53a9-0bad-4fb1-931e-012fac618167 |
...
│ │ │ └── directory_tree.txt |
...
│ │ └── submissionDocumentation |
...
│ │ └── transfer-AvalonCollection-252f53a9-0bad-4fb1-931e-012fac618167 |
...
│ │ └── METS.xml |
...
│ ├── README.html |
...
├── manifest-sha256.txt |
...
└── tagmanifest-md5.txt |
Interim storage location
At this point in the workflow, Archivematica continues to process the AIP and store it in the desired storage location. Copies are sent to a watched folder to be picked up by Avalon and processing continues, relying on the included Manifest.csv file to add metadata and establish connections between the files.
...