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

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

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

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)