Metadata Collections & QA

Objects framework

Framework purpose

The purpose of the Objects metadata framework is to describe name-value pairs. That is, the object is listed and then described. The object is also categorized in a broad library areas and more specific topics. This mainly a metadata framework used internally by the DLESE Program Center and is not for general use. Some examples of use include frequently asked questions and glossary terms for the DLESE website.

Required metadata

  • Object - the thing to be described (e.g. for a FAQ this would be: 'How do I install the DLESE OAI software?')
  • Description - a narrative describing the content of the object
  • Library area - broad areas into which the object can be categorized (e.g. governance, education, metadata and collections, technical infrastructure)
  • Topic - more specific areas into which the object can be categorized (e.g. OAI software, Lucene indexing, ADN metadata)
  • Dates - a date associated with the object or with the creation of the objects metadata record
  • Resource creator - contact information for the author contributor of the object
  • Resource cataloger - contact information for the cataloger of the object
  • Creation date - the creation date of the metadata record
  • Post date - the date the object is made public on the DLESE website
  • Catalog name and number - an identifying name like FAQ and an identification number for the metadata record like a library call number
  • Record type - the type of object being cataloged. Right now FAQ's, glossary terms, people and services are allowed


Robust metadata

All other metadata not included as required metadata is considered optional/suggested/robust metadata. Some examples include:

  • Relationships between objects

Tool support to create required metadata

There is no direct cataloging tool support for the framework.

Framework features

  • Any generic object that fits the idea of a name-value pair can be cataloged and described minimally
  • Allows for presentation elements like HTML tags directly in XML metadata record

Framework categories

  • None

Framework constraints

  • None


Framework XML

The framework is XML schema-based with strong data typing and some controlled vocabularies to support efficient and effective browsing, search and discovery. The XML schema and sample XML records provide the technical structure and view of the framework. See the current framework XML documents.

Framework vocabularies

Currently, these can only be seen directly in XML. Please see the Framework XML section above.


  • November 2003 - version 0.1.01 (alpha) release


Last updated: 11-11-03