Ingest. The OAIS entity that contains the services and functions that accept Submission Information Packages from Producers, prepares Archival Information Packages for storage, and ensures that Archival Information Packages and their supporting Descriptive Information become established within the OAIS. Manifest: A file made available by the Producer to the Archive, listing a series of files intended for storage by the Archive.
Ingest. The OAIS entity that contains the services and functions that accept Submission Information Packages from Providers, prepares Archival Information Packages for storage, and ensures that Archival Information Packages and their supporting Descriptive Information become established within the OAIS. Knowledge Base: A set of information, incorporated by a person or system, that allows that person or system to understand received information. Long Term: A period of time long enough for there to be concern about the impacts of changing technologies, including support for new media and data formats, and of a changing user community, on the information being held in a repository. This period extends into the indefinite future.
Ingest. “The Ingest process covers archival activities of creating the archival information package (AIP) from the submission information package (SIP).” [2] ID P2.2 Title Ingest Producer/depositor responses Question Is there a procedure to provide appropriate responses to the Producer, at the agreed points, during the Ingest process? Purpose The purpose is to identify if the organization provides responses to the Producer at the agreed points to ensure that are no faults in communication that might lead to loss of a SIP. Notes Examples of evidence to demonstrate this can be submission or deposit agreements, process documentation, operating procedures, or evidence of responses such as reports, memos, or emails.
Ingest. Best practices for pre-‐ingest, ingest and ingest tools • Archival Storage. Available formats and restrictions for storage and different national requirements for authentication for legal purposes. • Access. Gaps between requirements for access and current access solutions. Desktop research The purpose of the desktop research was to get overall knowledge of current practices and access solutions.
Ingest. The high-level illustration of the E-ARK Ingest process consists of a number of steps (Figure 2): Figure 2: E-ARK Ingest (High-level process) SIP Reception The process by which an SIP arrives at an agreed location is outside the scope of the E-ARK project. Therefore, for the purposes of the present document we assume simply that a SIP has been received and is saved to the appropriate processing area. Quality control SIP quality7 assurance includes both manual and automated processes. It consists of:
Ingest. Subject to the exclusive assignment provisions of subparagraph (a) above, any person, whether employed by the Employer or otherwise, may operate a Computer System for the purpose of ingesting data, information or material (collectively “data”), whether for live to air operations or otherwise, including but not limited to:
Ingest. “The Ingest process covers archival activities of creating the archival information package (AIP) from the submission information package (SIP).” In Deliverable 2.1 - General pilot model and use case definition.
Ingest. 6 Part of the quality assurance when SIPs are delivered to the archive 9 Part of the quality assurance when SIPs are delivered to the archive 16 Content information is tested/reviewed manually before AIP creation to ensure that it is understandable. It is part of the quality assurance process. Archival Storage and Preservation
Ingest. 5 Fonds are created as an agreement is signed. When the SIP arrives the information in the fond are updated. 10 The processes are not ad-hoc. Every time a change is made a new AIP is generated from the previous one (defined and assessed consistently) updated with the changes and additions. SIP is regarded in this process as the very first AIP.
Ingest. 14 The designated community is only the company/client that owns the records; no other users have the right to access the records. Data Management 27 Depends on the client's request. Usually the format in the AIP is sufficient but some ad hoc conversion is required.
