The Open Video Digital Library Toolkit

Metadata Schema Details

Required elements will be essential for basic exploration of the library and must be used (filled in) for each video. These include: Title, Abstract/Summary, Type, Language, Color, Sound, Duration, Date, Date Type, File Relation Type, File Name, File Locator.
Repeatable elements will be useable more than once for the same video and include: Alternative Title, Agent Name, Agent Type, Agent Role Type, Agent Role Title, Chapter Name, Chapter Start Time, Subject, Classification, Spatial Coverage, Temporal Coverage, User Annotation, Form/Genre, Date, Date Type, Collection Name, Related Videos Group, Related Files Group, Custom Elements.
Dependent elements will be linked with other elements and must be used together. Groups of dependent elements include: (Agent Group: Agent Name, Agent Type, (Agent Role Subgroup: Agent Role Type, Agent Role Title)); (Table of Contents Group: Chapter Name, Chapter Start Time); (Date Group: Date, Date Type); (Related Videos Group: Related Video, Video Relation Type); (Related Files Group: Restricted Access (Y/N), Restriction Type/Action, Delivery Controls, File Relation Type, File Name, File Description, File Locator, File Size, File Format, Digitzation Date).
Quick Links to Metadata Element Help
Access Controls Abstract/Summary Agent Name Agent Role Type Agent Role Title Agent Type Alternative Title Chapter Name Chapter Start Time Classification Collection Name Color Creation/Production Credits	Custom Elements Date Date Type Delivery Controls Digitization Date Donor Name Duration File Description File Format File Locator File Name File Relation Type File Size	Form Genre Language Local System Record ID Note Participant/Performer Note Permissions Language Preservation Note Related Videos Related Files Related Video Restricted Access (Y/N) Restriction Type	Rights License Rights Statement Sentence Summary Series Title Sound Spatial Coverage Subject Table of Contents Temporal Coverage Title Transcript Type User Annotation Video Relation Type

Title Information

Title
Alternative Title
Series Title

Title

Required?

Yes

Repeatable?

Dependent?

Description:

This element will hold the main/official title of the video.

Import/Export Mapping
Dublin Core - dc:title
MODS - (titleinfo)(title)
MARC - 245: $a and $b (MARC mapping still in process)
MIC - MICUC015: Title
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Abe Lincoln: The Early Years
B. Maine festival, Passamaquoddy dancers
C. Feline kidney transplant surgery, 4 April 2005, OR-3A

Alternative Title

Required?

Repeatable?

Yes

Dependent?

Description:

An alternative title might be a shorter version of the official title, a common "nickname," or a translated version of the title. Multiple alternative titles may be used to facilite item identification. Those wishing to colocate related items (and were perhaps expecting a Uniform Title element) are referred to the Related Videos section.

Import/Export Mapping
Dublin Core - dc:title.alternative
MODS - (titleinfo)(title type="alternative")
MARC - 246, 740 (MARC mapping still in process)
MIC - MICUC016: Alternative Title
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Lincoln, Abraham: The Early Years
B. Passamaquoddy dancers
C. Kidney transplant surgery, Feline, 4 April 2005, OR-3A

Series Title

Required?

Repeatable?

Dependent?

Description:

If the item being cataloged is part of a formal thematic series of videos, the Series Title would be entered here. Administrators/Catalogers will select from a dropdown list of existing Series Titles in the library (established during set up), or they may add a new one.

Those wishing to colocate related items that are not part of the same series (and were perhaps expecting a Uniform Title element) are referred to the Related Videos section.

Import/Export Mapping
Dublin Core - dc:title.series (.series - local qualifier)
MODS - (relatedItem type="series")(title)
MARC - 440, 490 (MARC mapping still in process)
MIC - MICUC019: Series Title
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Lincoln Interviews, The
B. Festivals of Maine
C. Feline Surgeries, 2005

Agents Responsible (for the creation and/or dissemination of the moving image)

AGENT GROUP

Agent Name
Agent Type
Agent Role Type
Agent Role Title

People and institutions associated with the production and/or distribution of the video in a substantial way will be cataloged as Agents. Performers, individuals or entities making an appearance, supporting technical staff and other participants can be noted in either the Creation/Production Credits (production assistants) or the Performer/Participant Note (actor, interviewee) elements.

The way Agents of Responsibility will be handled in the Open Video Digital Library Toolkit looks unusual, but in fact it corresponds directly with more traditional ways of cataloging personal and corporate names while providing greater flexibility in assigning multiple roles for single agents and improving browsing capabilities. Below are tables that show how the four grouped Agent elements will work together when exporting to different standards. Obviously, the importation process works in the reverse.

Mapping to DC (Dublin Core)
When	and	Then	Maps to:	Notes
Agent Type	Role Type

Any	Creator	Agent Name	dc:creator
		Role Title	dc:creator.title	.title - local qualifer; repeated for multiple roles

Any	Publisher	Agent Name	dc:publisher
		Role Title	dc:publisher.title	.title - local qualifer; repeated for multiple roles

Any	Contributor	Agent Name	dc:contributor
		Role Title	dc:contributor.title	.title - local qualifer; repeated for multiple roles

Mapping to MODS (Metadata Object Description Schema)
When	and	Then	Maps to:	Notes
Agent Type	Role Type

Personal	Any	Agent Name	(name type="personal")
		Role Title	(role)(roleTerm)	subelement of (name); repeated for multiple roles

Corporate	Any	Agent Name	(name type="corporate")
		Role Title	(role)(roleTerm)	subelement of (name); repeated for multiple roles

Meeting	Any	Agent Name	(name type="conference")
		Role Title	(role)(roleTerm)	subelement of (name); repeated for multiple roles

Mapping to MARC (MAchine-Readable Cataloging) in process

Mapping to MARC in process.

Mapping to MIC (Moving Image Collections)
When	and	Then	Maps to:	Notes
Agent Type	Role Type

