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).” [58] 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. “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.
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. 27 Depends on the client's request. Usually the format in the AIP is sufficient but some ad hoc conversion is required.
Ingest. 5 If we use scopeArchive for the cataloguing system: The Fonds level is created manually by the archivist, and the needed sublevels. We select the sublevel where the collection will be created from SIP contents (units of description). We do not have enough information regarding E-ARK AIP generation yet.
Ingest. 5 The repository is able to do both ways: 1. It’s able to create fonds, collections or series based on the Producer SIP information, if this info comes within the SIP or 2. Reuses existing ones, if no other information is supplied.
Ingest. Table 18 details the results of post-assessment questionnaire questions that related to the assessment of the ingest capability of the initial assessment and evaluation. The results are shown for each of the pilots that were selected to answer the questionnaire. There were 14 questions for this capability in the initial assessment and evaluation questionnaire. For each of these questions there were five questions in the post-assessment questionnaire as detailed in Table 18.
