...
Persistent identifiers (PID) could will be used for all archive archival packages on the indexing levels Work and Publication Event, and reference each otherwork, archival collection and data object to provide the respective references. In this way, clear relationships of the data packages to each other and to a superordinate are possible. That means, in In each AIP the metadata (according to FIAF D7) Manifestation/Item Physical Description as well as the core metadata for the identification of the work are represented in form of the minimum set EN 15744. These The metadata will be searchable via a user interface.
As part of the long-term archiving strategy of the SDK -ZIB project, the metadata will be automatically extracted from the SDK internal Adlib database and written to a metadata file in METS format, which comprehensively describes the data package. METS is the established standard for in the long-term archiving community to capture structures and descriptive information.
The METS format mentioned above serves as a container in which the metadata added to the archive package, which may be in different formats, can be compiled. For the optimal integration of the mentioned data into the METS these are supposed to be available as serialization in XML.embedded.
Each METS container in a data package contains perspectively
...
Persistent identifiers make it possible to transfer individual parts of e.g. a restoration event to the long-term archiving with a time lag archive without losing the relationships between the individual parts. The PID system is not operated in a proprietary system within the institution, but outside the archive on the web. The use of established standards and an openness to other identifier systems promotes broad acceptance in the community. Through an identifier system, the work and manifestation , colection or item technical metadata are also visible to the outside world.
A user interface allows research in the metadata on all recorded levels. A PID system with standardised core metadata has great potential to become a kind of union catalogue of institutions collecting AV materials. The search on the interface of the PID system then leads, for example, to the much more extensive metadata of the SDK database on its website. The relation of the metadata in the PID system to the data packages in the long-term archive and to the SDK database are preserved by the issued persistent identifiers. Using this reference, it will also be possible to request individual parts of a publication event from the digital long-term archive.
Tasks:
1: Analysis of potential identifier systems (PIDs) for film.
(EIDR, ISAN, Wikidata, Handle, DOI, ...)
After the research at film institutions and direct price requests from suppliers, a comparison of the advantages and disadvantages will be done, taking into account (inter-) national handling and practice. The requirements for a PID system are defined and a decision matrix will be created.
2: Cost calculation PID system.
Some of the PID systems to be evaluated cause considerable costs. For the estimation of the arising costs, an extrapolation is made on the basis of the number of objects to be referenced.
3: Metadata of the Identifier System.
...
EBUCore is a widespread, active and accepted international metadata standard for media assets. It is therefore very well suited as a target format for technical as well as decriptive metadata to be stored with the archive packages. However, since the filmographic data from EN 15744 is a uncomplicated and small set, it can also be fitted in EBUCore. EN 15744 is implemented in EBUCore according to the specifications and is not changed. An additional publication event is added to the metadata set, which is extracted from the manifestation fields in the SDK Adlib system. The publication event can be used to assign items to a manifestation. The work, the publication event and the item each receive a PID.
42: Building a test system for research
Based on the selected PID handle system a test data set with the metadata fields defined in task 3 1 is developed.
Costs and effort for this vary depending on the selected PID system and will be determined in the course of the project in task 2.
53: Interface PID system and Adlib database:
...