Personal	Any	Agent Name	Personal Entity Name
		Role Title	Personal Entity Role	repeated for multiple roles

Corporate	Any	Agent Name	Corporate Entity Name
		Role Title	Corporate Entity Role	repeated for multiple roles

Meeting	Any	Agent Name	Unspecified Entity Name
		Role Title	Unspecified Entity Role	repeated for multiple roles

Agent Name

Required?

Repeatable?

Yes with Agent group

Dependent?

Yes

Description:

The Toolkit will strongly encourage the use of a Name Authority File, like that of the Library of Congress, to ensure standardization in the presentation of names. At the very least, the Toolkit will recommend listing personal names in the following format: "Family/Last, Given/First,..." and corporate, meeting or other names (e.g., department, project) in a standard way. Keep in mind that users will be able to browse an alphabetical list of Agent Names.

Import/Export Mapping
See Agent Group mapping description above.

Examples:

A. Jones, Frank
B. Northeast Historic Film
C. Veterinary Medicine, School of

Agent Type

Required?

Repeatable?

Yes with Agent group

Dependent?

Yes

Description:

This element will guide the mapping of Agents to the traditional elements of Personal Name, Corporate Name, Meeting/Conference Name, or Unspecified Entity/Agent Name (MIC).

Import/Export Mapping
See Agent Group mapping description above.

Examples:

Personal, Corporate, Meeting

Agent Roles Group

A single agent may serve multiple roles in the creation of a moving image (Writer, Director, Publisher, Cinematographer, etc.). The Role Type element will guide the mapping of Role Title(s) to the three main elements of responsibility identified in the Dublin Core metadata standard: Creator, Publisher, Contributor. The Role Title element will default to the role selected in the Role Type, but will allow editing to provide greater specificity in describing the type of responsibility the agent has for the video (see below).

The Role elements can be repeated as many times as necessary for a single agent.

Agent Role Type

Required?

Repeatable?

Yes with Agent Group

Dependent?

Yes

Description:

Administrators/Catalogers must choose one of the three General Roles for every role attributed to an Agent. (Creator, Publisher, Contributor)

Import/Export Mapping
See Agent Group mapping description above.

Examples:

Creator, Publisher, Contributor

Agent Role Title

Required?

Repeatable?

Yes, with a Role Type

Dependent?

Yes

Description:

Role Title(s) may include the titles attributed to an Agent in the credits of the video or other detailed descriptions as determined by the administrator of the Toolkit. The element will default to the role identified in the Role Type element, but Administrators/Catalogers may edit the element by selecting from a list of over 100 "Relator Roles" from the MARC standard or create their own.

Import/Export Mapping
See Agent Group mapping description above.

Examples:

A. Director
B. Sponsor
C. Surgeon

Table of Contents / Scene List

TABLE OF CONTENTS GROUP

Chapter/Scene Name
Chapter/Scene Time

The two elements of Chapter/Scene Name and Chapter/Scene Start Time will work together to generate an interactive Table of Contents. When viewing the Table of Contents users will be able to click on a chapter/scene name and begin viewing that section of the video (like the scene selection function of feature film DVD menus). Display of times is optional.

Scene 1 (00:00)
Scene 2 (00:35)
Scene 3 (01:20)
Scene 4 (03:25)

Start times will not be required during the cataloging of the chapter/scene names. They can be added later during the semi-automated keyframe extraction process which captures frames of the video at intervals for the purpose of generating a "fast forward" preview of the video. Administrators/Catalogers will have the opportunity to associate certain keyframes with chapter/scene titles. Such linking also will allow for the display of a keyframe image with each chapter/scene name if desired.

This dynamic Table of Contents function will prove especially valuable for Toolkit users needing extensive scene or shot-level access. The number of allowable chapters/scenes is infinite, and the names/titles themselves are both searchable and browsable.

Import/Export Mapping
Most other systems or metadata standards are not designed for tracking chapters/scenes independently and usually have only one element to accommodate an entire table of contents. When exporting metadata from the Toolkit, all the chapter/scene names for a single video, and their associated start times, will be aggregated into a single continuous value with chapters/scenes separated by punctuation. Likewise, upon importation, Toolkit users will have the opportunity to identify which punctuation separates their chapter/scene titles in order to facilitate parsing into individual chapters/scenes that can then be matched with keyframes and start times. The combined elements will import/export as follows:

Dublin Core - dc:tableofcontents
MODS - (tableofcontents)
MARC - 5xx (MARC mapping still in process)
MIC - MICUC032: Contents
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Chapter/Scene Name

Required?

Repeatable?

Yes

Dependent?

Yes

Description:

The value of this element could be a formal name for a scene or chapter (as in feature films) or contain keywords to help identify the scene or shot (to facilitate searching for "clips"). The name will be displayed to end users with details about the video or in browsable lists. Using meaningful first words will assist with identification in browse lists.

Import/Export Mapping
See Table of Contents Group mapping description above.

Examples:

A. Splitting rails (formal chapter name)
B. Climax of group dance (vs. "group dance climax" may help users to find scene quickly)
C. Extraction of kidney (or Closing, or Anesthesia)

Chapter/Scene Start Time

Required?

Repeatable?

Yes

Dependent?

Yes

Description:

Start times associated with the above names of chapters/scenes can be selected from among keyframes generated by the keyframe extraction tool (see above) or they may be manually added/imported if known.

Import/Export Mapping
See Table of Contents Group mapping description above.

Examples:

A. 00:05:42
B. 00:27:53
C. 01:02:14

Content Summary

Abstract/Summary
Sentence Summary
Transcript

Abstract/Summary

Required?

Yes

Repeatable?

Dependent?

Description:

This element will hold a prose summary of the contents of the video to assist end users in identifying the relevance of the video for their needs. It will be recommended that the abstract/summary be less than 500 words and include any keywords beyond those provided in Subject (or other elements) to increase findability for different user types and purposes. Provision will be made for inclusion of a fully searchable transcript in the Transcript element as described below.

