Although the OAIS reference model recognizes the need for an interim agreement between the manufacturer and the archive, the model does not describe it in detail. However, there is a separate methodology that defines and structures the relationships and interactions between an information producer and an archive. The producer Archive Interface Methodology Abstract Standard (PAIMAS) which defines the methodology of the structure of the required actions from the first date of contact between the producer and the archives until the receipt and validity of the information objects by the entity The Ingest (220.127.116.11) in an akzepden OAIS of SIPS, which performs on them and generates an AIP. Qs may include control totals or cyclical redundancy tests. If the SIP transmission is flawed, Ingest requires a new transmission. Ingest then converts SIPs into AIPs, which could include file format conversion, reorganization, transmission to different media, etc. ”An OAIS is not always necessary to keep the information provided to it in the exact format as in the SIP” (4.3.2). At least a unique identifier is added. SiPs are sent to the OAI archives by producers. Producers are authors, organizations or even programs that provide materials to the OAIS.
Some submissions do not have representation information or Preservation Description to meet the strict requirements of the AIP, which means they may not necessarily be PIAs. Effective data extraction/records/files based on the data selection profile defined in the agreement process. Depending on the conditions of the source system, this process can be tedious and can often result in unforeseen costs, especially for extracting data from legacy it-systems. The ”achievements” resulting from the application of the PAIMAS methodology are agreements on conservation principles, technical tolerances, package structures, processes and regulations. In addition, the organizational needs and funding of everything are identified, defined and quantified. The SIP is prepared for deposit and forwarded to the archives that receive it. ESSArch supports transmissions from the same instance and remote instances. Ideally, there should be a bidding agreement between the manufacturer and OAIS, setting criteria such as file formats, themes, registration plan, access restrictions, verification minutes, etc. (2.3.2). ”A significant iteration may be necessary to agree on the exact information to be transmitted and to put it in forms acceptable to the OAIS” (3.2.1). They also have to negotiate legal aspects, for example.
B the power to migrate content information to new presentation forms (3.2.2).