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
|
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 We will consider mapping 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>? |
Example Records |
...