Difference between revisions of "Pid Cache Manager Service"
Jump to navigation
Jump to search
m (→Implementation) |
|||
Line 7: | Line 7: | ||
== Implementation == | == Implementation == | ||
* Since | * Since PId cache service is to override the PIDManager, its architecture intends to simulate the PIDManager. | ||
=== Interface === | === Interface === | ||
* The PID cache service provides a REST interface: | * The PID cache service provides a REST interface: |
Revision as of 11:54, 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 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>/<suffix>: the method called:
- /read/view : Visualization of a PID.
- /read/search: Search of a PID.
- /write/create: Creation of a PID.
- /write/update: Update of a PID.