Import/Export Mapping
Dublin Core - dc:description.abstract
MODS - (abstract)
MARC - 520 (MARC mapping still in process)
MIC - MICUC033: Summary
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Abe Lincoln talks about his early life from birth until first political post. Interview scenes intercut with photos and ephemera. Key milestones covered include: splitting rails, love of books, law degree, ...
B. Passamaquoddy dancers perform as part of the Maine Festival, an annual arts event held in Brunswick, Maine. The company, members of the Passamaquoddy Tribe from Pleasant Point in Washington, County, Maine, is composed of young dancers, wearing both traditional and contemporary clothing. The dances are announced. Musical accompaniement includes drumming. The performance takes place outdoors on a platform with a cloth backdrop. Audience member sit on the ground.
C. Feline kidney transplant surgery performed in Operating Room OR-3A on 4 April 2005 by Dr. Smith. Single camera records all steps including: anesthesia, extraction of kidney, replacement of kidney, closure. Demonstrates effective handling of complications from excessive bleeding. Staff present include surgeon, anesthesiologist, 2 nurses, kidney specialist...

Sentence Summary

Required?

Repeatable?

Dependent?

Description:

In preliminary search results sets, users will be provided with minimal information for selecting a video. The sentence summary will be a way to describe the video concisely. This element will default to the first line of the Abstract/Summary, but can be edited/changed by Administrators/Catalogers to a more concise and descriptive sentence if necessary.

Import/Export Mapping
Dublin Core - dc:description.sentence (.sentence - local qualifer)
MODS - (abstract) add to end when exporting to MODS
MARC - add to end of 520 when exporting to MARC (MARC mapping still in process)
MIC - MICUC033: add to end of Summary when exporting to MIC
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Abe Lincoln talks about his early life from birth until first political post. (default)
B. Passamaquoddy Indian dance performance with live percussion. (edited)
C. Feline kidney transplant surgery; all steps; complications from excessive bleeding; specialist present. (edited)

Transcript

Required?

Repeatable?

Dependent?

Description:

This element will hold the full electronic transcript of the video. In order to enable searching of the transcript text, the transcript content must be copied/pasted or typed in directly. Document files (DOC, PDF, other) of the transcript may also be made available through the Related Files group of elements.

Import/Export Mapping
Dublin Core - dc:description.transcript (.transcript - local qualifer)
MODS - (abstract script="??") (MODS map in process)
MARC - no map (MARC mapping still in process)
MIC - no map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

Full text of transcripts.

Subject Matter

Subject
Classification
Spatial/Geographic Coverage
Temporal/Time Period Coverage

Subject

Required?

Repeatable?

Yes

Dependent?

Description:

This element will hold the topical subjects of the video. It will be recommended that a controlled vocabulary be used to select appropriate subjects. Relevant controlled vocabularies may include: Library of Congress Subject Headings (LCSH), Medical Subject Headings (MeSH), Art and Architecture Thesaurus (AAT), Thesaurus for Graphic Materials: Subjects (I) and Genres/Physical Characteristics (II) (TGMI, TGMII), FAST Authority File (Faceted Application of Subject Terminology). Links to other controlled vocabularies/thesauri (UNESCO thesaurus, Biocomplexity thesaurus, etc.) can be found at the Queensland University of Technology Controlled Vocabularies web site.

Individuals, corporations, meetings or other entities may also, of course, be the subject of the video. As for Agents above, it is recommended that a Name Authority File be used whenever possible.

Library of Congress Subject Headings (LCSH) are common in libraries, but the rules for constructing headings are complex and the multi-part subjects do not support the kind of faceted browsing the Toolkit will be designed for (separate elements for geographic references, time period references, and other subdivisions). If LCSH subjects are imported into the Toolkit directly into the Subject element, the Toolkit will still be able to retrieve videos when searching for geographic, temporal, form/genre, as the text of the Subject element will be searched. If these subdivisions are parsed out, however, and entered into the appropriate Toolkit metadata elements, the videos will also be findable in alphabetical browsing lists.

OCLC's FAST project is working on a program for automatically converting LCSH to faceted subjects. This may prove useful to those users wishing to maximize the faceted Toolkit metadata schema. Resources will be included in the documentation for the Toolkit.

Import/Export Mapping
Dublin Core - dc:subject
MODS - (subject)(topic) or (subject)(name)
MARC - 650, 600, 610, 611 (MARC mapping still in process)
MIC - MICUC040: Subject
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Lincoln, Abraham, 1809-1865 (LC)
B. Passamaquoddy Indians (LC); Folk dancing (LC)
C. Kidney Transplantation; Cats (MESH)

Classification

Required?

Repeatable?

Yes

Dependent?

Description:

Classification numbers (a.k.a. call numbers) will not be required in the Toolkit due to the flexibility of the digital environment in searching and browsing subjects and other facets of identification. The Toolkit will, however, accept and utilize classification numbers imported from other systems and will offer browsing based on these numbers if desired.

Classification numbers like those represented by the alpha-numeric Library of Congress Classification (LCC) or numeric Dewey Decimal Classification (DDC) systems can serve a number of functions. The traditional, primary function has been to identify the physical location of an item in a physical library or storage area (grouped by subject and form to additionally facilitate browsing and discovery by patrons). In the digital world, the physical locator function of a classification number is replaced by filenames, URLs, or URIs for locating unique digital items (files).

Classification can also serve to conceptually locate an item within the scope of human experience. (Is the item more a biography of a person or a history of the Civil War? Is it more about kidney transplants or cats?) In this sense, classification numbers are still useful in the digital environment if it is important to display the entire collection in a single, topically organized list. Otherwise, it is difficult to justify the additional work to classify items in the digital world, as much of the same access and discovery is provided through multi-term searching and browsing of subjects.

