UCLA Film & Television Archive Cataloging Procedure Manual--Voyager
| TYPE OF RECORD | FIELD | PROBLEM(S) |
|---|---|---|
| Bibliographic--Films and videorecordings | 008/6 (Type of date) |
Many code q's in this byte are erroneously coded, together with their date 1's (008/7-10) and 2's (008/11-14)
|
| Bibliographic--Films and videorecordings | 008/15-17 (Place of publication) |
When country of origin was not known, we erroneously input three blanks instead of the correct xx_ (meaning in MARC21: completely unknown) |
| Bibliographic--Films and videorecordings | 008/18-20 (Running time) |
Data completely lost in ORION1 to TAOS data migration and probably impossible to restore; restore to records as encountered |
| Bibliographic--Films and videorecordings | 008/34 (Technique code) |
Lost in ORION1 to TAOS migration. Changed to l or a in TAOS based on presence of genre headings for animation or cartoons in the bib. record; code c for animation and live action may need to be restored as encountered; consider finding all records with the phrase 'live action' in the notes and 008/34 code of 'a,' and change code 'a' to code 'c'? Under cataloger's review? |
| Bibliographic--Films and videorecordings | 008/35-37 (Language) |
When language was not known, we erroneously input three blanks (meaning in MARC21: no sung, spoken or written textual content) instead of und (cannot be determined); change all to und? |
| Bibliographic | 041 (Language) |
In 2001, the MARC 21 format practice of placing multiple language codes in one subfield (e.g. $aengfreger) was made obsolete (e.g. $a eng $a fre $a ger); update all older records to add subfield codes between language codes In 2007, the MARC 21 format changed the meaning of subfield b (which used to mean subtitles) to language code of summary or abstract; now subfield j means language code of subtitles or captions; change all subfield b to subfield j |
| Bibliographic | 245 |
Square brackets ([]) mistakenly input as curly brackets ({}) in ORION1 migrated to TAOS as 'y' with an umlaut. Consider converting all of these back to square brackets? May have been fixed in migration from TAOS to Voyager--verify |
| Bibliographic | 245 |
When 1XX? 130? present, change first indicator to 0? Or report to catalogers for review? |
| Bibliographic | 245 |
|
| Bibliographic | 257 $a and 260 $a |
Change all 'U.K.' to 'Great Britain.' |
| Bibliographic | 440 |
As of October 24, 2008, the 440 field has been made obsolete; all 440 tags should be changed to 490, first indicator 1, AND 830 second indicator 0 (with any initial articles dropped, as signalled by a filing indicator in the now obsolete 440) |
| Bibliographic | 500 |
In the 590 to 500 conversion, moving of 511 below 508 and moving down of 501 in TAOS to Voyager conversion, some note ordering was lost; restore as encountered |
| Bibliographic | 520 |
When first indicator 8 is present, change tag and indicators to 518 _ _. |
| Bibliographic | 6XX genre/form headings |
Consider doing a global update to change the following music and dance headings from 650 fields to 655, second indicator 0, except when followed by $vDrama or $xHistory and criticism or $xPublic opinion or $xWriting and publishing:
|
| Bibliographic | 700, 710 |
Would it be possible to identify all local name authority headings in our file and add $5 CLU-FT to the 700 and 710 fields for those headings in the bibliographic records? |
| Holdings | 008/07 |
When donor/depositor code in 905 $c subfield is 0992 (taped off the air), change 008/07 to code 'g' and add an 866 $x subfield with the text 'Taped off the air.' |
| Holdings | 008/12 |
In ORION1 to TAOS migration, all should have been coded 8 for permanently retained, but for some reason some holdings records were missed and have blanks instead; change all blanks to 8. |
| Holdings | 008/16 |
Some completeness codes for films fixed in migration from TAOS to Voyager, based on 007/16 codes, but some not; video completeness codes not fixed because lack 007/16 codes. Consider global update based on first number in 866 $a (2 or higher); if 866 $a begins with 1 and 007/16 is code c, change 008/16 to code 4; if 866 $a begins with a number higher than 1 and 007/16 is code c, change 008/16 to code 1. Also change all films with 007/16 code i to a) 008/16 code 2, b) leader 6, code v, and c) leader 17 code 3. Also change all holdings with leader 6 code v and 008/16 code 4 to 008/16 code 1. |
| Holdings | 008/20 |
In ORION1 to TAOS migration, all should have been coded b for will not lend, but for some reason some holdings records were missed and have blanks instead; change all blanks to b. |
| Holdings | 008/21 |
In ORION1 to TAOS migration, all should have been coded b for will not reproduce, but for some reason some holdings records were missed and have blanks instead; change all blanks to b. |
| Holdings | 843 |
Remove 'REPRODUCTION:' from in front of $n notes automatically created in TAOS to Voyager migration |
| Holdings | 843 |
Underline character in ORION1 did not migrate accurately to either TAOS or Voyager and causes display problems. It is common in holdings record reproduction notes where we used it to signal incomplete information. Fix as encountered by changing it to a question mark or using terminology such as 'unknown element.' |
| Holdings | 852 $h |
When the ORION1 record contained only an X# with a MY number, the MY number was migrated both to the 852 $j=852 $h in Voyager, and to the 866 $z. The 866 $z is not needed when the MY number is being used for location, as in the case of ARSC and Commercial Services materials, and should be deleted as encountered. Consider doing a global update to remove these? Under cataloger review? Do not delete other MY numbers that are duplicated in this way; for example, the presence of the MY number in the 866 $z LOCATION: note for an item in the Preservation Vault may indicate that the item is located using the MY number despite the fact that many MY numbered items in the Preservation Vault are located using other numbers such as old location numbers. |
| Holdings | 866 and 903 |
|
| Holdings | 866 and 916 |
Find all holdings records with a barcode in 866 $z LOCATION: and in 916 and move the barcode to an item record, deleting the 866 LOCATION: note and the 916 field (unless there is more in the 916 besides the barcode)? |
| Holdings | 903 |
Change all second indicator 0 to blank. |
| Authority | 010 |
The Library of Congress control numbers for names have the letter(s) and numbers run together (e.g. n78095332), while the Library of Congress control numbers for subjects have the letters and numbers separated by a space (e.g. sh 96001637). The DRA loader will close up spaces on incoming records. The presence/absence of the space will affect indexing of the 010 in the LCAX index and will affect duplicate detection. Before instituting automatic downloading of authority records, global update should be done to close up spaces in the subject heading control numbers. |
| Authority | X50 |
2nd indicator is undefined in MARC 21, but was set as 0 (meaning LCSH) or 9 (meaning local) in ORION1, and migrated that way. Second indicator 0's have all been removed and so have many second indicator 9's (on fictititious character headings), but second indicator 9's on locally made cross references remain. Consider global update to change all 2nd indicators to blank. In the mean time, as encountered, change second indicator 9's on 150's to blanks and add the phrase 'LOCAL HEADING' in a 667 field; change second indicator 9's on 450's and 550's to blanks, and add a "cross reference(s) locally added" note to the 667 field. |
| Authority | 555 |
See and see also references on local subject authority records were mistakenly changed to 455 and 555 on data migration. May have been fixed in TAOS to Voyager migration; verify. |
| Authority | 680 |
360 and subfield i in 680 would not display properly in ORION1 or TAOS, so were input as 680 subfield a; needs human editing, perhaps based on a report of authority records with 680 fields with no subfield i's in them. |
Last modified: February 25, 2010, my