1

Developing a Metadata Element Set or an Application Profile

Image credits: 6Y old Anthony. http://rennisonprimarydesigntechnology.info/design_drawing.html;

2

Major Steps (Overview)1. Functional requirements

What do you want to accomplish with your application?2. Domain model

What kind of things (entities) your metadata will describe, and what are the relationships between those things?

3. Desired metadata elementsWhat elements are desired?

4. Value Space Decisions • Cardinality enforcement (Required or not?)• Value Space Restriction (Controlled values? How – vocabulary or rule?)• Relationship and dependency specification (Sub-elements?)

5. Existing elements Any existing element to consider?

6. Crosswalks7. Specification /Documentation

Put into a complete specification of the element set. 8. Prepare guidelines for use.

3

Major Steps (1-3)Step 1. Functional requirements

What do you want to accomplish with your application?

Step 2. Domain model What kind of things (entities) your metadata will describe, and what are the relationships between those things?

Step 3. Desired metadata elementsWhat elements are desired? List in a table:

Desired Element Explanation and Description of the Element

(This will be the element definition and will be included in the final schema.)

Example (The examples may be included in the best practice guide, either in the schema or in a separate guide.)

1. Communicating about the Functional Requirements

4

An operational systemAn operational system

Questions: What do we want to 'search by', 'browse by', 'sort by', 'link to'?

Question: Will the metadata support these functions?

5

No FORMAT information

Video? Image? Text?

media type

media type

Video? Image? Text?

media type

media type

Resource

Agent

About…

2) Select or Design a Domain Model

What kind of things (entities) your metadata will describe, and what are the relationships between those things?

Review: Entity Relationship Diagram

7Source: from CCO

8

http://dev.iptc.org/rNews-10-Introduction-to-rNewsfor clearer figure

Example:The complete class diagram of the rNews data model.

(for embadding metadata within the news pieces)

9

(cont.) Major Steps (4)Step 4. Value Space Decisions Content and value specifications, vocabularies.

Cardinality enforcement (Required or not?) M, O, R (Mandatory /Optional? Repeatable?)

Value Space Restriction Controlled values? How – vocabulary or rule? (A pre-defined list of terms, name of an existing scheme, or rules, may attach a list or link.)

Relationship and dependency specification (Sub-elements?)

10

Step 5. Find existing elements and re-use them in an Application Profile

What element in another schema would match your element?

Assume your have a namespace (e.g., "ksu" or any other word). Select the namespace you want to reuse (e.g., dc:, dct:, or vra:). List in a table all of the following:Element Name (The element defined by the last task) Matched SCHEMA A Element (Schema A is the preliminary source schema, e.g., vra.agent)Matched SCHEMA B Element and Qualifier (Schema B is the secondary source schema, e.g., dc.langauge) Un-matched Element

(This element will be claimed under ksu Namespace, e.g., ksu.collectionType)

(cont.) Major Steps (5)

11

Step 6. 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.

(cont.) Major Steps (6)

12

Step 7. 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

– Scholarly Works Application Profile (SWAP)http://www.ukoln.ac.uk/repositories/digirep/index/

Eprints_Application_Profile#Scholarly_Works_Application_Profile

Step 8. Prepare guidelines for use.

(cont.) Major Steps (7)

13

Review: Major Steps1. Functional requirements

What do you want to accomplish with your application?2. Domain model

What kind of things (entities) your metadata will describe, and what are the relationships between those things?

3. Desired metadata elementsWhat elements are desired? Cardinality enforcement (Required or not?)

4. Value Space Decisions • Value Space Restriction (Controlled values? How – vocabulary or rule?)• Relationship and dependency specification (Sub-elements?)

5. Existing elements Any existing element to consider?

6. Crosswalks7. Specification /Documentation

Put into a complete specification of the element set. 8. Prepare guidelines for use.

14

In-Class Exercise Team work to make a list of desired elements for either postcards or bookmarks

Element Name | Definition | Example

We will share the elements and discuss these issues: In preparing your metadata project, what do you foresee as the most challenging decisions for your project? Why do you think they are challenging decisions to make? What factors will affect your decisions?