Hannah Wilson Final Project-Metadata Application Profile Design Metadata Applications Summer 2012 Application Scenario WCTN, a Detroit

local news station, has a video library of news segments from the last thirty years that need to be preserved and made accessible. They have hired our company to preserve, store, and make their historic and current video libraries digitally accessible for use internally, by member institutions, and by various third parties (i.e., broadcasters, TV and film producers, advertisers, etc.). In an effort create a digital library that will allow for rich, detailed, and precise searches, our company is creating timeline based metadata for numerous 30minute news segments (segments are roughly 20 minutes when commercials are extracted). Timeline based metadata will be generated based on two-minute increments of each broadcast. Historically, WCTN has attached free-text descriptions to the segments but timeline based descriptions will allow users to perform complex searches and retrieve specific and meaningful results. WCTN has provided the videos and their native, descriptive metadata. The existing metadata will be repurposed into a local scheme created by our company and new fields will be added to enhance access. Our goal is to create granular metadata that allows for both asset-level retrieval of full-length videos as well as moment-level retrieval of subject specific clips. This project contains one data dictionary with functional requirements and element descriptions and occurrence as well as crosswalk mappings to MODS and Dublin Core. Additionally, 8 fully cataloged metadata records are included, representing subject specific video clip increments for one news segment found in WCTNs video library. Each record will contain descriptive, administrative, and structural metadata. Automated Technologies and Time-based Metadata Time-based metadata (as opposed to asset level metadata) refers to frame-by-frame metadata tags allowing access to the various content contained within one film or video or in this case, one news segment My scheme includes Core elements as well as several more specific elements. Much of the input could (and would) be automated, specifically, the digital processing details. Other automated technologies would include ad-break detection and the ability to remove sponsor icons that may infringe on copyright laws as well as spatial recognition (of faces), phonetic recognition (voices), and script synching. What these automated technologies cannot do is interpret the subject, emotion/tone, and other human described details. This scheme are the fields I tried to capture in my scheme. Fields such as Event Primary, Event Secondary, Location Depicted, and Description allow the cataloger to attach tags and free text that cannot be automated.

Data Dictionary / Encoding Scheme / Crosswalk Fields: * Required 1. Title* 2. Alternative Title 3. Event Primary* 4. Event Secondary 5. Name 6. Name Type 7. Name Role 8. Name Dates 9. Name Gender 10. Description 11. Language* 12. Color* 13. Sound* 14. Duration* 15. Date* 16. Date Type 17. Location Depicted* 18. Location Type 19. Collection Name* 20. Collection Description* 21. Original Owner* 22. Local System Record ID* 23. Use Permissions* 24. Rights License* 25. File Format* 26. File Name* 27. File Locator* 28. Digitization Date 29. Clip Duration* 30. File Duration* 31. Downloading Requirements* 32. Processing Hardware* 33. Processing Software* 34. Notes 35. Media Processor*

Element Title

Specifications Required: yes Controlled: no Repeatable: yes Searchable: yes Required: yes Controlled: no Repeatable: yes Searchable: yes

Description and Notes Main/official title of the video. Ex: NBC News Overnight. WTCN 5/3/1983 For titles of clips within fulllength movies, constructed by cataloger. An alternative title might be a shorter version of the official title, a common "nickname," or a translated version of the title. Use for shortened title to describe the isolated clip, if applicable. Ex: NBC News Overnight. WTCN 5/3/1983: Coalinga California Earthquake

Encoding and Rules Provided by original owner of video content. Format indicated in native metadata will be honored. Follow format: Title: Alternative title

MODS Crosswalk <titleInfo><title>

Dublin Core Crosswalk dc:title

AlternativeTitle

<titleinfo><subTitle>

dc:title:alternative

EventPrimary

Required: yes Controlled: editable and dropdown menu Repeatable: yes Searchable: yes

Event depicted in video. Primary event relates to the main happening. Ex: earthquakes elections

LCSH AAT

<subject><topic>

dc:subject

EventSecondary

Required: yes Controlled: editable and dropdown menu Repeatable: yes Searchable: yes

Event depicted in video. Secondary event could be object depicted, instance occurring such as an interviewgeneral topics besides the primary event. Ex: bulldozer natural events

LCSH AAT

<subject><topic>

