LC-PCC PS for 1.7.1
FIRST ALTERNATIVE
LC practice/PCC practice for Alternative (1st): For capitalization of transcribed elements, catalogers are encouraged (but not required) to follow Appendix A; it is permitted to "take what you see" on the resource. For punctuation, numerals, symbols, abbreviations, etc., follow the guidelines in 1.7.3-1.7.9 and in the appendices. If supplying information in brackets or providing a romanized form, apply cataloger's judgment to follow the appropriate appendix or not.
; it is permitted to "take what you see" on the resource. For punctuation, numerals, symbols, abbreviations, etc., follow the guidelines in 1.7.3-1.7.9 and in the appendices. If supplying information in brackets or providing a romanized form, apply cataloger's judgment to follow the appropriate appendix or not.PCC practice for Alternative (1st): For rare materials, use Descriptive Cataloging of Rare Materials
as the "designated published style manual" in place of the instructions given under 1.7.3-1.7.9 for transcribing punctuation, numerals, symbols, abbreviations, etc.
as the "designated published style manual" in place of the instructions given under 1.7.3-1.7.9 for transcribing punctuation, numerals, symbols, abbreviations, etc. [2015-07]
LC-PCC PS for 1.7.1
SECOND ALTERNATIVE
LC practice for Alternative (2nd): Follow appropriate LC copy cataloging guidelines with respect to accepting and modifying data from other agencies. Generally accept data derived from digital sources (e.g., ONIX data for CIP resources); make any adjustments to the supplied information judged appropriate (e.g., to reflect more closely the data provided in a CIP galley).
PCC practice for Alternative (2nd): Generally accept data derived from digital sources (e.g., ONIX data for CIP resources); make any adjustments to the supplied information judged appropriate (e.g., to reflect more closely the data provided in a CIP galley).
Note: Catalogers using data derived from a digital source are permitted (though not required) to make the capitalization conform to Appendix A.
[2012-07]
LC-PCC PS for 1.7.5
SYMBOLS
Signs and Symbols
LC practice/PCC practice: The objective in treating signs and symbols not represented in the character set is to render or convey the intention without undue time and effort and with a minimum of interpolation, using one of the techniques described in this section. Note that a minimum of interpolation is wanted because those searching the machine catalog cannot very often be expected to "second-guess" the cataloger in this respect, i.e., users will normally formulate search queries that necessarily do not take interpolations into account. As judged appropriate, use notes to explain and use access points to provide additional access; the examples below are illustrative, not prescriptive.
1.
If the symbol is judged not to be an integral or essential part of the title, do not intervene in the transcription. Instead, omit the symbol; explain its omission in a note if it is judged worth mentioning.
EXAMPLE
On the title page the traditional female symbol appears under the letter "W" but the preface makes it clear that the symbol is not intended to form part of the title and gives the full title)
2.
Use existing characters when this can be done without serious distortion or loss of intelligibility.
3.
Use the double underscore convention (see the section on Special Letters, Diacritical Marks, and Punctuation Marks in Policy Statement 1.4
.)
.)EXAMPLE
Preferred source
| Where to stay USA from 50¢ to $9 a night |
Transcription
| 245 10 | $a Where to stay USA from 50c to $9 a night |
4.
Substitute in the language of the context the word, phrase, etc., that is the obvious spoken/written equivalent (if unknown in the language of the context, use English); bracket the interpolated equivalent. If the element in the source is not preceded or followed by a space, in general precede or follow the bracketed interpolation by a space unless a space would create an unintended result for searching.
EXAMPLE
EXAMPLE
Preferred source
Poe  and free verse |
Transcription
| 245 10 | $a Poe[try] and free verse |
Suggested note
| 500 ## | $a On title page "[try]" appears as an illustration in the form of a tree |
The interpolation is not preceded by a space because that would create two words for searching (brackets are not separators)
EXAMPLE
Preferred source
| The added mass coefficient of a cylinder oscillating in shallow water in the limit K───> 0 and K∞ |
Transcription
| 245 10 | $a The added mass coefficient of a cylinder oscillating in shallow water in the limit K --> 0 and K [infinity] |
Suggested note
| 500 ## | $a In title "[infinity]" appears as the infinity symbol. |
The arrow is input as two hyphens and an angle bracket
Exception 1: Do not transcribe symbols that indicate birth (e.g., an asterisk) or death (e.g., a dagger) even if such characters are in the character set. Do not use a mark of omission; instead, explain the omission in a note and provide a variant title with an interpolated word or phrase if it seems useful.
EXAMPLE
Preferred source
| Walter : *1926 ✠1945 an der Ostfront |
Transcription
| 245 00 | $a Walter : $b 1926 1945 an der Ostfront |
Possible variant title
| 246 30 | $a Walter : $b [geboren] 1926 [gestorben] 1945 an der Ostfront |
Suggested note
| 500 ## | $a In title, "1926" is preceded by an asterisk; "1945" is preceded by an Iron Cross |
Exception 2: Ignore symbols indicating trademark (registered or otherwise), patent, etc. These include a superscript or subscript "R" enclosed in a circle (®) (ignore although included in the character set) and the superscript or subscript letters "TM" (™). Explain their presence in a note if considered important. Ignore such symbols also when they appear with elements used in access points.
EXAMPLE
Preferred source
| The Gumby® books of letters |
Transcription
| 245 14 | $a The Gumby books of letters |
5.
If the spoken/written equivalent is not obvious, give an explanation or a description in the language of the context (if unknown in the language of the context, use English).
6.
If a title consists solely of a sign or symbol or one or more marks of punctuation, provide an equivalent in all cases, even if the particular symbol is itself in the character set.
EXAMPLE
but
Preferred source
| ????? Steele’s answers, by Daniel Steele ... |
Transcription
| 245 10 | $a ????? Steele’s answers / $c by Daniel Steele ... |
Although the title begins with marks of punctuation, it also contains indexable data and no special intervention is required
[2017-03]
LC-PCC PS for 1.7.5
ALTERNATIVE
See Policy Statement for 1.7.5 for additional guidance on omitting some symbols even though they are reproducible.
for additional guidance on omitting some symbols even though they are reproducible.[2016-03]
LC-PCC PS for 1.8.1
OPTION
LC practice/PCC practice for Optional addition: For rare materials, apply the optional addition in the following elements when applicable: date of production, date of publication, date of distribution, date of manufacture.
[2017-03]
LC-PCC PS for 1.8.2
FIRST ALTERNATIVE
LC practice/PCC practice for Alternative (1st): Apply the alternative, except when recording numerals found in these non-Latin scripts:
Chinese, Japanese, Korean, Perso-Arabic, Cyrillic, Greek: substitute Western-style arabic numerals when non-Latin script numerals appear on the resource. If important for identification, the cataloger may record a note showing the non-Latin script form of the numeral found on the resource.
EXAMPLE
Preferred source for date of publication
| 二〇一二 |
Record in both non-Latin and romanized field
| 2012 |
Preferred source for date of publication
| 二千十二 |
Record in both non-Latin and romanized field
| 2012 |
Preferred source for date of publication
| 民國一百 |
Record in non-Latin field
| 民國 100 [2011] |
Record in romanized field
| Minguo 100 [2011] |
Note: shows application of 2.8.6.3, Optional addition in non-Latin and romanized fields
Preferred source for numbering within series
| 第四期 |
Record in non-Latin field
| 第4期 |
Record in romanized field
| Di 4 qi |
Hebrew script: record dates using the Hebrew script as found on the resource.
EXAMPLE
Preferred source for date of publication
| תשע״א |
Record in non-Latin field
| תשע״א |
Record in romanized field
| 771 [2010 or 2011] |
Note: shows application of 2.8.6.3, Optional addition in romanized field
PCC practice for Alternative (1st): For rare materials, apply the alternative.
[2015-12]
LC-PCC PS for 1.8.2
SECOND ALTERNATIVE
LC practice for Alternative (2nd): Apply the alternative if the cataloger considers it important for identification.
EXAMPLE
| 264 #1 | $a Pisa : $b Fabrizio Serra Editore, $c MMXII [2012] |
PCC practice for Alternative (2nd): For rare materials, apply the alternative in the following elements when applicable: date of production, date of publication, date of distribution, date of manufacture (see the Policy Statement for 1.8.1, Option). For other materials, apply the alternative if the cataloger considers it important for identification.
). For other materials, apply the alternative if the cataloger considers it important for identification. [2017-07]
LC-PCC PS for 1.10
NOTES
LC practice/PCC practice: For additional guidelines on punctuation in notes, see Policy Statement 1.7.1.
.[2013-12]
LC-PCC PS for 1.10.2
FIRST ALTERNATIVE
LC practice/PCC practice for Alternative (1st): Do not apply the alternative.
[2012-07]
LC-PCC PS for 1.10.2
SECOND ALTERNATIVE
LC Practice/PCC practice for Alternative (2nd): Generally accept data derived from digital sources (e.g., ONIX data for CIP resources); make any adjustments to the supplied information judged appropriate (e.g., to reflect more closely the data provided in a CIP galley).
Note: Catalogers using data derived from a digital source are permitted (though not required) to make the capitalization conform to Appendix A.
[2012-09]
LC-PCC PS for 1.11
FACSIMILES AND REPRODUCTIONS
Microform Reproductions of Print Resources
LC practice/PCC practice: The PCC follows an interim approach to cataloging microform reproductions of print resources in the RDA environment. The general principle is to record descriptive elements for the print version, and give details of the microform reproductions, both those cloned from print version records and records created originally (i.e., no print record exists, or the cataloger chooses not to clone from the print record).
Cloning from existing records for the original print resource: If the existing record is a PCC record, and is not coded as RDA (i.e., lacks "rda" in 040 subfield $e), it is permissible to retain the basic manifestation elements and cataloging rules code in the new record and still code the new record as PCC; that is, the cataloger is not required to re-describe as RDA. However, if the existing record is a non-PCC record and is not coded as RDA, the new record for the microform reproduction must be completely re-described as RDA if it is going to be coded as PCC. Note that, over time, records that are not coded as "rda" in the MARC 040 field may contain data typically found in RDA records, such as spelled out forms of words that were formerly abbreviated pre-RDA, due to automated database enrichment activities. Nevertheless, the record for the reproduction should not be coded as "rda" in MARC field 040 field unless the entire record is being re-described as RDA.
MARC coding:
Leader/18: Record the value "i". Exception: When cloning from an existing pre-RDA PCC record for the original print resource, and not re-describing as RDA, retain the value used in the record for the original resource.
008/06: Do not record the type of date as "r".
008/07-10 and 008/11-14: Record the dates associated with the original print resource.
008/15-17: Record the place of publication, etc., associated with the original print resource.
008/23: Record the value associated with the microform being cataloged (a, b, or c).
040: Record the code "rda" in subfield $e. Exception: When cloning from an existing pre-RDA PCC record for the original print resource, and not re-describing as RDA, do not add the "rda" code.
Manifestation elements: Provide all manifestation elements such as title, edition statement, publication statement, extent of the resource, etc., as they relate to the original print resource (if they are readily ascertainable); when cloning from a PCC record for the original print resource, these elements may remain as they are. Record elements that relate specifically to the microform reproduction as noted in the MARC 533 field section below. Information recorded in the 533 field may call for the addition of access points that relate only to the microform reproduction.
"Description based on" note: When cloning from a PCC record for the original print version and retaining the basic description, record "Description based on print version record." in MARC field 588.
Content, media, and carrier information: Regardless of whether the record for the reproduction is being coded as RDA, include the content type, media type, and carrier type (MARC fields 336, 337, and 338). Do not use the general material designation (MARC 245 subfield $h). The term in the media type (MARC field 337) should be "microform", and the term used in the carrier type (MARC field 338) should reflect the specific microform carrier type (e.g., "microfilm reel" or "microfiche").
Reproduction note: In the MARC 533 field, give the following bibliographic data relating to the reproduction:
Format of the reproduction
Dates of publication and/or sequential designation of issues reproduced (for serials)
Place and name of the agency responsible for the reproduction. Follow RDA instructions for recording the place and name of the reproducing agency. For example, if the place associated with the reproducing agency is unknown, use [Place of publication not identified]; if the name of the reproducing agency is unknown, use [publisher not identified].
Date of the reproduction
Extent of the reproduction
Series statement of the reproduction (if applicable)
Notes relating to the reproduction (if applicable).
EXAMPLE
| 533 ## | $a Microfilm. $b Washington, D.C. : $c United States Historical Documents Institute, $d [1972] $e 12 reels ; 35 mm. |
Related manifestation: Optionally, record the relationship of the reproduction to the print original using MARC field 776. Use either a relationship designator in subfield $i, such as: "Reproduction of (manifestation):" or, especially for serials, use other relationship information, such as the unstructured: "Print version:".
Comprehensive records: If the cataloger has a resource consisting of multiple monographs or serials on the same reel(s)/fiche, they may catalog the comprehensive resource by creating a new RDA record. Within the reel(s)/fiche, individual analytics may be cataloged using the procedures outlined above.
Print on Demand (POD) Reproductions and Photocopies
PCC practice: Use the following "provider-neutral" approach when cataloging Print on Demand (POD) reproductions and photocopies of textual materials, scores, and cartographic materials. This approach will result in a single PCC record that represents multiple POD reproductions and photocopies of the same original resource. Do not apply this technique to regular print publications, republications, reprints, facsimile reproductions, etc., or to microform reproductions. Use this technique only when the entire content of both the original resource and the reproduction is identical. Do not use it for a POD reproduction or photocopy of a book chapter or journal article. In case of doubt, do not apply this policy.
Definition: For the purposes of this policy, POD reproductions are print reproductions that are not printed until an order is received, are printed using digital techniques, and for which the source is a digital document such as a PDF file. Photocopies are print reproductions that are typically printed using xerographic techniques and for which the source is a physical document. A POD reproduction or photocopy may be made in-house or it may be ordered from a POD or photocopy service provider. Bear in mind that the source of a POD reproduction or photocopy may itself be a reproduction.
Cloning from existing records for the original print resource: If the existing record is a PCC record, and is not coded as RDA (i.e., lacks "rda" in 040 subfield $e), it is permissible to retain the basic manifestation elements and cataloging rules code in the new record and still code the new record as PCC; that is, the cataloger is not required to re-describe as RDA. However, if the existing record is a non-PCC record and is not coded as RDA, the new record for the POD reproduction or photocopy must be completely re-described as RDA if it is going to be coded as PCC. Note that, over time, records that are not coded as "rda" in the MARC 040 field may contain data typically found in RDA records, such as spelled out forms of words that were formerly abbreviated in pre-RDA, due to automated database enrichment activities. Nevertheless, the record for the reproduction should not be coded as "rda" in MARC field 040 field unless the entire record is being re-described as RDA.
MARC coding:
Use one record for all POD reproductions and photocopies of the same original manifestation. (For example, use the same record for a photocopy of book A and for a POD reproduction made from the HathiTrust digitized copy of book A.) Use this record for all such print reproductions, no matter their dates of reproduction.
Leader/18: Record the value "i". Exception: When cloning from an existing pre-RDA PCC record for the original print resource, and not re-describing as RDA, retain the value used in the record for the original resource.
008/06: Do not record the type of date as "r".
008/07-10 and 008/11-14: Record the dates associated with the original resource.
008/15-17: Record the place of publication, etc., associated with the original resource.
008/23 (Form of item) or 008/29 (Form of item): Record the value "r" indicating the form of item is a print reproduction.
040: Record the provider neutral code "pn" in subfield $e.
040: Record the code "rda" in subfield $e. Exception: When cloning from an existing pre-RDA PCC record for the original print resource, and not re-describing as RDA, do not add the "rda" code.
Manifestation elements: Provide all manifestation elements such as title, edition statement, publication statement, extent of the resource, etc., as they relate to the original print resource (if they are readily ascertainable); when cloning from a PCC record for the original print resource, these elements may remain as they are. If they are not readily ascertainable, use the information available.
020: If the reproduction is made by a commercial POD service provider that assigns ISBNs to its reproductions, record each ISBN in its own subfield $a. (If the original resource ISBN is available, also include it but record it in a subfield $z). Include any qualifying information in subfield $q. Use multiple 020 fields as needed.
037: Record a commercial POD service provider as a source of acquisition if desired. Use multiple 037 fields as needed.
33X: Regardless of cataloging rules, record the RDA content type, media type, and carrier type (MARC fields 336, 337, and 338) that are applicable to the reproduction.
533: Create a single MARC 533 field carrying only this content: 533 ## $a Print reproduction.
"Description based on" note: When cloning from a PCC record for the original print version and retaining the basic description, record "Description based on print version record." in MARC field 588.
Related manifestation: Optionally, record the relationship of the reproduction to the original using MARC field 775 (if both resources have the same physical format) or MARC field 776 (if both resources do not have the same physical format, e.g., a printout from a PDF). Use a relationship designator in the subfield $i, such as: "Reproduction of (manifestation):" or use other relationship information, such as the unstructured: "Print version:".
Local record: If the cataloger wishes to make specific extensions to the record, this should be done locally after the shared PCC record (e.g., master record in the utility) has been produced. Only then should information such as the place, name, and date pertaining to the locally-held reproduction be added (if desired) for their local catalog. It is important to stress that there should be one PCC record in the utility for all POD reproductions/photocopies of a given source document, regardless of who manufactured the POD reproduction/photocopy or the date upon which it was produced.
Basing the Description on the Reproduction (non-PCC practice)
Institutions that wish to base the description on the photocopy, microform reproduction, or POD reproduction itself (rather than the original), may do so, but such records should not be coded "pcc" in the MARC 042 field. In such records, details pertaining to the original resource would be given in the MARC field 534.
[2017-03]