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. Update: IU catalogers for sound recordings and film/video consulted and answers/decisions to questions noted.
We will consider mapping the MARC 047 (form of composition) element in some circumstances if we find we're not getting sufficient data from other elements (i.e., 655 and 008/18-19 when Leader/06=j)
The MARC to MODS Crosswalk for Avalon reflects a much more complete list of fields than is currently available for use in Avalon Media System. We are aiming high and this crosswalk reflects where we would like to end up. - 01/08/2015
Adds support for various notes and for system identifiers other than the bibliographic identifier used to import MARC metadata. Moves the location of the bibliographic identifier from mods/identifer to mods/relatedItem@type="original"/identifer and adds the attribute "source" to the element recordInfo/recordIdentifier.
Case 1 - Resource Description Form: MARC fields from Z39.50 call based on a single supplied unique identifier needs to populate the Resource Description form.