Introduction

The Data Exchange Protocol for Interoperability and Preservation (DEPIP) aims at facilitating inter-operability between a digital archive and information systems of its partners: producers who have created the documents themselves (Originating Agency), intermediaries who are acting on behalf of producers and are not responsible for the intellectual content per se (Transferring Agency), consumers (Consumer) and control authorities (Control Authority). This document provides a framework for data exchange between systems. It is based on the OAIS Reference model. It is generic and may be adapted to all types of information, whether printed or in a born-digital format.

DEPIP is intended for:

— commercial software vendors, in order to complete and/or improve their applications;
— archives, in order to standardize ingest of data destined for preservation; to provide access to archived data; and to facilitate the exchange of data between archives;
— application programmers, in order to enable interoperable data transactions between Archives and the information systems they are developing;
— third parties responsible for transferring documents to Archives;
— data storage service suppliers.

The parties to data exchange may rely on this document to:

— define their archiving/preservation processes or harmonize their existing processes with the best practices;
— organize the management of the archiving/preservation processes; and
— control the creation and management of metadata, whatever descriptive models are used.

Note that DEPIP may be implemented either in its entirety or only partially. However, it is impossible to foresee what the implementations will be like in different domains such as libraries, archives or museums. Domain-specific or generic International Standardized Profiles specifying different levels of interoperability may be developed in the future to support the implementers of this document. The minimum implementation, or level 0, is: Transfer and Delivery, including at least mandatory metadata. Note that in level 0, existing metadata is not redefined and that the initial request and the final reply are required.

Note that DEPIP is a conceptual standard to be considered as a data dictionary. The model defined in DEPIP is independent of implementation issues. In different implementations, DEPIP can be supplemented by relevant technical protocols (like HTTP) allowing implementers to handle technical exchanges between systems.

BS ISO 20614:2017

Information and documentation. Data exchange protocol for interoperability and preservation

Current

Published:

30 Nov 2017