Metadata Collections & QA

XML: Collection metadata version 1.0.00

This page provides links to the XML files (main schema, controlled vocabulary schemas and instance documents) for a specific framework and version number. DLESE metadata uses XML schema and therefore the DLESE metadata frameworks are strongly data typed and are often maintained across several XML schema documents. The schemas for a particular framework are organized via an overarching or main schema (see below). This main schema may call different category and vocabulary schemas to create the framework.

To obtain all the XML schema files as a bundle for a particular framework and version, please contact and request either a unix tar file or a windows zip file. Be sure to include the name of the framework and the desired version number (e.g. ADN version 0.6.50).

Main schema

  • collection.xsd (Include this schema in instance documents (metadata records) for validation)
  • collectionRecord is the root element
  • The framework is composed of several category schemas that call different vocabulary schemas

Category schemas

  • Access - technical access of the collection; describes how the collection will provide its records to externals
  • Approval - collection accessioning status and documents the collection approval process
  • Commonfields - common fields across the different categories of the framework
  • General - describes the overall characteristics of a collection (e.g. subjects, keywords, audience, title, description)
  • Lifecyle - provides the contact and responsible party for a collection
  • MetaMetaData - provides for internal administration of the DLESE collection-level metadata records (e.g. id number, creation date, cataloger information )
  • NSDL - indicates information DPC needs to provide to NSDL in order for the collection to be part of NSDL
  • Relations - creates relationships between collections
  • Vocabs - calls the individual vocabulary schemas


Vocabulary schemas

The vocabulary schemas define the different controlled vocabularies that are used by individual metadata fields.

  • Cost
  • Defaults
    • metadata fields: several different metadata fields
    • schemas: defualts.xsd
  • Grade range
    • metadata fields: general.gradeRanges.gradeRange
    • schemas: gradeRange.xsd
  • Item Format
    • metadata fields: otherAccessMethods.method.metadata or access.oaiSets.oaiSet.metadata
    • schemas: itemFormat.xsd
  • Key
    • metadata fields: access.otherAccessMethods.method.key or access.oaiSets.oaiSet.key
    • schemas: key.xsd
  • Name title
    • metadata fields: lifecycle.contributors.contributor.person.nameTitle and metaMetadata.contributors.contributor.person.nameTitle
    • schemas: nametitle.xsd
  • OAI version
    • metadata fields: access.oaiSets.oaiSet.version
    • schemas: OAIversion.xsd
  • Policy type
    • metadata fields: approval.DLESEpolicies.DLESEpolicy.type
    • schemas: policyType.xsd


  • Relation
  • Role - collection approval
    • metadata fields: approval.contributors.contributor.role
    • schemas: roleApproval.xsd
  • Role - collection contacts
    • metadata fields: lifecycle.contributors.contributor.role
    • schemas: roleLifecycle.xsd
  • Role - collection cataloger
  • Service
    • metadata fields: approval.collectionStatuses.collectionStatus.state
    • schemas: service.xsd
    • metadata fields: approval.collectionStatuses.collectionStatus.state
    • schemas: state.xsd
  • Status
    • metadata fields: metaMetadata.statusOf.status
    • schemas: status.xsd
  • Subject

Sample records

Sample records are provided to show how the collection item-level metadata framework may be used.

Last updated: 2006-01-11