Collision course presentation (corrrect)

22
William F. Worford LS566 Metadata – Digital Repository Project – Spring 2011 1 University of Alabama Football

description

 

Transcript of Collision course presentation (corrrect)

Page 1: Collision course presentation (corrrect)

William F. Worford

LS566 Metadata – Digital Repository Project – Spring 2011

1

University of Alabama Football

Page 2: Collision course presentation (corrrect)

Saturday, April 8, 2023

2

Spring 2011

In the Spring of 2011, the students of DC version of LS 566 - Metadata were asked, as apart of their headlining assignment to index a series of six images. The Collection of these images would feature photos from the University of Alabama Crimson Tide 1992 football season.

Page 3: Collision course presentation (corrrect)

Saturday, April 8, 2023

3

Introduction

Establishing Key Stakeholders and Steering Groups

for the Repository Establish Metadata elements and interpretation of

those elements Software, hardware (server storage) and

parameters for Metadata Schema Time table completion

Page 4: Collision course presentation (corrrect)

Class partitioned into groups of three

Regular Online Class meetings were set aside for students to present a metadata schema for class exposure and to determine which schema would be used for the indexing project

Saturday, April 8, 2023

4

Key Stakeholders and Steering Groups for the Repository

Page 5: Collision course presentation (corrrect)

Saturday, April 8, 2023

5

Wikis, Blogs, Tweets and Presentations

A wiki was created to centralize element’s definition and served as a knowledge resource center for the project

Dublin Core and VRA Core were the front runners for the schema of choice at the first part of the semester

Students were required to publish 5 blog entries per week and tweet using the hashtags #ls566 and #metadata

Page 6: Collision course presentation (corrrect)

Saturday, April 8, 2023

6

Wikis, Blogs, Tweets and Presentations

Page 7: Collision course presentation (corrrect)

Saturday, April 8, 2023

7

Metadata Schema

The class chose to use a modified version of Dublin Core Element interpretation was determined by groups of 4 in the

form of a process of elimination Customized Mapping of Elements mainly followed simple

Dublin Core standards

Page 8: Collision course presentation (corrrect)

Library of Congress Thesaurus for Graphic Materials

Library of Congress Subject Headings (LCSH)

Anglo - American Cataloguing Rules, Second Edition, 2002 Revision (AACR2 2002) for creation of new entries

Saturday, April 8, 2023

8

Content Standards

Page 9: Collision course presentation (corrrect)

Instantiation - An identifiable occurrence or occasion of something; in the case of Dublin Core, a specific occurrence of an information resource

Content

Intellectual Property

Saturday, April 8, 2023

9

Elements of The Resource

Page 10: Collision course presentation (corrrect)

Language: A language of the resource. Recommended best practice is to use a controlled vocabulary such as ISO 639-2. Example: “eng” for English.

Identifier: An unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string conforming to a formal identification system, such as an ISBN.

Date: A date associated with the creation or availability of the resource. Recommended best practice is defined in a profile of ISO 8601 that includes dates of the forms YYYY and YYYY-MM-DD among several others.

Format: The file format, physical medium or dimensions of the resource. Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]. Example: tiff.

Saturday, April 8, 2023

10

Instantiation

Page 11: Collision course presentation (corrrect)

Title: The name given to the resource.

Description: An account of the content of the resource. Description may include but is not limited to: an abstract, table of contents, reference to a graphical representation of content, and/or a free-text account of the content.

Subject: The topic of the content of the resource. Typically, a subject will be expressed as keywords or key phrases or classification codes that describe the topic of the resource.

Coverage: The extent or scope of the content of the resource. Coverage will typically include spatial location (a place name or geographic co-ordinates), temporal period (a period label, date, or date range) or jurisdiction. (such as a named administrative entity)

Source: A reference to a resource from which the present resource is derived. The present resource may be derived from the Source resource in whole or part.

Type: The nature or genre of the content of the resource. Type includes terms describing general categories, functions, genres, or aggregation levels for content.

Relation: A reference to a related resource.Saturday, April 8, 2023

11

Content

Page 12: Collision course presentation (corrrect)

Creator: The primary responsible entity for making the content of the resource possible. Examples of a Creator include: a person, an organization or a service.

Contributor: An entity responsible for making contributions to the content of the resource. Examples of a Contributor include a person, an organization or a service. Typically, the name of a Contributor should be used to indicate the entity.

Publisher: The entity responsible for making the resource available. Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.

Rights: Information about rights held in and over the resource. Typically a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource.

Saturday, April 8, 2023

12

Intellectual Property

Page 13: Collision course presentation (corrrect)

Instantiation: Date Format Identifier Language

Content: Title Description Coverage

Relation Source Subject Type 

Intellectual Property: Contributor Creator Publisher Rights

Saturday, April 8, 2023

13

Elements : 15 Elements

Page 14: Collision course presentation (corrrect)

Saturday, April 8, 2023

14

Elements : 15 Elements

