Ramverket ESSArch stöder er i era funderingar från idéstadie till fullskalig lösning för digital långtidslagring ...

En introduktion till bevarande, digital långtidslagring och elektroniska arkiv ...

ESSArch Ingest

Ingest is the archive interface to Producer whether PreIngest is used or not. The purpose is to receive information packages, prepare them for long-term preservation and store them in a secured environment. Submission Agreement regulates how it should be done and all the neccessary steps to fulfil the agreement are designed on the basis of that.



Ingest process is based on 7 steps. Together they secure and prepare the archived information to be stored for long-term preservation. First we receive the information package SIP either direct from Producer or preferably from PreIngest. We do a quality check to control if the SIP is delivered as expected and not altered during transportation. If the SIP fulfils our criterias for validation and verification it is taken care off and a receipt is sent to the shipping interface, preferably PreIngest. If the SIP not qualifies for the archive, it will not be processed further and the receipt will explain why.

As the qualification process succeds the SIP is extracted in the module AIP Creator and reformed into an Archival Information Package, AIP. The structure for the AIP is defined in Submission Agreement as well. When the SIP is extracted and the package information is divided into several parts descriptive information is added as metadata into the new package, AIP.

After the AIP is created another quality check occurs in order to fulfil the requirements for Archival Storage. Different storage methods are used and they have different profiles and policys. The quality check qualifies the AIP and stores it according to selected storage method.

At the same time the AIP is stored to Archival Storage, information about the package are updated in Data Management, DM, the information services for all stored archival objects. Data Management also keeps track of all events related to the archived object. If anything happens to the object during process, it is registered as events in DM.

During the whole Ingest process several receipts from different modules are managed in order to handle exceptions and notify management. Finally, the AIP are stored and are now considered to be in the core of the archive and available at request.

Theme provided by Danetsoft under GPL license from Danang Probo Sayekti