Presentation is loading. Please wait.

Presentation is loading. Please wait.

Dublin Core Application Profiles and the OCLC Digital Gateway

Similar presentations


Presentation on theme: "Dublin Core Application Profiles and the OCLC Digital Gateway"— Presentation transcript:

1 Dublin Core Application Profiles and the OCLC Digital Gateway
New tools for improving discoverability of digital collections Please list me last in the list of authors on this one.  Thanks! Sandra Allyson Mower, University of Utah Cheryl Walters, Utah State University Sandra McIntyre, Mountain West Digital Library

2 Catalogue of Boston Medical Library Arranged in Numerical Order: Manuscript,

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

4 The Card Catalog at the University of Pennsylvania Library http://bit

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

6 Harvested environments arose in early 2000s

7 Semantic web connects metadata + content

8 Application profiles manage metadata and help librarians build digital collections

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

10

11 A group of metadata experts developed the profile
Chair Cheryl Walters (USU) Task force members Sandra McIntyre (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)

12 Dublin Core contained the terms we needed

13

14 Putting it into practice
Mountain West Digital Library in Ex Libris Primo WorldCat via Digital Collection Gateway So, how does the Application Profile we have developed help us manage our digital collections?  There are two ways we have put it into practice this spring: --With the implementation of the Mountain West Digital Library into the new integrated discovery tool, Ex Libris Primo and, --With the uploading of our digital collections into WorldCat using the new Digital Collections Gateway,. These tools have made it possible for us to SEE how our metadata is being mapped, and to CONTROL that mapping.  This makes our digital collections more DISCOVERABLE and more useful to a wider audience.

15 Mountain West Digital Library
Search portal at 340 collections from 11 repositories 50 partners 300,000 records Rich metadata from a variety of sources First, the Mountain West Digital Library, or MWDL, is a regional digital collaborative for Utah, Nevada, and other states in the Mountain West.   The search portal at mwdl.org provides free access to over 340 collections from 11 different repositories.  These collections are maintained by about 50 different partnering organizations, including libraries, archives, museums, historical societies, state agencies, counties, and municipalities.  There are currently more than 300,000 items available, and each has rich metadata assigned to it, from many different academic disciplines and areas of expertise.

16 Mountain West Digital Library
Goals: Interoperable shared metadata Consistent searching and browsing for users Organized for a variety of access paths through the portal Started in 2001, the MWDL has these goals for its portal:

17 Migrating to Ex Libris Primo
An integrated discovery system Sits on top of other library systems and provides integrated access Catalog Article databases E-books E-journals Digital collections The Mountain West Digital Library is in the process of migrating to a new tool, Primo from Ex Libris.  This new integrated discovery layer for digital collections in MWDL will allow us to take advantage of the full power of the new Application Profile. Primo sits on top of other library systems, and it provides integrated access to all of them.  For the first time, it is possible to give "one-stop searching" for all sorts of records, from the traditional catalog, to article databases, e-books, and e-journals, as well as the digital collections maintained by our many partners. 

18 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 Primo provides powerful searching capabilities, with the option to refine results using facets.  It also streamlines the harvest of records from different sources, using the Open Archives Initiative, or OAI, protocols for metadata harvesting. Finally, it facilitates the online delivery of full records and the resources themselves, if they are available online.  For non-digital resources, Primo displays availability information and directs the patron to typical catalog functions such as placing a hold on a book or saving your favorites in a list for later perusal.

19 Migrating to Ex Libris Primo
Here is an example of a Primo website, the new Primo portal at the University of Utah, one of the partner libraries of the Mountain West Digital Library This site is going live within the next day or two and will be available at this URL. The Mountain West Digital Library Primo site will be similar to this and will be available within the next few weeks.   Looking at this interface, you can see that the search is very simple up front ... but it delivers a lot of power ... IF the metadata for all the resources adheres to common standards, such as the MWDL Application Profile. The University of Utah has used the MWDL Profile for its digital collections in this Primo implementation, and, as a result, the digital collections can be searched in a wide variety of ways. 

20 Applying the Profile in MWDL-Primo
Harvesting metadata from different repositories The Dublin Core Application Profile is applied with the Mountain West Digital Library when the metadata records are harvested into MWDL-Primo from the different repositories.

21 Applying the Profile in MWDL-Primo
Mapping metadata fields to Primo fields During the harvest, the normalization rules set up in MWDL-Primo map the metadata fields to Primo fields. This process looks for metadata fields that conform to the Application Profile.

22 Applying the Profile in MWDL-Primo
Mapping metadata fields to Primo fields For example, while harvesting a digital collection, if Primo finds a Dublin Core field for <dc:date> in the OAI stream of metadata, it maps it to Primo's "Creation date" field.

23 Results in Facets If the metadata has been entered according to the constraints set in the Dublin Core Application Profile, search results can be intelligently faceted, and patrons can refine their searches to select, for example, only items from a certain range of dates.

24 Wrapping up the conversion
Training of collection partners Conformance review and "Metadata Clinics" Sharing the process with colleagues in various venues The success of the conversion to the new Application Profile will depend on the cooperation of MWDL partners in taking advantage of the new elements and refinements in the Profile. We plan to create some training, both online and through webinars.  This summer we will review selected collections and make suggestions to partners for changes.  We also hope to hold some Metadata Clinics, to answer questions and encourage partners to bring up issues they are encountering.  Finally, we intend to share the Application Profile and the process of creating it with other colleagues in various venues.

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

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

27 Solving problems with new guidelines
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 Test of speaker notes 2

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

29 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: Format:  The file format, physical medium, or dimensions of the resource             (image/jp2, 45 minutes) MARC 300 or 340 Type:  The nature or genre of the resource (image, audio, text) MARC 655

30 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   yyyy-mm-dd (ex ) yyyy-mm (ex ) yyyy (1999) yyyy-yyyy for date range (ex )

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

32 Same thing… Only different!
Dublin Core Best Practices and Profile Same thing… Only different! OCLC’s Best Practices 1 2 While MWDL was working on its application profile, another group of OCLC libraries was working on a similar set of Best Practices and a marvelous new tool was being developed at OCLC:  the Digital Collections Gateway. MWDL Application Profile

33 Opening your collections to the World via WorldCat
How to get from this To this 1.5 billion  items available here...

34 OCLC’s new Digital Collections Gateway
3 OCLC’s new Digital Collections Gateway Crosswalk DC data into MARC WorldCat record See effects of following your DC Profile Can see and edit mapping Can generate WorldCat 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

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

36

37 Preview how fields will map in MARC WorldCat record

38 Editing tools inside the Gateway

39 Preview the record

40 DC Summary shows how often a field is used

41 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

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

43 Want to break up field into multiple fields?

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

45 An item level record

46

47 Collection-level record describes the entire collection

48 "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)

49 Questions? Cheryl Walters cheryl.walters@usu.edu Allyson Mower
Sandra McIntyre


Download ppt "Dublin Core Application Profiles and the OCLC Digital Gateway"

Similar presentations


Ads by Google