Fig.1

Page 15: Collision course presentation (corrrect)

Saturday, April 8, 2023

15

Elements : 15 Elements

Fig.2

Page 16: Collision course presentation (corrrect)

Saturday, April 8, 2023

16

Elements : 15 Elements

Fig.3

Page 17: Collision course presentation (corrrect)

Saturday, April 8, 2023

17

"Alabama FB Nathan Cox, #40 punts the football, Georgia vs. Alabama 10/5/2002.," in ls566-spring2011 Football Images, Item #641, http://omeka.slis.ua.edu/ls566-spring2011/football-images/items/show/641 (accessed August 17, 2013).

Elements : 15 Elements

Fig.4

Page 18: Collision course presentation (corrrect)

Images were scanned at high resolution and saved as tiff files (1200 pixels)

Library of Congress Subject Headings (LCSH)

Anglo - American Cataloguing Rules, Second Edition, 2002 Revision (AACR2 2002) for creation of new entries

Saturday, April 8, 2023

18

"Alabama QB Watts (#14) in mid-air during touchdown play; Alabama vs. LSU, 11/16/2002," in ls566-spring2011 Football Images, Item #645, http://omeka.slis.ua.edu/ls566-spring2011/football-images/items/show/645 (accessed August 14, 2013).

Digital Standards

Page 19: Collision course presentation (corrrect)

Omeka software used to extract image text. Connect image file with text

File assigned to element field via Omeka upon import

Saturday, April 8, 2023

19

Federated Search Tools

Page 20: Collision course presentation (corrrect)

Saturday, April 8, 2023

20

The Process

The indexing process lasted throughout part of the summer due to a tornado that crossed the state of Alabama

The storm caused severe damage throughout the northwest section of Alabama including the city of Tuscaloosa where the University of Alabama resides

Some students worked on the project despite not having running water and maintained communication via tweets and blog entries

Page 21: Collision course presentation (corrrect)

“Alabama FB Nathan Cox, #40 Punts the Football, Georgia Vs.  Alabama 10/5/2002.,” October 5, 2002. http://omeka.slis.ua.edu/ls566-spring2011/football-images/items/show/641.

Apps, Ann. "Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata.” Dublin Core Metadata Initiative. 13 June 2005. <http://dublincore.org/documents/dc-citation-guidelines/> (15 January 2007).

Beckett, Dave, Eric Miller, and Dan Brickley. "Expressing Simple Dublin Core in RDF/XML.” Dublin Core Metadata Initiative, 31 July 2002. <http://dublincore.org/documents/dcmes-xml/> (15 January 2007).

DCMI Usage Board. “DCMI Type Vocabulary.” Dublin Core Metadata Initiative, 28 August 2006. <http://dublincore.org/documents/dcmi-type-vocabulary/> (23 January 2007).

--- "Dublin Core Metadata Terms." Dublin Core Metadata Initiative, 18 December 2006. <http://dublincore.org/documents/dcmi-terms/> (15 January 2007).

Dublin Core Metadata Initiative. “DCMI Term Declarations Represented in XML Schema Language.” Dublin Core Metadata Initiative, 10 April 2006. <http://dublincore.org/schemas/xmls/> (23 January 23, 2007).

Dublin Core Metadata Initiative. "Dublin Core Metadata Element Set, Version 1.1." Dublin Core Metadata Initiative, 18 December 2006. <http://dublincore.org/documents/dces/> (15 January 2007).

Resources

Saturday, April 8, 2023

21

Page 22: Collision course presentation (corrrect)

Hillman, Diane. “Using Dublin Core.” Dublin Core Metadata Initiative, 12 April 2001. <http://dublincore.org/documents/2001/04/12/usageguide/sectc.shtml> (15 January 2007).

Lagoze, Carl and Herbert Van de Sompel, ed. “The Open Archives Initiative Protocol for Metadata Harvesting,” Version 2.0. The Open Archives Initiative, 14 June 2002, <http://www.openarchives.org/OAI/openarchivesprotocol.html> (23 January 2007).

Powell, Andy. "Expressing Dublin Core in HTML/XHTML Meta and Link Elements.” Dublin Core Metadata Initiative, 30 November 2003. <http://dublincore.org/documents/dcq-html/> (15 January 2007).

Powell, Andy and Pete Johnston. "Guidelines for implementing Dublin Core in XML.” Dublin Core Metadata Initiative, 2 April 2003. <http://dublincore.org/documents/dc-xml-guidelines/> (15 January 2007).

Rider, Jody.” 15 metadata elements for the description of resources… especially digital resources.” Digital Libraries LS 565, Spring 2007.(15 August 2013.

Woodley, Mary, Gail Clement, and Pete Winn. "DCMI Glossary.” Dublin Core Metadata Initiative, 7 November 2005.<http://dublincore.org/documents/usageguide/glossary.shtml> (15 January 2007).

Resources

Saturday, April 8, 2023

22