Common requirements

From Metadata-Registry
Revision as of 07:01, 27 August 2008 by Diane (Talk | contribs)

Jump to: navigation, search

DCMI Registry Task Group


Back to DCMI Registry Community Main Page


GOAL: Develop a set of functional requirements common to current registries, based on the experience and findings of current registry implementers and stakeholders. As part of this, investigate the dissemination functionality considered desirable in a registry, and appropriate use cases associated with this functionality.

Requirements

Requirements Relating to Search & Discovery

NSDL Registry
  1. External users should be able to:
    • Search the Registry to discover:
      • Schemas, including those available in associated registries (Description)
      • Relationships between schema elements in available schemas—intra-schema relationships (Resource)
        • Relationships between the term of interest and other terms are a function of contextual browse
      • Available vocabularies, based on topical coverage, owning organization and purpose (Description)
      • Vocabulary terms: by preferred term, broader/narrower relationships—inter-schema relationships (Resource)
        • Relationships between the term of interest and other terms are a function of contextual browse
      • Keyword searches on concept and element description texts (Resource)
    • Searches should be filterable by:
      • Organization
      • Status
      • Usage
  2. Search result display options should include:
    • WordNet style tree display, with links
    • Browse result set in visually oriented display (Naomi's browse?)
    • Rank order by usage

Link to Documentation

Requirements Relating to Data Entry

NSDL Registry

Submitting, Creating and Editing Schemas, Schemes and Application Profiles

  1. Add Organization description
  2. Edit/Update Organization description
  3. Deprecate Organization description
  4. Add Element Set, Vocabulary or Application Profile description
  5. Upload or Create elements, terms or AP specifications
    • If element descriptions, vocabularies, or APs were created in an external tool, and available in approved XML schema, uploaded the set of elements into the registry [Note: Uploaded descriptions subject to validation.]
  6. Edit/Update Element Set, Vocabulary or AP description
  7. Deprecate Element Set, Vocabulary or AP description

Link to Documentation

Requirements Relating to Versioning and History

Requirements Relating to Authentication and User Management

Requirements Relating to Services

Use Cases

Use Cases Relating to Search & Discovery

Use Cases Relating to Data Entry

Use Cases Relating to Versioning and History

Use Cases Relating to Authentication and User Management

Use Cases Relating to Services


Back to DCMI Registry Community Main Page