Dublin Core Application Profiles and the OCLC Digital

Dublin Core Application Profiles and the OCLC Digital Gateway New tools for improving discoverability of digital collections Allyson Mower, University of Utah Cheryl Walters, Utah State University Sandra Mc. Intyre, Mountain West Digital Library

Catalogue of Boston Medical Library Arranged in Numerical Order: Manuscript, 1816 -1825

Supplementary Catalogue of Books added to the San Francisco Free Public Library , 1888.

The Card Catalog at the University of Pennsylvania Library http: //bit. ly/dy 1 anc

Cataloging rules have changed over time Format Cards Content Rules Format Rules ALA Cataloging Rules 1880 s Info Universe Local Cards Print/Fiche Union Catalogs Cards AACR ISBD & G Cooperative Card Production MARC AACR 2, APPM OCLC Bib Shared catalogs & Formats online union catalogs EAD DACS Dublin Core BCR/CDP Dublin Core Best Practices Dublin Core Application Profiles Local, Consortia DCMI Local, Consortia & Worldwide Web

Harvested environments arose in early 2000 s

Semantic web connects metadata + content

Application profiles manage metadata and help librarians build digital collections

Application profiles manage metadata and help librarians build digital collections Author's Manuscript Peer-reviewed Manuscript copyright holder Author Published Article copyright holder Publisher

http: //mwdl. org

A group of metadata experts developed the profile Chair Cheryl Walters (USU) Task force members Sandra Mc. Intyre (MWDL) Kayla Willey (BYU) Cory Lampert (UNLV) Gina Strack (Utah State Archives) Jan Robertson (UU) Tawnya Mosier (UU) Allyson Mower (UU) Ray Matthews (Utah State Library)

Dublin Core contained the terms we needed

Putting it into practice • Mountain West Digital Library in Ex Libris Primo • World. Cat via Digital Collection Gateway

Mountain West Digital Library Search portal at http: //mwdl. org • 340 collections from 11 repositories • 50 partners • 300, 000 records • Rich metadata from a variety of sources

Mountain West Digital Library Goals: • Interoperable shared metadata • Consistent searching and browsing for users • Organized for a variety of access paths through the portal

Migrating to Ex Libris Primo An integrated discovery system Sits on top of other library systems and provides integrated access o o o Catalog Article databases E-books E-journals Digital collections

Migrating to Ex Libris Primo • Powerful searching, with ability to refine results (facets) • Powerful harvesting of digital collections via Open Archives Initiative (OAI) • Online delivery of records and digital resources

Migrating to Ex Libris Primo http: //search. library. utah. edu

Applying the Profile in MWDL-Primo • Harvesting metadata from different repositories

Applying the Profile in MWDL-Primo • Mapping metadata fields to Primo fields

Results in Facets

Wrapping up the conversion • Training of collection partners • Conformance review and "Metadata Clinics" • Sharing the process with colleagues in various venues

From OCLC and MWDL Working Groups, 2009 -2010 New tools & guidelines to help with metadata • ‘Best Practices’ for CONTENTdm users creating shareable metadata • Mountain West Digital Library Dublin Core Application Profile • OCLC Digital Collection Gateway

Review of previous MWDL Metadata Guidelines (2006) • Clarify & refine Split Coverage element into narrower Temporal and Spatial elements o Rename Digitization Specifications to Conversion Specifications o Adding MARC tag equivalents o • Improve harvesting o o Give more instruction on formatting Give more instruction on mapping • Improve searchability o Reliable date searching • Facilitate digital preservation o Add preservation fields for future migration of archival master files

Solving problems with new guidelines Problem: When fields collide Data runs together illegibly when multiple fields mapped into the same field Several solutions: • End each field with a semi-colon to separate data if mingled with another field • Begin second field with a prefix (ex. “Spine title”) to identify data in the field. • Map all but one multiple field “none” so that only one field harvested

Potato, Potahto, Potatoe Problem: Inconsistent use of metadata fields Temporal & Date fields o o Temporal = time period covered by intellectual content Date = when digital object created Example: Book about Civil War written in 1922 Temporal = 1861 -1865 Date = 1922 Source & Relation: o Source = Information about an original resource from which the present digital resource is derived. o Relation = Another resource related to digital object

Type versus Format Adding MARC equivalent tags clarifies meaning of fields Format & Type: Which is which Important to use the correct field so search limits will work in MWDL Knowing the MARC fields these are crosswalked to is helpful: o Format: The file format, physical medium, or dimensions of the resource (image/jp 2, 45 minutes) § MARC 300 or 340 o Type: The nature or genre of the resource (image, audio, text) § MARC 655

Getting the date right and the right date Date search failure due to improper date formatting Use date original item created Set data type to Date in field properties Format dates correctly o o yyyy-mm-dd (ex. 1776 -07 -04) yyyy-mm (ex. 1776 -07) yyyy (1999) yyyy-yyyy for date range (ex. 1901 -1967)

From OCLC and MWDL Working Groups, 2009 -2010 New tools & guidelines under development in 2009/10 to improve metadata ‘Best Practices’ for CONTENTdm users creating shareable metadata o Mountain West Digital Library Dublin Core Application Profile o o OCLC Digital Collection Gateway

Dublin Core Best Practices and Profile Same thing… Only different! OCLC’s Best Practices 1 2 MWDL Application Profile

Opening your collections to the World via World. Cat How to get from this To this 1. 5 billion items available here. . .

3 OCLC’s new Digital Collections Gateway • Crosswalk DC data into MARC World. Cat record • See effects of following your DC Profile • Can see and edit mapping • Can generate World. Cat records for each item and also a record for the entire collection • Each record is assigned a OCLC number • Automatically add OCLC numbers to metadata records for each digital object in CONTENTdm

Delete fields you don't want Don't want pixel dimensions to display? 1. Click on field. 2. Change to "No mapping" 3. Replace

• Preview how fields will map in MARC World. Cat record

Editing tools inside the Gateway

Preview the record

DC Summary shows how often a field is used

Use Frequency Analysis for quick check of mapping and data entry Oops, need to fix this – The Type “image; still image” should appear in all 2638 records, not just 23 of them

Need to block certain slides? Maybe those by one specific creator for copyright reasons?

Want to break up field into multiple fields?

Using the field prefixes/suffixes to clarify data • Added prefix “Originally taken: ” in front of 1968. • Added prefix “Date digitized” to other date.

An item level record

Collection-level record describes the entire collection

"An application profile provides a standardized way to document the important decisions that have been made about the elements, including content standards and rules for use. Such documentation can facilitate migration, harvesting, and other automated processes. " Hicks, Perkins, and Maurer (2006) "Application Profile Development for Consortial Digital Libraries" Library Resources & Technical Services 51 (2)

Questions? Cheryl Walters cheryl. walters@usu. edu Allyson Mower allyson. mower@utah. edu Sandra Mc. Intyre sandra. mcintyre@utah. edu