Apply Persistent Identifier Clause Samples

Apply Persistent Identifier. In a collection management database a single physical object can be represented by several different digital assets like images, text documents, and audio files. These assets are usually not stored in the CMS itself. Assets which can be retrieved via Internet are stored on separate servers, apart from the CMS. There should be a URL or some other form of persistent identification constructed which points to the permanent location of the asset. The ECK might have to consider the provision of PIDs also for items that are not available over the web or are only internally available through the ECK to support the process. For persistency it is preferred that the PID (URI) will be provided by the CMS and stored in Europeana or an aggregator, as it is the key for updates and deletions in Europeana from the CMS of the content provider. In case the PID is source of the PID is not the CMS the ECK will have to provide the list of published PIDs back to the institutions. Other points of references like Institutions, Collections, Object-images and Linked concepts. The construction of the permanent identifier could be based on values in specific fields in the database, but the identifiers must be independent of the aggregator and persistent identifiers must remain constant for the content provider (may not vary according to the aggregator) to avoid duplicate entries. A solution for PIDs has been suggested by the HOPE project24. The re-usability of this work has to be investigated. Also, Europeana has set up a task force to define the needs of content providers regarding PIDs and the role aggregators like Europeana play to service them25. 24 ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/ 25 ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇/web/network/europeana-tech/-/wiki/Main/Task+Force+Persistent+Identifiers