Hi Taehyung,
Archivematica was built with reference to the
OAIS Reference model, which was first developed by the Consultative Committee for Space Data Systems, and has since beeen adopted as an international standard (ISO 14721). While ISO makes you pay to access its standards, the CCSDS makes a copy of the OAIS reference model freely available:
If you are new to digital preservation and Archivematica, I suggest spending some time with this standard, and looking up other explainers. Terms such as AIP, SIP, and DIP are all derived directly from the reference model. The standard includes a glossary of terms with definitions though on their own outside of context, they are fairly circular:
- Submission Information Package (SIP): An Information Package that is delivered by the Producer to the OAIS for use in the construction or update of one or more AIPs and/or the associated Descriptive Information.
- Archival Information Package (AIP): An Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.
- Dissemination Information Package (DIP): An Information Package, derived from one or more AIPs, and sent by Archives to the Consumer in response to a request to the OAIS.
Not very clear! But if you read the whole standard, it starts to make more sense. Essentially, a SIP is the content and metadata submitted for ingest into the archive, upon which various preservation actions are performed to create an AIP for long-term preservation. A DIP generally contains lower-res and more widely supported formats, and are used for access. So when you ingest content into Archivematica, you will preserve your AIP, and if you want to make a copy of the objects accessible, then Archivematica can pass a DIP to AtoM.
AtoM will extract the objects and some of the technical metadata (and descriptive metadata too, depending on your workflow in Archivematica) and append them to the target parent description, where you can add further descriptive metadata. The DIP itself is not kept by AtoM, once the objects and metadata have been extracted. However, if you have a reason to preserve your DIP, Archivematica also includes a "Store DIP" option. You can also re-ingest an AIP to generate new DIPs wherenever you need - see the Archivematica documentation for more information, and I suggest asking any follow-up questions about Archivematica functionality in the
Archivematica User Forum.
You might also find the following slide deck useful: the first part will introduce you to some basic digital preservation concepts, as well as other standards, metrics, and tools that might be of interest to you. The second part provides an overview of Archivematica, and how it can help you establish a digital preservation workflow. See:
Once digital objects are extracted from the DIP passed to AtoM from Archivematica, AtoM will store them similarly to any other digital object - that is, in the uploads directory. Technical metadata is written to AtoM's database, and it includes the unique universal identifier (UUID) for both the file, and the related AIP from which the DIP was derived. This maintains a link - a chain of custody - back to the original objects. You can use the UUID to search in Archivematica, if needed.
Slides 25 and onward in the following slide deck explain a bit more about how AtoM can be used with Archivematica to maintain a digital chain of custody:
Regards,