Bulatovic, N.

English

MPG.PuRe

Persistent identification of resources in  eSciDoc service-oriented infrastructureNatasa BulatovicResearch and Development Max Planck Digital LibraryThis work is licensed under a Creative Commons Attribution 2.0 Germany License http://creativecommons.org/licenses/by/2.0/de/Research and Development Activities● Development, operation and maintenance○ Solutions (PubMan, FACES, VIRR, WALS, Admin)○ Services (Service Oriented Architecture - SOA)● IT Infrastructure services○ Development environment○ Communication and collaboration platform○ Wordpress MU platform● eSciDoc project 2004-2009 (closed)○ FIZ Karlsruhe and Max Planck Digital Library○ Development is continuedNameeSciDoc SOA LandscapeNameDiversity of MPG supported by a service infrastructure● People● Librarians, researchers, developers, general public● Data● Publications, research data, supplementary material etc.● Processes● Various institutes apply various workflows supporting their data managementName 21.04.2010Which data are managed (content resources)?NameWhich workflows are supported? Create Modify v4Releasev4“Published” version of a resourceModify  v1Modify v3Modify v5Modify V2 SubmitReleasev5Name 21.04.2010To what and when  a PID is assigned? ● A PID can be assigned to each content resource● A PID can be assigned to each version of the content resource● Example: A publication 1 full text file, 3 supplementary material files associated● has minimum 5 PIDs assigned (each version gets a new PID)● A PID can be assigned in each stage of the workflow to the object as a whole, or to the object versionName 21.04.2010eSciDoc PID ManagerPotential bottleneckPID ManagerGWDG Handle SystemResource HandlerOther System(e.g. locally (Item, Container)managed IDs)● Single Operation success (e.g. creation, modification, submit or release) depends on PID system (GWDG Handle system)● Batch operations issue as well e.g. import or batch release requires several thousand PIDs (handles) to be created at once Name 21.04.2010● End users may be unable to finish their workExtension with PID Cache ManagerResource PID ManagerGWDGHandle SystemHandler(Item, Container)PID CacheManager● PID Cache Manager holds a user-defined threshold of pre-assigned handles (incoming buffer)● Pre-assigned Handles have dummy resolution● If GWDG Handle System is not available a handle is taken from the threshold and moved to an outgoing buffer● An asynchronous process updates the resolution in the GWDG Handle system (in a user-defined frequency)Name21.04.2010The PID Cache Manager GWDGHandle SystemPID CacheManager● Is independent service, can be used by anybody● Technology: PID Cache Manager (Java), HSQLDB, JBoss● Pre-assigned handles have dummy resolution● If GWDG Handle System is not available a Handle is taken from the threshold and moved to an outgoing buffer● An asynchronous process updates the resolution in the GWDG Handle system (in a user-defined frequency)See also: http://colab.mpdl.mpg.de/mediawiki/Pid_cacheName 21.04.2010Requirements for the GWDG Handle system● Interfaces● Stable● Clear specification of methods● The XML schema for create, update of handles is needed● REST interfaces: GET, POST, PUT, DELETE (Retrieve, Create, Update, Delete)● Backward compatible in case of interface changes● Stable operation● Support  and documentation● Community to discuss special servicesName 21.04.2010Proposal: some extensions● Allow to identify same content with multiple resolutions ● Managed by single PID user● Example: Publication item with internal repository identifier escidoc:1234, has following representations: PubMan Item , SengbushWordpress blog post entry, Core-service style sheethttp://pubman.mpdl.mpg.de/pubman/faces/viewItemFullPage.jsp?itemId=escidoc:39182:9http://sengbusch.blogs.mpdl.mpg.de/?s=escidoc%3A39182http://coreservice.mpdl.mpg.de/ir/item/escidoc:39182:9● URL (resolution) validation● Active or passive● LinkedData publishing Name 21.04.2010Extension example: Inter project: archiving LAMUS data into eSciDoc repository● Resources from  LAMUS are additionally archived in the eSciDocrepository● PIDs managed by different PID users● Corpus -> Container (or Item, tbd)● Session -> Item● Session Resources->Item.components● Do we re-assign a handles in eSciDoc repository or resources are getting a new handle● What about resolutions (output from discussions with Daan Broeder, see next slide)?Name 19.04.2010Alternatives for multiple resolutions● Alternative 1 ● PID is associated with two URLs: url_a and url_b, ● We need to indicate which administrator/user should be able to modify each url record. ● This could be done by adding an extra record specifying which HS_ADMIN can modify the URL information in record number "n“.● If no such extra record is present the owner of the PID is the only one that can administrate that URL. Of course this mechanism should be enforced by the PID service implementation ● extra programming required● Alternative 2 ● separate pid for each representation – each created by another owner● ”same-as” (linked data) relation provided by the owner of the PID to point to the other PID● Possible incosistencies on both copies? (are these indeed copies?)● extra  programming requiredBoth alternatives have  valid related use case at MPDL eSciDoc repositoryName 19.04.2010Questions?● bulatovic@mpdl.mpg.deName 21.04.2010

Persistent identification of resources in eSciDoc service-oriented infrastructure

http://hdl.handle.net/11858/00-001M-0000-0013-8364-B

Persistent identification of resources in eSciDoc service-oriented infrastructure

Abstract

Similar works

Full text

Available Versions

MPG.PuRe