Algorithm for Batch Loading Variations Metadata from MARC

Algorithm - Major Processing Steps
MARC Record Groupings
Collective titles black and white lists
Form list

Algorithm - Major Processing Steps

  1. Contributor Record Creation
  2. Work Record Creation
  3. Container Record Creation
  4. Instantiation Record Creation (for those works created above)
  5. Container Record Mapping (second pass, to account for instantiations not created)

Full Mapping Table

MARC Record Groupings

Collective titles "black" and "white" lists

List includes selected terms from http://www.library.yale.edu/cataloging/music/musicat.htm#uniformtitles

Does not account for arbitrary ranges/sets of specific works (e.g. Sonatas, |m piano, |n no. 2-5)

List A - (Collective Titles "black list") Automatically exclude as a work title...

List A1 - (Collective titles "white list") (see Instantiation Mapping document for explanation)

Form list

List B - (Forms) - Exclude as a work title under the following circumstances:

  1. If no |m, |n, |p or |r -- Exclude
  2. If |m but no |n, |p or |r -- Exclude in Groups 2-4 if derived from a 240. Do not exclude and flag for human review if derived from 240 (in Group 1a) or from a 700 |t (in Groups 2-4).
  3. If |m and/or [|n, |p, |r] -- Do not exclude
  4. Note: if singular form (no "s" at end of word, unless one of the exceptions noted below *) -- Do not exclude

Terms..

* This text would be taken from |m. This could be disregarded when determining collective title status, unless |n and/or |p are present (thus meaning title is not collective)

** "Sonatas, violoncello, piano" may be a specific work title if composer wrote more than one sonata but only one for violoncello and piano. If the composer wrote more than one sonata for violoncello and piano, than this is a collective title. The same is true of concertos, suites, etc. Cannot yet devise a way around this ambiguity in uniform title nomenclature.