Import/Export Mapping
Dublin Core - dc:subject.classification (.classification - local qualifer)
MODS - (classification)
MARC - 050, 080, 082, etc. (MARC mapping still in process)
MIC - MICUC046: Classification
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. E457.T427; 973.7/092 (LCC;DDC for Lincoln)
B. KF8208.B76; 346.7304/3/08997 (LCC;DDC for Passamaquoddy)
C. SF447.M32; 636.8/083 (LCC;DDC for cat diseases/health)

Spatial/Geographic Coverage

Required?

Repeatable?

Yes

Dependent?

Description:

This element will be used to identify any geographic or spatial area covered by the video. The most obvious use would be if the video is "about" Boston, or the Nile, or Mars. But users may also wish to find videos that take place in Boston or concern New England notables, for example. In this case, a documentary about Henry David Thoreau or transcendentalism, which are not "about" Massachusetts, may still be made more "findable" by including a geographic coverage element that references the area. The extent of use of this element will depend on the content of the local collection and the anticipated needs of the users.

OCLC's FAST project is working on a program for automatically converting LCSH to faceted subjects. If a geographic/spatial subdivision is included in a Library of Congress Subject Heading being imported into the Toolkit, it could be parsed and moved to this geographic/spatial coverage element. Resources will be included in the documentation for the Toolkit.

Import/Export Mapping
Dublin Core - dc:coverage.spatial
MODS - (subject)(geographic)
MARC - 522, 651, 691, 043, 052 (MARC mapping still in process)
MIC - MICUC040: Subject
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. None (only "United States" would be applicable to Lincoln, but it would be too broad for usefulness, though a county or town may be useful if the video is part of a regional collection, like a historical society in Illinois or Kentucky)
B. Maine; Brunswick, Maine
C. None (geo-spatial coverage deemed not relevant for users searching for feline kidney transplant surgery videos)

Temporal/Time Period Coverage

Required?

Repeatable?

Yes

Dependent?

Description:

