You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Goals

Note: Questionable goals are in red

For Identifiers

  1. Generally, these identifiers should be branded to Cornell through the use of a Cornell-based DNS name for the resolver; however, it should be possible to use the resolver with an alternate non-Cornell DNS name for consortia and other non-Cornell-branded needs.
  2. Identifiers must be permanent
  3. Identifiers must permanently resolve to a digital object
  4. Simplicity (of description and implementation)
  5. Support for OAI-ORE structuring
  6. Support for vitality checking
  7. Compatible with the Handle System and supports Handle System metadata
  8. Needs to support multiple repositories and naming schemes
  9. Makes sense in context of VIVO, arXiv, OAIS (CUL), Voyager Catalog, and WorldCat
  10. Compatible with multi-institution collections where Cornell branding is inappropriate
  11. Support for "private" identifiers (e.g. for dark archive or internal digital objects)
  12. Identifiers should be short
  13. Identifiers should be (mostly) opaque
  14. Must be resolvable through a web browser
  15. Must be unique without the DNS name portion of the URL

For Resolver and System

  1. Supports billions of identifiers with very fast resolution
  2. Robust architecture and implementation - a highly available system
  3. Need to avoid unbounded generation of surrogate persistent identifiers
  4. Should support multiple delivery formats for an identifier
  5. Must support splitting collections (what does this mean?)
  6. Need a lightweight understanding of identifier equivalence
  7. Need a way to integrate outside PIDs with Cornell (what does this mean? examples?)
  8. The identifiers and the associated content should be easily discoverable by Google
  9. The overall system should integrate well with the "web architecture"
  • No labels