On february 17-18 CATCHPlus participated in and contributed to the EuropeanaConnect ERDS (Europeana Resolution Discovery Service) meeting at the German National Library in Frankfurt. Aim of this meeting was to jointly formulate requirements for the Europeana "meta resolver" for the different kinds of persistent identifiers in use with participating institutions.
CATCHPlus had the opportunity to report on their experiences with formulating requirements from Cultural Heritage and Audiovisual domains, on the solution that CATCHPlus has chosen and implemented and on a number of application pilots.
Why Teams call analytics are critical to your entire business
Â
CATCHPlus on Europeana Connect: Persistent Identifier solution
1. Persistent Identifiers for Audiovisual Archives and Cultural Heritage Hennie Brugman Technical coordinator CATCHPlus Max-Planck-Institute for Psycholinguistics Netherlands Institute for Sound and Vision
Scalable: hashing, caching, replication Metadata: checksum, link to metadata, restoration information
Includes batch operations (âmove collectionâ)
Handle vs DNS: DNS is control hierarchy, Handles not (necessarily) Handle admin can be somebody else than sysadmin (distributed administration) Handle resolver can be behind http proxy Handle supports Unicode, DNS not Mirroring per record (handle) versus mirroring per data set (dns) Support for access control and authentication (dns has not) PILIN doc: http://www.pilin.net.au/Project_Documents/Community_Guidelines/Using_URLS_PI.htm â URI can be used as a persistent identifier, but at the cost of additional maintenance, which needs to be planned for through explicit strategiesâ Clearer to uncouple locations and identifiers (although an http URI can be both) Avoid unnecessary protocol dependence URL can be used as identifier or as service call. It should be possible to call different services for the same identifier http URI also need explicit identifier management (just as Handles) CoolURIs necessary, otherwise http URI tend to be interpreted as locators Take care that not everyone can publish http URIs, define curation boundaries Identifier management infrastructure is needed for http URIs as well
![Summary ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)