Procedure for Cataloging Translations
Department: Technical Services
Procedure: Cataloging Translation
updated 7 June 2016
Purpose: This procedure documents the unique MARC fields to be used when cataloging translations.
Overview: For a definition of “translation” for the purposes of cataloging, see the Classification and Shelflisting Manual, section G150 (hereafter referenced as the Shelflisting Manual). The phrase “translated by” may appear on the title page of a translation and thus appear in the 245 subfield c, but not always. Translations cataloged by the Library of Congress will almost always have the fields indicated below. However, if they do not, add them as per guidelines below. (Exception: DLC records needing a uniform title or an entry for the translator should be referred to a librarian.) Since we strive to follow LC, we should also use the unique translation fields when working with member-input records or doing original cataloging. As of this writing, this procedure applies only to printed monographs. It will be updated later for music scores and non-print materials.
Required Knowledge/Skills: OCLC Connexion, MARC.
Equipment/Supplies: Access to OCLC.
Procedure
1. Fixed field. Lang=code for the language of most of the text, usually the language indicated in 041 subfield a. See below.
2. 041 field. Should be present. First indicator=1.
a. Subfield a=language code for the language of the text in hand (i.e. the translation).
b. Subfield h=language code for the original language (i.e. the language translated from). May be repeated if the original text was in more than one language.
c. Note: OCLC prefers the use of MARC codes as found in MARC Code List for Languages (http://www.loc.gov/marc/languages/).
d. Subfield k=language of intermediate translation.
3. 130 or 240. A uniform title field should be present but is not required. Search OCLC to see if you can find a standard heading for the original work, but do not search beyond OCLC. If you cannot determine the standard heading for the original title when working with member input records or doing original cataloging, it is better to not add a uniform title.
a. Use 130 for title main entry; use 240 for author main entry. First indicator is usually 1. Second indicator depends on the use of initial articles.
b. Subfield a=usually the title of work in the original work in the original language. Sometimes this field will have uniform title heading contrived
by LC (i.e. Works.)
c. Subfield l=language of the translation. Note: do not use a language code; spell out the name of the language.
d. Add other subfields as needed (i.e. Subfield k: Selections). Follow OCLC guidelines for the 130/240 field for the order of subfields.
4. 500 or 546 field.
a. 500 field. Often translation notes are included in a 500 field. If so, that is sufficient. However, if the text in the 500 and the 546 are
identical, delete one of them.
b. 546 Language note. The 546 field is used to describe the language of the text. The 546 field is not needed to indicate the original language
unless the text in hand has more than one language. Add a 546 field if there is text in more than one language or script.
5. 700 field for translator. May or may not be included, depending on the translator’s importance. Generally, accept what has been done by the inputting library, unless the translator is a member of the VU community.
a. If the translator is a member of the VU community, always add them in a 700 note. If there is no OCLC authority record for the translator, and if the
person’s name has not been established in our catalog, refer the name to a professional cataloger to establish the heading.
b. The use of a relator term or code (subfield e or subfield 4) is optional. Do not add either subfield to DLC copy. If you think it necessary to add a
relator term, use subfield e with the term “translator” spelled out. Do not add subfield 4.
6. Call number. *If the book comes shelf-ready and labeled, we will \[\[not\]\] edit the call number in the record or change the label to conform to translation Cuttering described below, if the Cutter is the only problem.* Otherwise use the translation Cutter table for all translations. NOTE: Since 1983, LC practice is to use the translation Cutter table only when the record has a uniform title. We will follow the pre-1983 guidelines and use the translation Cutter on all translations. See Classification and Shelflisting Manual, section G150 for for the translation Cutter table and additional details.
a. Prefer 050 second indicator 4 over 090.
b. Try to find a record for the work in the original language. If you agree that the work in the original language is classified correctly, supplement
the Cutter with additional digits, depending on the language of the translations. See the translation Cutter table and the classification
schedule.Usually you will add two digits; sometimes you will add one.
c. Exception: If you have DLC copy for an earlier edition of the same translation, use the LC number from the earlier with the new date.
d. Exceptions: Do not use the translation Cutter table:
i. For entries with a corporate or conference creator.
ii. For autobiographies or correspondence.
iii. When using the Biography Table. (See the Shelflisting Manual, section G150 for additional details.)
e. If the language is not listed in the translation Cutter table, ask the Head of Metadata Service to run a list to see if we have added other works