Strand map service
Defines the metadata focus in the DLESE Strand Map Service.
Develop and evaluate a service that uses the AAAS strand maps to provide an interactive interface to educational resources in NSDL. This service will enable educators and learners to:
Metadata focus of the project
In order to provide services to NSDL, information is exchanged via XML and generally as metadata records. So the metadata focus of this project is to:
Metadata development questions
To create a metadata framework, answers to fundamental design questions need to be gathered and understood by interested parties:
SMS collection objects
When developing a metadata framework, you want to know the general concepts to be captured. A concept could be date information or the name and description of something. Concepts then lead to several individual metadata fields like the date the resource was cataloged, the date the resource was accessioned into the library. The table below illustrates the developing metadata framework for the Strand Map Service by listing SMS collection objects across the top and potential metadata fields down the left column. Not all the fields apply to each object in the collection. Information collected about an object may depend on the type of object. See the table key for further explanation.
Table Key: M is mandatory metadata, S is mandatory metadata with a special vocabulary, O is optional metadata
For a better understanding of the conceptual metadata framework depicted by the table above, some of the collection objects are listed below and the content of the metadata fields name, full text and description is described.
Object: One of the Boxes
Object: Benchmark section
XML information for metadata fields
Once the individual fields of a metadata framework are determined, XML specification information for each field is needed. When the XML specification information is complete, development and direct coding of the metadata framework into XML schemas can be done. The following is the list of XML specification information needed about each metadata field listed in the table above.
Types of relationships
Within collections, it is often desirable to create relationships between objects. This section describes broad categories of relationships and then presents observed relationships for the SMS collection. The broad categories are:
For this project, the observed relationships below seem to fall into the hierarchy category. The list below also provides a vocabulary term (e.g. Is part of ) that may be used to describe the observed relationship. These are displayed in bold. Please note at the 2-7-03 mtg, Ted emphasized that connections between the benchmarks and the section in the Benchmark book should be added. Often the cluster name will be the same as the section name but maybe not; thus the reason for the adding the section relationship. Ted said we could keep the cluster relationship for now.
External relationships between SMS objects and other standards
External relationships between SMS objects and other resources
Last updated: 5-19-03