Metadata Crosswalks

Crosswalk	Marc to MODS Crosswalk (created 6/27/2013 KM)
Standards/Records consulted	Adapted from http://www.loc.gov/standards/mods/mods-mapping.html; June, 2013 NUL actually has in Voyager for bib records that represent sound or video recordings Recommendations of MARC usage by OLAC (the Online AudiovisualCatalogers organization) FIAF (International Federation of Film Archives) Recommendations from the assistant head of Bibliographic Services and the Senior Music Cataloger at NUL
Details of Crosswalk	Tab 1, Avalon_crosswalk: the proposed mapping, based on LC’s mapping of MARC to MODS. This is dense and meant for developers and catalogers. Tab 2, Dropped mappings: a list of elements LC maps to MODS but I decided we didn’t want. Also includes a list of elements I added to the LC crosswalk. Tab 3, MARC_NUL: Includes a list of MARC codes used in NUL’s database for any bib. record that might describe audio or video (and thus includes a lot that aren’t), a tally of how many records use each MARC field, a corresponding column of LC elements mapped, and color/font coding describing how any discrepancies should be handled. Also very dense, not for the faint of heart. Tab 4, Note: A detailed list of outstanding questions, most of which are summarized below, plus other notes. It would be great if somebody at IU in cataloging who’s familiar with the Variations mapping could look this over and let us know what they think.
Unresolved Issues	Variations uses the MARC 655 (Genre), MARC 047 (Form of Musical Composition Code), and 008/18 (Form of composition). We'd decided early on not to use <genre> in the Resource Description page, but can easily reconsider. So: Is it important to have the Form of Musical Composition Codes mapped to MODS <genre>? IU maps MARC 048 to an element called mediumOfPerformance. This MARC field holds a code for instruments and the number of parts. This is NOT in the LC mapping and there is no obvious MODS element for it. Should keep it? If so, it will likely go into a MODS note or into an extension element. Variations keeps the Target Audience field, which I don't believe is used much at NUL. Is this important to keep? We'd also decided early on not to use this MODS element, which is called <tartetAudience>, in the Resource Description page. I’ve suggested dropping most local notes but IU doesn't do that for Variations. Our music & video catalogers think it's not useful "unless they contain NUL specific information", but it's difficult to determine without human interaction. Is there systematic use of local notes that is reliably useful at IU? I have dropped all elements that describe characteristics of the media which will be automatically generated at the time of ingest, including Playing Time, which is not mapped by LC but would likely map into a child of the MODS <physicalDescription> element. Is there any reason not to do this?
Example Records	NULMARC_Video1_201206.xml IUMARC_Audio1_201206.xml IUMARC_Video1_201206.xml