This element will be used to identify the time period(s) covered by the video. The most obvious use would be if the video is "about" the 1960s, the Renaissance, the Jurassic period. But users may also wish to find videos that take place in the 16th century or concern Victorian era society, for example. In this case, a documentary about Shakespeare or the "Great Exhibition" in London (1st World's Fair), which are not "about" the 1500s or the 1800s, may still be made more "findable" by including a temporal coverage element that references the time period. The extent of use of this element will depend on the content of the local collection and the anticipated needs of the users.

OCLC's FAST project is working on a program for automatically converting LCSH to faceted subjects. If a chronological subdivision is included in a Library of Congress Subject Heading being imported into the Toolkit, it could be parsed and moved to this temporal coverage element. Resources will be included in the documentation for the Toolkit.

Import/Export Mapping
Dublin Core - dc:coverage.temporal
MODS - (subject)(temporal)
MARC - 523, 045, 518, 033 (MARC mapping still in process)
MIC - MICUC040: Subject
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. 1809-1834
B. 1978
C. 2005

Participant Credits

Creation/Production Credits
Participant/Performer Note

Creation/Production Credits

Required?

Repeatable?

Dependent?

Description:

This element will hold a list all of the personnel associated with the creation or production of the video that are not deemed to have had primary responsibility (Agents). This note would contain film crew, editing staff, support/clerical services, etc.. Actors, interviewers, participants, or individuals appearing would be listed in the Performer/Participant Note.

Import/Export Mapping
Dublin Core - dc:description.productionnote (.productionnote - local qualifier)
MODS - (note)
MARC - 508 (MARC mapping still in process)
MIC - MICUC034: Creation or Production Credits
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Sue Jones, Cinematographer; Bill Frank, Editor; Danny Miller, Sound
B. Ben Levine, Videographer
C. Unsupervised camera and sound

Participant/Performer Note

Required?

Repeatable?

Dependent?

Description:

This element will hold a list all of the personnel or entities that actually appear in the video. This note would contain actors, interviewers, participants, or individuals appearing. Film crew, editing staff, support/clerical services, etc. would be listed in the Creation/Production Credits.

Import/Export Mapping
Dublin Core - dc:description.participantnote (.participantnote - local qualifer)
MODS - (note type="performer)
MARC - 511 (MARC mapping still in process)
MIC - MICUC035: Participant or Performer Note
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Abraham Lincoln, Interviewee; Joe Smith, Interviewer; Mary Todd Lincoln, Appears briefly
B. Passamaquoddy Tribe youth dance troupe
C. Dr. Smith, surgeon; Jan Sims, anesthesiologist; Sue Miller, nurse; Paul Ogambwe, nurse; Sharon Liu, kidney specialist

Notes

Note
Preservation Note
User Annotation

Note

Required?

Repeatable?

Dependent?

Description:

This element will provide the opportunity to include additional information about the video that will be helpful to end users - information that may not naturally fit into any of the other metadata elements. The Note element will be included in any search and therefore it can also be used to contain local keywords that do not correspond to whatever controlled vocabulary is used in the Subject element.

Import/Export Mapping
Dublin Core - dc:description.note (.note - local qualifier)
MODS - (note)
MARC - 500 (MARC mapping still in process)
MIC - MICUC031: Note
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Lincoln laughs when talking about first job. Lincoln affectionate when Mary turns up. Five minutes of sound missing from early part.
B. Audio quality is uneven.
C. Dean of school in visitor gallery, not shown.

Preservation Note

Required?

Repeatable?

Dependent?

Description:

This element can hold detailed preservation metadata. The Toolkit is designed for presentation of video via the Web, and not for comprehensive archival management. This note is provided for those institutions whose users need information about preservation aspects of the original moving image to facilitate their exploration of the library. This information may very often include provenance (ownership history), technical details about format, or details about the preservation or restoration of the original item. If more precise preservation detail is necessary, Custom Elements may be used for this purpose.

Import/Export Mapping
Dublin Core - dc:provenance
MODS - (note type="conservation history")
MARC - 561 (MARC mapping still in process)
MIC - MICUC031: Note
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Found at yard sale in Joliet, Illinois in 1955; bequeathed to institution in 1976; film type unknown, custom rendering device developed by University of Atlantis film program to facilitate viewing and conversion to digital
B. 3/4-inch field tapes transferred to BetaSP in 2004.
C. originally recorded on VHS

User Annotation

Required?

Repeatable?

Yes

Dependent?

Description:

This optional element will enable end users to contribute information about the video (reviews of content, pointers to related videos or web sites, etc.). When activitating this element as part of the toolkit setup, Administrators/Catalogers will be able to provide guidelines for users, and tools will be provided for monitoring and controlling the annotation.

Import/Export Mapping
Dublin Core - dc:description.annotation (.annotation - local qualifier)
MODS - (note)
MARC - 500 (MARC mapping still in process)
MIC - MICUC031: Note
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. This is amazing footage!; see use in teaching here: URL.
B. Annotation including identification of dancers and status of other recordings of these dances should be done in coordination with Passamaquoddy tribal government.
C. Excellent example of managing bleeding complications in small animals.; Thanks for CC rights, see my re-use here: URL

Description

Type
Form/Genre
Language
Language Note
Color
Sound
Duration

Type

Required?

Yes

Repeatable?

Dependent?

Description:

This element will always default to "Moving Image." Other types of files that provide context for the video (promotional poster, stills, etc.) are cataloged in the Related Files section and their "types" are determined by their File Format.

Import/Export Mapping
Dublin Core - dc:type
MODS - (typeOfResource)
MARC - (MARC mapping still in process)
MIC - MICUC023: Type
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

moving image (for all)

Form/Genre

Required?

Repeatable?

Yes

Dependent?

Description:

Form descriptions identify the general purpose or production characteristics of the moving image (advertisement, amateur, animation, feature, television, unedited, etc.)

Genre descriptions identify the style or content (children's, documentary, espionage, ethnic, instructional, legal, news, western, etc.).

The Toolkit will give users the ability to browse videos by either Form or Genre or a combination, such as:

unedited (Form) animal (Genre) footage;
biographical (Genre) home movies (amateur - Form);
television (Form) news (Genre) clips, or;
funny (comedy - Genre) ads (advertising - Form).

Each video will be able to be described by as many forms or genres as are relevant. In the case of advertisements, for example, a further Form of Television-Commercial may be added to distinguish the video from advertisements that may run prior to feature films, or those displayed locally in retail stores or public transportation venues.

A recommended Form/Genre list will be included in the Toolkit. The term list will be compiled from the Library of Congress (LC) Moving Image Genre/Form Guide and the Video Development Initiative (ViDe) Genre list (p.16).

Import/Export Mapping
Dublin Core - dc:description.formgenre (.formgenre - local qualifier)
MODS - (genre)
MARC - 655 (MARC mapping still in process)
MIC - MICUC041: Genre/Form
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. feature; biographical (non-fiction); historical
B. dance performance; event; historical
C. unedited; diagnostic/surgical procedure; medical

Language

Required?

Yes

Repeatable?

Dependent?

Description:

This element will describe the primary language of the video. Additional languages, subtitles, and other information may be recorded in the Language Note.

Languages will be stored in three-character code according to ISO 639 standard (e.g., eng for English, esl or spa for Spanish), but will be displayed in full English.

Import/Export Mapping
Dublin Core - dc:language
MODS - (language)(languageTerm)
MARC - 041, 546 (MARC mapping still in process)
MIC - MICUC037: Language;
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. English
B. English
C. English

Language Note

Required?

Repeatable?

Dependent?

Description:

This element will describe any additional information about languages related to the video including other languages occurring, available subtitles or dubbing options, or notes of original language, etc.

Import/Export Mapping
Dublin Core - dc:language.note (.note - local qualifier)
MODS - (note type="language")
MARC - 041, 546 (MARC mapping still in process)
MIC - MICUC038: Language Note
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Subtitles available in French, German and Spanish
B. Additional language: Passamaquoddy (Peskotomuhkati)
C. [no note]

Color

Required?

Yes

Repeatable?

Dependent?

Description:

This element will identify whether the video is fundamentally Black and White, Color, or Colorized. Specific notes about color can be included in the Note element. For example, a documentary that contains a great deal of black and white footage, but includes some color footage (e.g., recent interviews) must be considered Color in the Color element, but notation about the percentages of color content can be included in the Note element.

Import/Export Mapping
Dublin Core - dc:description.color (.color - local qualifer)
MODS - (physicalDescription)
MARC - 300 (MARC mapping still in process)
MIC - MICUC028: Physical Characteristics
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Black and White
B. Color
C. Color

Sound

Required?

Yes

Repeatable?

Dependent?

Description:

This element will identify whether the video is accompanied by sound (synchronized or not).

Import/Export Mapping
Dublin Core - dc:description.sound (.sound - local qualifer)
MODS - (physicalDescription)
MARC - 300 (MARC mapping still in process)
MIC - MICUC028: Physical Characteristics
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Yes
B. Yes
C. Yes

Duration

Required?

Yes

Repeatable?

Dependent?

Description:

This element will identify the total duration of the moving image. The time can be expressed to the second.

Import/Export Mapping
Dublin Core - dc:format.extent
MODS - (physicalDescription)
MARC - 300 (MARC mapping still in process)
MIC - MICUC022: Duration
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. 00:59:03
B. 00:13:48
C. 02:45:12

Dates

DATES GROUP

Date
Date Type

Many different types of dates associated with a moving image will be important to different types of users that may be exploring a digital video library. These dates may include a record creation date, record update (last) date, original/creation/shooting/production date, publication date, copyright date, air/broadcast date, release/issue date, reissue date or others. The Toolkit will be designed to accommodate these diverse needs by allowing administrators to include as many dates as are important to their anticipated user group. As with the treatment of Agents, the Dates group may appear unusual at first, but the descriptions below explain how the Toolkit Dates structure will map to other schemas for metadata importing/exporting purposes.

Mapping to DC (Dublin Core)

The Dublin Core Date element also includes eight DC-approved qualifiers, of which four are relevant for videos. When a Toolkit Date Type corresponds to one of these qualifiers, the corresponding Toolkit Date element will be mapped to the appropriate qualifed DC Date element:

Air/Broadcast maps to dc:date.available
Shooting/Production maps to dc:date.created * see also Digitization Date below
Copyright maps to dc:date.dateCopyrighted
Release/Issue maps to dc:date.issued

Additional local qualifiers will also be used for other Date Types that may be selected, including:

Reissue maps to dc:date.reissued
Publication maps to dc:date.publication
Record Creation maps to dc:date.recordcreation
Record Update (Last) maps to dc:date.lastrecordupdate

Mapping to MODS (Metadata Object Description Schema)
The MODS recordInfo element allows for two subelements related to date. The MODS originInfo element allows for seven date related subelements, of which only three are really valid for most videos and a fourth (dateOther) must accommodate all other Toolkit Date Types. When a Toolkit Date Type corresponds to one of these subelements, the corresponding Toolkit Date will be mapped to the appropriate MODS subelement: Record Creation maps to (reocrdInfo)(recordCreationDate) Record Update (Last) maps to (recordInfo)(recordCreationDate) Shooting/Production maps to (originInfo)(dateCreated) Copyright maps to (originInfo)(copyrightDate) Release/Issue maps to(originInfo)(dateIssued) Air/Broadcast maps to (originInfo)(dateOther) Reissue maps to (originInfo)(dateOther) Publication maps to (originInfo)(dateOther)

Mapping to MARC (MAchine-Readable Cataloging)
MARC mapping is complex and is still in process. Resources for importing/exporting from/to MARC will be included with Toolkit.

Mapping to MIC (Moving Image Collections)
MIC uses a single repeatable Date element to represent a variety of dates. This element is under revision and mapping activities will be coordinated with the MIC metadata team.

Digitization Date Please note that digitization dates are unique to the various file formats made available and are not covered in this primary metadata element. See Related Files for more information.

Date

Required?

Yes

Repeatable?

Yes, with Date type

Dependent?

Yes

Description:

This element will contain an actual date as expressed in YYYYMMDD form. The date will be displayed with the month spelled out for easier identification. Only those parts of the date that are not "00" will be displayed.

Import/Export Mapping
See Dates Group mapping description above.

Examples:

A. 3 November 2003 (20031103)
B. 1978 (19780000)
C. 5 April 2005 (20050405)

Date Type

Required?

Yes

Repeatable?

Yes, with Date

Dependent?

Yes

Description:

This element will identify the type of date identified in Date. Date types will include record creation date, record update (last) date, original creation date, publication date, copyright date, air date, release date, reissue date or others.

Import/Export Mapping
See Dates Group mapping description above.

Examples:

A. Air
B. Shooting
C. Creation

Contextual Information

Collection Name
Donor/Contributor Name
Local System Record ID

Collection Name

Required?

Repeatable?

Yes

Dependent?

Description:

If a video is part of one or more larger collections, these collections would be noted in this element. A video may be considered a part of more than one collection and this element may be repeated as many times as necessary. Administrators/Catalogers will select from a dropdown list of existing Collections in the library (established during set up), or they may add a new one.

Import/Export Mapping
Dublin Core - dc:relation.isPartOf.title (.title - Vide qualifier)
MODS - (relatedItem type="host")(title)
MARC - 5xx (MARC mapping still in process)
MIC - MICUC043: Collection Identifier
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Civil War Films Collection
B. Media Source Collection
C. [none, created by staff]

Donor/Contributor Name

Required?

Repeatable?

Dependent?

Description:

This element will hold the name of the person or entity that has contributed the moving image. Administrators/Catalogers will select from a dropdown list of existing Donors in the library (established during set up), or they may add a new one.

Import/Export Mapping
Dublin Core - dc:provenance.donor (.donor - local qualifier)
MODS - (note type="acquisition")
MARC - 541 (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Mertz, Fred and Ethel
B. Levine, Ben
C. Staff generated

Local System Record ID

Required?

Repeatable?

Dependent?

Description:

This element will be used to contain a reference number from an institution's local system (catalog, inventory list, etc.). Including this reference number will assist with locating the item in the other system for purposes of identifying greater detail not necessary for the Web display of video (preservation metadata, technical metadata). Direct linking between the Toolkit and other systems will be developed in later phases of the Toolkit.

Import/Export Mapping
Dublin Core - dc:source
MODS - (note)
MARC - 5xx (MARC mapping still in process)
MIC - MICUC004: Local Metadata Record ID
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. FEM-023
B. 5286-01-NHFC-20
C. [none, video metadata only in Toolkit library]

Rights for Reproduction and Re-use

Rights Statement
Rights License
Permissions Language

Rights Statement

Required?

Repeatable?

Dependent?

Description:

The Rights Statement will be a general statement about the rights associated with the video. If any rights are granted to the user, the legal details will be outlined in the Rights License (as described below).

Rights for reproduction and re-use of video content are complex. It is important for donors as well as users to be clear about what can and cannot be done with the video being shared over the Web. The Toolkit will enable precision and flexibility in managing rights-related issues by providing 3 reproduction and re-use elements and 3 access control elements at the file/format level.

Import/Export Mapping
Dublin Core - dc:rights
MODS - (accessCondition)
MARC - 540 (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. All rights reserved. For permissions please contact: ...
B. Some rights granted. Non-profit reproduction, re-use and screening encouraged. Commercial re-use must be negotiated with Northeast Historic Film. Attribution requested. See Permissions Language below.
C.

This work is licensed under a Creative Commons License.
[What is Creative Commons? click here.]

Rights License

Required?

Repeatable?

Dependent?

Description:

The Rights License element will contain the legal text defining the details of the rights granted to the user as described generally in the Rights Statement (as described above).

Rights for reproduction and re-use of video content are complex. It is important for donors as well as users to be clear about what can and cannot be done with the video being shared over the Web. The Toolkit will enable precision and flexibility in managing rights-related issues by providing 3 reproduction and re-use elements and 3 access control elements at the file/format level.

Import/Export Mapping
Dublin Core - dc:rights.license
MODS - (accessCondition)
MARC - 540 (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. [no license text, permissions granted privately]
B. Northeast Historic Film represents the donor, Ben Levine. Permission for commercial reuse must be negotiated with Northeast Historic Film... [legal text]
C. Link to legal language of Creative Commons non-commercial-attribution-share-alike license.
[What is Creative Commons? click here.]

Permissions Language

Required?

Repeatable?

Dependent?

Description:

If rights are granted that require attribution, the requested attribution language to be used will be listed in this element.

Rights for reproduction and re-use of video content are complex. It is important for donors as well as users to be clear about what can and cannot be done with the video being shared over the Web. The Toolkit will enable precision and flexibility in managing rights-related issues by providing 3 reproduction and re-use elements and 3 access control elements at the file/format level.

Import/Export Mapping
Dublin Core - dc:rights.language (.language - local qualifer)
MODS - (accessCondition)
MARC - 540 (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. [no language, permissions granted privately]
B. When reproducing, re-using or screening this video publicly, please acknowledge: "Media Source Collection, Northeast Historic Film (www.oldfilm.org), Bucksport, Maine."
C. When reproducing, re-using or screening this video under the terms of the Creative Commons licence, please acknowledge: "University of Atlantis, School of Veterinary Medicine (www.vet.uatlantis.edu). For more information please contact: ..."

Related Files

RELATED FILES GROUP

Access Controls
File Description
File Specifications

For each video, multiple digital files in various formats can be made available to users. Each of these related files can be represented by all of the same primary metadata (Title, Agents, Subject, Description, Rights, etc.). Beyond the primary metadata, these related files are distinguished only by their format and file size (and perhaps digitization date).

The metadata elements associated with these related files will include access controls, text descriptions that will enable users to understand what types of files are available, and the technical distinctions of the files themselves (size, format, digitization date, location).

The descriptions of all of the Related Files elements below will be relevant for each related digital file. These 10 elements will be linked for each separate file and there may be as many files as desired. When mapping to/from other standards, these elements will be mapped within the "relation" elements of other standards, which are likewise repeatable for each related file.

Administrators/Catalogers will catalog one file at a time. The files will not be "uploaded" into the Toolkit, but rather "pointed to" by URLs, URIs or other filepaths listed in the File Locator element.

Non-video Related Files Most related files will be format or quality distinctions of the video described by the primary metadata, but the Toolkit will allow for other related files such as a transcript (PDF, DOC, etc.), images of promotional materials like posters or advertisements (JPG, GIF, PDF, etc.), or even simple links to related web sites (URLs).

Access Controls

Restricted Access (Y/N)
Restriction Type/Action
Delivery Controls

The Toolkit will enable Administrators to institute precise access controls over each of the digital files. For example, access could be restricted to streaming video only (no downloading). Some formats could be restricted entirely to certain types of users (members, fee-based). In support of these restrictions, the Toolkit will also activate certain behaviors when restrictions are encountered. If a user clicks on a restricted video, they will be prompted to log in, accept the license agreement, or some other action of the institution's choosing.

Restricted Access (Y/N)

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will indicate whether the element is restricted or not. If "Yes," then the Restriction Type element below is consulted to determine which action should be activated to bring the user to the next step in accessing the file.

Import/Export Mapping
Dublin Core - dc:relation.Q.restricted (.restricted - local qualifer) (Q = appropriate qualifier per "Relation Type" below)
MODS - (relatedItem type="Q")(accessCondition) (Q = appropriate qualifier per "Relation Type" below)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Yes
B. No
C. Yes

Restriction Type/Action

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will identify what action the system should take if the file is restricted. Actions may include asking the user to log in, asking the user to accept a license agreement, or other actions as needed by the institution.

Import/Export Mapping
Dublin Core - dc:relation.Q.behavior (.behavior - local qualifer) (Q = appropriate qualifier per "Relation Type" below)
MODS - (relatedItem type="Q")(accessCondition) (Q = appropriate qualifier per "Relation Type" below)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. user login
B. [not applicable since no restriction]
C. user license agreement acceptance

Delivery Controls

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will identify what level of delivery will be allowed for this file (once restricted access criteria have been met). Administrators/Catalogers will select from a controlled list which will include: streaming only, download low-quality, download any, etc.

Import/Export Mapping
Dublin Core - dc:relation.Q.accessRights (.accessRights - local qualifier) (Q = appropriate qualifier per "Relation Type" below)
MODS - (relatedItem type="Q")(accessCondition) (Q = appropriate qualifier per "Relation Type" below)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. Streaming only
B. Download any
C. Download any

File Description

File Relation Type
File Name
File Description

File Description elements will contain information that will help users identify which type of file they may want to access and guide the structure of display of the files to the end user.

File Relation Type

Required?

Yes

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will describes the relationship of the video described by the primary metadata to this related file. Relationships will include the approved qualifiers used in Dublin Core:

hasFormat, isFormatOf,
hasPart, isPartOf,
hasVersion, isVersionOf,
references, isReferencedBy,
replaces, isReplacedBy,
requires, isRequiredBy

as well as these Toolkit specific relationships:

hasReusedPartsFrom, isReusedPartiallyBy

Relation types would be selected by the Administrator/Catalogrer based on the "Subject, Predicate, Object" model: The video described by the primary metadata (Subject) "Relation Type" (Predicate) this file (Object). In most cases, with different formats of the same video, the Relation Type will be "hasFormatOf." If, however, the file is an image of a promotional poster, the Relation Type would be "isReferencedBy." Or, if the file is a PDF of the transcript, the Relation Type would be "isVersionOf."

Import/Export Mapping
Dublin Core - no DC map; whatever is selected becomes "Q" in other elements
MODS - no MODS map; whatever is selected becomes "Q" in other elements
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. [Abe Lincoln: The Early Years] "hasFormatOf" [this MPEG-4 file]
B. [Maine festival, Passamaquoddy dancers] "isReferencedBy" [this JPG file of promotional poster]
C. [Feline kidney surgery, 4 April 2005, OR-3A] "hasFormatOf" [this QuickTime file]

File Name

Required?

Yes

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will hold a title of the unique digital file that can be displayed to the user. If no title is entered, the Toolkit will display the name of the format of the file.

Import/Export Mapping
Dublin Core - dc:relation.Q (Q = appropriate qualifier per "Relation Type" above)
MODS - (relatedItem type="Q")(title) (Q = appropriate qualifier per "Relation Type" above)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. ["MPEG-4" is displayed]
B. promotional poster (JPG)
C. ["QuickTime" is displayed]

File Description

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

If the related file is more than just a different format of the video, it may be useful to provide some description. This element will be displayed to the user.

Import/Export Mapping
Dublin Core - dc:relation.Q.description (.description - local qualifer) (Q = appropriate qualifier per "Relation Type" above)
MODS - (relatedItem type="Q")(abstract) (Q = appropriate qualifier per "Relation Type" above)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. [none, format only]
B. Promotional poster featuring artist rendering of dancer, woods and listing date, location, contact information for festival. Excellent example of 1920s stylized advertising.
C. [none, format only]

File Specifications

File Locator
File Size
Format
Digitization Date

The File Specification elements will identify the details that make the related files unique and enable the system to retrieve the file when called by a user.

File Locator

Required?

Yes

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will hold a URL, URI, or other filepath that will be invoked to retrieve the file when requested by a user.

Import/Export Mapping
Dublin Core - dc:relation.Q.identifier (.identifier - ViDe qualifer) (Q = appropriate qualifier per "Relation Type" above)
MODS - (relatedItem type="Q")(identifier) (Q = appropriate qualifier per "Relation Type" above)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. http://www.wgbh.org/CWF/alearly.mov
B. http://www.oldfilm.org/ocg/publicMainView.cfm?id=571
C. http://www.vet.uatlantis.edu/20050405_OR3A02.mp4

File Size

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will identify the file size in megabytes (MB) or kilobytes (K). The file size will be presented to users next to the File Name to aid in determining downloading speed.

Import/Export Mapping
Dublin Core - dc:relation.Q.format.size (.format - local qualifer) (Q = appropriate qualifier per "Relation Type" above)
MODS - (relatedItem type="Q")(physicalDescription) (Q = appropriate qualifier per "Relation Type" above)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. 500 MB
B. 400K
C. 850 MB

File Format

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will identify the format/medium of the file. Administrators will select from a controlled list of formats or add their own as new formats develop.

Import/Export Mapping
Dublin Core - dc:relation.Q.format.medium (.format.medium - ViDe qualifer) (Q = appropriate qualifier per "Relation Type" above)
MODS - (relatedItem type="Q")(physicalDescription) (Q = appropriate qualifier per "Relation Type" above)
MARC - (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. MPEG-4
B. JPEG
C. QuickTime

Digitization Date

Required?

Repeatable?

Yes, with Related Files Group of elements

Dependent?

Yes

Description:

This element will hold the date the file was digitized. This will assist users in distinguishing files that may have been digitized using an older version of a particular format. This element will contain an actual date as expressed in YYYYMMDD form. The date will be displayed with the month spelled out for easier identification. Only those parts of the date that are not "00" will be displayed.

Import/Export Mapping
Dublin Core - dc:relation.Q.creationdate (.creationdate - local qualifer) (Q = appropriate qualifier per "Relation Type" above)
MODS - (relatedItem type="Q")(date) (Q = appropriate qualifier per "Relation Type" above)
MARC - 518 (MARC mapping still in process)
MIC - no MIC map
(Above link to element registries. For introductions, see: DC, MODS, MARC, MIC)

Examples:

A. 2 June 2002 (20020602)
B. 23 January 2005 (20050123)
C. 17 April 2005 (20050417)

Custom Elements

Required?

Repeatable?

Yes

Dependent?

Description:

The Toolkit will be designed to serve a diverse group of institutions and individuals that wish to make their moving image collections available via the Web. It will be as flexible as possible, while remaining simple and easy to use. It would be impossible to anticipate the metadata needs of every institution so the Toolkit will include Custom Elements that can be used to incorporate more detailed information/metadata desired by users (e.g., production, preservation, technical, historical/contextual).

Toolkit Administrators/Catalogers can add as many custom elements as they feel would provide added benefit to their users. Due to the technical complexity of integrating custom elements, only three will be browsable in the default installation of the Toolkit. The Toolkit, however, will be built with MySQL and PHP (open source software products) with the intention that institutions/individuals with greater customization needs can easily modify the Toolkit structure and interfaces to accommodate their collection and users.

The default installation of the Toolkit will show the Browsable Custom Elements on the main "Details" page for each video. All additional custom elements will be displayed on a separate "Additional Details" page accessible by a link from the "Details" page.

Import/Export Mapping
Details of the mapping options for Custom Elements are being developed.

Examples:

n/a

Top of Page

Metadata Schema Details

Title Information

Agents Responsible (for the creation and/or dissemination of the moving image)

Mapping to DC (Dublin Core)

Mapping to MODS (Metadata Object Description Schema)

Mapping to MARC (MAchine-Readable Cataloging) in process

Mapping to MIC (Moving Image Collections)

Table of Contents / Scene List

Content Summary

Subject Matter

Participant Credits

Notes

Description

Dates

Mapping to DC (Dublin Core)

Mapping to MODS (Metadata Object Description Schema)

Mapping to MARC (MAchine-Readable Cataloging)

Mapping to MIC (Moving Image Collections)

Contextual Information

Related Videos in the Library

Rights for Reproduction and Re-use

Related Files

Custom Elements