Difference between revisions of "Pid Cache Manager Service"
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
** POST: /<service>/<prefix>/ - identifier generation and registration at PID system | ** POST: /<service>/<prefix>/ - identifier generation and registration at PID system | ||
** DELETE: /<service>/<prefix>/<suffix> - delete (Not allowed) | ** DELETE: /<service>/<prefix>/<suffix> - delete (Not allowed) | ||
* <service>: the url of the pid cache service (for instance: dev-pubman.mpdl.mpg.de/pidcache/handle) | |||
* <prefix>: the method called: | |||
** /read/view : Visualization of a PID. | |||
** /read/searh: Search of a PID. | |||
** /write/create: Creation of a PID. | |||
** /write/update: Update of a PID. |
Revision as of 11:15, 11 March 2010
This Page describes the PID cache service.
Introduction[edit]
- The role of the PID cache service is to avoid unavailability of the PIDManager service hosted at the GWDG [1].
- The PID cache service overrides the PIDManager service for the eSciDoc solutions.
- The PID cache service owned predefined PID which are assigned to eSciDoc Object by calling the Object Handler methods (assignObjectPid() and assignVersionPid()).
Implementation[edit]
- Since the role of the PId cache service is to override the PIDManager, its architecture intends to simulate the PIDManager.
Interface[edit]
- The PID cache service provides a REST interface:
- GET: /<service>/<prefix>/<suffix> - resolve
- PUT: /<service>/<prefix>/<suffix> - registration at PID system (Not implemented)
- POST: /<service>/<prefix>/ - identifier generation and registration at PID system
- DELETE: /<service>/<prefix>/<suffix> - delete (Not allowed)
- <service>: the url of the pid cache service (for instance: dev-pubman.mpdl.mpg.de/pidcache/handle)
- <prefix>: the method called:
- /read/view : Visualization of a PID.
- /read/searh: Search of a PID.
- /write/create: Creation of a PID.
- /write/update: Update of a PID.