dc:subject

Name

NameRole

Required: no Controlled: editable and dropdown menu Repeatable: yes Searchable: yes Required: yes Controlled: editable and dropdown menu Repeatable: yes Searchable: yes Required: no Controlled: editable and dropdown menu Repeatable: no Searchable: no

Name of subject person or corporation depicted in video. Ex: Mike Sanford Role of person or corporation depicted in video. Ex: newscaster Personal or corporate name type.

Provided by original owner of video content. Format indicated in native metadata will be honored. LCSH

<subject><name>

dc:subject would have to map all details of name field to name.

<subject><namePart>

NameType

Options: personal corporate

<subject><nameRole>

NameDates

Required: no Controlled: editable and dropdown menu Repeatable: no Searchable: no

NameGender

Required: no Controlled: editable and dropdown menu Repeatable: no Searchable: yes

For personal names it is usually a general date derived from the date of the newscast. Use personal dates (birth, death, active) when available. Fuzzy date capability allows for broader searches. Ex: 1980s Gender of subject depicted in video, if available. Ex: male

<subject><namePart> Format: 1980s, 1990s.

Options: male / female, unknown not applicable

<subject><namePart>

Description

Required: no Controlled: no Repeatable: no Searchable: yes

Summary of the contents of the video to assist end users in identifying the relevance of the video for their needs.

It is 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.

<note>

dc:description

Language

Required: no Controlled: no Repeatable: no Searchable: no

Additional languages, subtitles, and other information

ISO 639

<language>

dc:language

Color

Required: yes Controlled: yes Repeatable: no Searchable: yes

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. This element will identify Options: whether the video is black and white fundamentally Black and color White, Color, or Colorized. Specific notes about color can be included in the Note element. Ex: Black and White. This element will identify whether the video is accompanied by sound Ex: Yes This element will identify the total duration of the moving image. The time can be expressed to the second. Options: Yes No Ex: 00:59:03 - 00:13:48

<physicalDescription>

dc:format

Sound

Required: yes Controlled: yes Repeatable: no Searchable: yes Required: yes Controlled: yes Repeatable: no Searchable: yes

<physicalDescription>

dc:format

Duration

<physicalDescription>

dc:format

Date

Required: yes Controlled: editable and dropdown menu Repeatable: yes Searchable: yes Required: yes Controlled: editable and dropdown menu Repeatable: yes Searchable: yes Required: yes Controlled: editable and dropdown menu Repeatable: yes Searchable: yes Required: yes Controlled: yes Repeatable: no Searchable: yes

As specific as posibble but is dependent on native metadata from owner. May just include the year.

Ex: 7/2/89

<originInfo>

dc:date

DateType

Ex: captured

Options: captured; created; altered; broadcast

<originInfo><subelements >

Location depicted

Name of the location depicted or featured within the clip or film. Ex: Coalinga (California, United States) If a video is part of one or more larger collections or is a clip of a full video, this would be noted in this element. Ex: NBC News Overnight WTCN.

TGN

<subject><geographic> or <subject><topic>

dc:coverage:spatial dc:coverage:temporal

Collection Name

Provided by original owner of video content. Format indicated in native metadata will be honored.

Collection Description

Required: no Controlled: no Repeatable: no Searchable: yes

Descriptive information about collection. Ex: WTCN, is an NBCaffiliated television station based in Detroit, Michigan, United States. It is owned by PostNewsweek Stations and is the flagship station and home base of the group with the offices of the group located alongside WDIV's studios; the "Local" branding now utilized by all stations in the group was launched here alongside its acquiring of flagship status in 2000. It is the only major television station in the area whose offices and studios are located in the city of Detroit, while its other television station counterparts are located in Southfield.

Provided by original owner of video content. Format indicated in native metadata will be honored.

<description>

dc:description

Original owner

Required: yes Controlled: yes, dropdown menu Repeatable: no Searchable: yes

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.

Provided by original owner of video content. Format indicated in native metadata will be honored.

<originInfo>

dc:publisher

Local System Record ID

Required: yes Controlled: yes, dropdown menu Repeatable: yes Searchable: yes Required: yes Controlled: yes, dropdown menu Repeatable: yes Searchable: yes

