General instruction: This exercise is designed with the intent of having individuals collaborate by working together in groups. All group work should be conducted after the related section in this chapter is both taught and studied.

Download work template (PDF file)

A "collection" of works should be identified by the instructor or students. An example would be a collection of unused postcards or bookmarks made of different materials, sizes, shapes, and published in different languages, places, and times for different purposes. Treat the items of the collection as the resource, i.e., the postcards themselves, and not the images on the postcards.

Group Work I

Group Work I. Identify desired metadata elements for the collection. List in a table all of the following:

1. Desired Element
   
   
2. Explanation and Description of the Element
   (This will be the element definition and will be included in the final schema.)
   
   
3. Example
   (The examples may be included in the best practice guide, either in the schema or in a separate guide.)
   
   
4. Implementation—M, O, R
   (Mandatory /Optional? Repeatable?)

Group Work II

Group Work II. Decision for value spaces: content and value specifications, vocabularies.

List in the table all of the following:

1. Element Name
   (The element defined by the last task)
   
   
2. Value controlled?
   (Yes, No, and How)
   
   
3. Values
   (a pre-defined list of terms, name of an existing scheme, or rules)

Group Work III

Group Work III. Establish an Application Profile. Assume your own namespace (e.g., "ksu" or any other word). List in a table all of the following:

1. Element Name
   (The element defined by the last task)
   
   
2. Matched SCHEMA A Element and Qualifier
   (Schema A is the preliminary source schema, e.g., vra.agent)
   
   
3. Matched SCHEMA B Element and Qualifier
   (Schema B is the secondary source schema, e.g., dc.langauge)
   
   
4. Additional ksu qualifiers for matched SCHEMA elements
   (These are additional/revised qualifiers for matched SCHEMA A/B elements, e.g., vraksu.subject.May4th.)
   
   
5. Un-matched Element
   (This element will be claimed under ksu Namespace, e.g., ksu.collectionType)

References:

• For the selection of elements from different standards, consult the AVEL METADATA ELEMENT LIST: http://avel.library.uq.edu.au/technical.html
  
  
• For the presentation format of your application profile, consult the DC Government Application Profile: http://dublincore.org/documents/2001/09/17/gov-application-profile/
  
  
• For the presentation of an application profile based on an existing application profile, consult the National Library of Medicine (NLM) Metadata Schema: http://www.nlm.nih.gov/tsd/cataloging/metafilenew.html

Group Work IV

Group Work IV. Create crosswalks

1. Create a crosswalk by mapping your element set to another group's element set.
   
   
2. Create crosswalks using the new element set just created as the source schema, mapping it to another schema, e.g., MODS, DC.

 

Group Work V

Group Work V. Write a specification for the complete element set.

Follow the examples of specifications from the original element sets; write your specification for the element set for postcards

• Examples of original element sets:
  DC: http://dublincore.org/documents/dces/
  
  
• Examples of original Application Profiles:
  NLM: http://www.nlm.nih.gov/tsd/cataloging/metafilenew.html
  and
  DC-GOV: http://dublincore.org/documents/2001/09/17/gov-application-profile/