Charge (Adam C)
Problem statement
- Digital collection identifiers (Rick)
- Persistent IDs for digital preservation (Bill)
*Requirements for an implementation*(John)
- We don't want to break any system currently used at CUL that uses persistent identifieres, such as the PURL server. Backward compatible.
- Provide a mechanism for persistent ID's for OAI-PMH
- Optionally resolvable only within a constrained environment. Secured nameservice. For archiving. The individual
- Can ensure confidentiallity.System should define a mechanism for client authentication/authorization to ensure data integrity and authority control.
- It doesn't have dependencies on external systems in order to resolve local PIDs.
- Every PID should be globally unique.
- PID should be free of location semantics.
- PID must be able to refer to multiple aspects, attributes, or behaviors of the digital object, but with a default aspect that conforms with convential use.
- Globally resolvable.
- Fine-grained control of PIDs, so that groups can maintain their own sets, without having to maintain multiple PID resolvers/servers.
Methodology (Adam S)* Overview of PID
- PURL
- ARK
- Handle
- OpenURL
- OAI-PMH requirements
Recommendations
(embed the rationale for each recommendation)
- CNRI Handle System (George)
- Proof-of-concept implementation. (Bill)
- Resource Requirements -- we don't know what the requirements are (development? a standalone machine? server space? maintenance?) (John)
- Evaluate the system and its use some time in the future. (Rick)
- A deliverable: A Usage Document that explains how the system can be integrated into CUL collection building (Adam C)
- An explicit statement of the estimated lifespan of the PID and the object it represents. (Bill)