William F. Worford
LS566 Metadata – Digital Repository Project – Spring 2011
Spring 2011
In the Spring of 2011, the students of DC version of LS 566 Metadata were asked, as apart of their headlining ...
Introduction
 Establishing Key Stakeholders and Steering Groups for the
Repository
 Establish Metadata elements and inte...
Key Stakeholders and Steering Groups for
the Repository
 Class partitioned into groups of three
 Regular Online Class me...
Wikis, Blogs, Tweets and Presentations
 A wiki was created to centralize element’s definition and
served as a knowledge r...
Wikis, Blogs, Tweets and Presentations
Metadata Schema
 The class chose to use a modified version of Dublin Core
 Element interpretation was determined by grou...
Content Standards
 Library of Congress Thesaurus for Graphic Materials
 Library of Congress Subject Headings (LCSH)
 An...
Elements of The Resource
 Instantiation - An identifiable occurrence or occasion of something;
in the case of Dublin Core...
Instantiation
Language: A language of the resource. Recommended best practice is to
use a controlled vocabulary such as IS...
Content
Title: The name given to the resource.
Description: An account of the content of the resource. Description may inc...
Intellectual Property
Creator: The primary responsible entity for making the content of the
resource possible. Examples of...
Elements : 15 Elements
Date
Title
Relation

Instantiation:
Format Identifier

Language

Content:
Description
Coverage
Sour...
Elements : 15 Elements

Fig.1
Elements : 15 Elements

Fig.2
Elements : 15 Elements

Fig.3
Elements : 15 Elements

Fig.4
Digital Standards
 Images were scanned at high resolution and saved as tiff files (1200
pixels)
 Library of Congress Sub...
Federated Search Tools
 Omeka software used to extract image text. Connect image file with
text
 File assigned to elemen...
The Process
 The indexing process lasted throughout part of the summer due to a
tornado that crossed the state of Alabama...
Resources
“Alabama FB Nathan Cox, #40 Punts the Football, Georgia Vs. Alabama 10/5/2002.,” October
5, 2002. http://omeka....
Resources
Hillman, Diane. “Using Dublin Core.” Dublin Core Metadata Initiative, 12 April 2001.
<http://dublincore.org/doc...
Upcoming SlideShare
Loading in …5
×

Collision course presentation (corrrect)

411 views
298 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
411
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Collision course presentation (corrrect)

  1. 1. William F. Worford LS566 Metadata – Digital Repository Project – Spring 2011
  2. 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.
  3. 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
  4. 4. Key Stakeholders and Steering Groups for the Repository  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
  5. 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
  6. 6. Wikis, Blogs, Tweets and Presentations
  7. 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
  8. 8. Content Standards  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
  9. 9. Elements of The Resource  Instantiation - An identifiable occurrence or occasion of something; in the case of Dublin Core, a specific occurrence of an information resource  Content  Intellectual Property
  10. 10. Instantiation 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.
  11. 11. Content 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.
  12. 12. Intellectual Property 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.
  13. 13. Elements : 15 Elements Date Title Relation Instantiation: Format Identifier Language Content: Description Coverage Source Subject Type Intellectual Property: Contributor Creator Publisher Rights
  14. 14. Elements : 15 Elements Fig.1
  15. 15. Elements : 15 Elements Fig.2
  16. 16. Elements : 15 Elements Fig.3
  17. 17. Elements : 15 Elements Fig.4
  18. 18. Digital Standards  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
  19. 19. Federated Search Tools  Omeka software used to extract image text. Connect image file with text  File assigned to element field via Omeka upon import
  20. 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
  21. 21. Resources “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/dccitation-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 ).
  22. 22. Resources 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).

×