This element will be used to Automated. contain a reference number from an institution's local system (catalog, inventory list, etc.). 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. legal text defining the details of the rights granted to the user as described generally in the Use Permissions. Provided by original owner of video content. Format indicated in native metadata will be honored.

<recordInfo><recordIdenti dc:identifier fier>

Use permissions

<accessCondition>

dc:rights statement

Rights License

Required: no Controlled: yes, dropdown menu Repeatable: no Searchable: no

Provided by original owner of video content. Format indicated in native metadata will be honored.

<accessCondition>

dc:rights statement

File format

File name

Required: yes Controlled: yes Repeatable: no Searchable: no Display: yes Required: yes Controlled: yes Repeatable: no Searchable: no Display: yes Required: yes Controlled: no Repeatable: no Searchable: no Display: yes

Type of file uploaded (.avi, .mov)

Automated.

<typeOfResource>

dc:format:medium

Name of digital file with extension. Ex: WXZY_JUNE1977_1342.mo v This element will hold a URL, URI, or other filepath that will be invoked to retrieve the file when requested by a user.

Automated.

<identifier>

dc:identifier

File Locator

Automated.

<location><url>

dc:identifier

Digitization date Required: no Controlled: no Repeatable: no Searchable: no Display: no Clip duration Required: yes Controlled: yes Repeatable: no Searchable: no Display: yes Duration of clip.

Expressed ex: 7/2/89

<originInfo><dateCapture d>

dc:date:created

Expressed as: 2 minutes 15 seconds

<physicalDescription><ex tent>

dc:format:extent

File duration

Required: yes Controlled: yes Repeatable: no Searchable: no Display: yes Required: no Controlled: yes Repeatable: no Searchable: no Display: yes Required: yes Controlled: yes Repeatable: no Searchable: no Display: no Required: yes Controlled: yes Repeatable: no Searchable: no Display: no Required: no Controlled: no Repeatable: no Searchable: no Display: no

Duration of full-length video file.

Expressed as: 30 minutes

<physicalDescription><ex tent>

dc:format:extent

Downloading requirements

Program needed for Automated. downloading if applicable. Video encoding information e.g. (H.264, MPEG-4, 300/800 kbps.) Ex: Apple Intel Core Duo Automated.

<accessCondition>

dc:rights statement

Processing Hardware

Processing Software

Notes

Type of software used to Automated. process video. Ex: Sorenson Squeeze, version 8 settings: F8, 2MB/S, VP6 Pro, Mp3 Additional notes regarding technical aspects of file.

<description>

dc:description

Media Processor Required: yes Controlled: no Repeatable: no Searchable: no Display: no Comments

Name of individual responsible for cataloging record.

First and last name.

<recordInfo>

One of the biggest lessons I have learned from this assignment was not to underestimate the importance of careful and meticulous planning. I learned with experience why it is so crucial to consider all aspects of metadata application profiles when building a local scheme. I was thankful that the project was broken down into steps because it forced me to consider every aspect of metadata design as a process. Otherwise, I would have wanted to jump straight in and start cataloging the records. In researching for this project, it was interesting to consider metadata from a corporate and commercial standpoint where major objectives are predominantly monetary rather than educational or in the interest of preservation. In the business realm, access drives demand. Rich and granular metadata allows for enhanced access, which drives user experience and unlocks value for consumers. I decided to break up my elements into three sections: Content, Content, and Digital File; although I found that several of the fields overlap. I consulted several online resources when creating my scheme such as the Open Video Project Toolkita web-based digital library project established at the University of North Carolina at Chapel Hill; and University of Washingtons Special Collections Moving Image Collection Data Dictionary. One of the biggest challenges of this project was projecting what Ive learned from working in a library setting into a commercial/corporate setting. In a business setting such as the one in my scenario, interoperability is not a concern for long-term use; mapping media to an existing metadata schema (cultural heritage or otherwise) is not usually a consideration. However, I have even more of an appreciation now for library and cultural heritage cataloging standards. Following standards forces the metadata designer to consider aspects that they may have missed. I found myself consulting VRA Core, MODS, and Dublin Core documentation when creating a local scheme for insight about fields that I may have not considered. Ive learned that a big part of metadata design is trial and error. If this project became an actual online collection, I would certainly rely on user feedback before launching a final version of the scheme.