cat:original-cataloging-book
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
cat:original-cataloging-book [2019/05/22 14:46] – [Manufacture Date (RDA 2.10.6)] ehardy | cat:original-cataloging-book [2019/05/22 15:32] (current) – removed ehardy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== PINES Original Cataloging with RDA: Book Format ====== | ||
- | |||
- | |||
- | **<fc # | ||
- | |||
- | Training for original cataloging on OCLC is mandatory for all except those catalogers who have already had experience on OCLC. Copy catalogers wishing original cataloging training should contact the PINES Cataloging Specialist for arrange for training to be scheduled. | ||
- | |||
- | Currently there is full level cataloging training for books and AV formats. Original records, either full or K level, should be created with the OCLC Connexion Client and then imported into the PINES database. | ||
- | |||
- | <note important> | ||
- | |||
- | **Fixed fields**: All fixed fields must be coded correctly according to current practice (see [[https:// | ||
- | |||
- | **Variable fields**: The following variable fields must be present in MARC bibliographic records when information is available and/or applicable. | ||
- | |||
- | |||
- | <wrap indent> | ||
- | * _ = blank value in indicators\\ | ||
- | * ǂ = subfield delimiter\\ | ||
- | * Subfield a (ǂa) in the first position of a MARC tag is implied in OCLC system, so is omitted. | ||
- | |||
- | **Resources: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | ===== Guidelines for Transcription (RDA 1.7) ===== | ||
- | |||
- | |||
- | **Transcribe vs Record: general information** | ||
- | |||
- | **Transcribed elements** match exactly what is on resource, except when specific instructions say otherwise (those for capitalization and punctuation, | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | **Recorded elements** is data about a resource that is not exactly as it appears on the source, or, is taken from another source. | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Capitalization (RDA 1.7.2) ==== | ||
- | |||
- | For the sake of consistency, | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | **Record as:** 245 10 Babar the King / ǂc Jean de Brunhoff ; translated into English by Scott Fontenot & Denise St. Pierre. </ | ||
- | |||
- | ==== Punctuation (RDA 1.7.3) ==== | ||
- | |||
- | **Add punctuation if necessary for clarity.** | ||
- | |||
- | **On resource title page**:\\ | ||
- | |||
- | Aristotle Onassis\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Record as**: | ||
- | <wrap indent> | ||
- | |||
- | **Transcribe punctuation as it appears on the source.** | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent>I don’t do dishes!</ | ||
- | |||
- | |||
- | **Make a note to indicate that punctuation has been omitted or modified, if considered important for identification.** | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | ==== Diacritics (RDA 1.7.4) ==== | ||
- | |||
- | Transcribe diacritical marks or add them, if needed, even if absent from the resource.\\ | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | === How to add diacritics in Connexion: === | ||
- | |||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | |||
- | ==== Symbols (RDA 1.7.5) ==== | ||
- | |||
- | Replace symbols and other characters that cannot be reproduced by the facilities available, and add a note with a description of the symbol. | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | Spacing (RDA 1.7.6) | ||
- | |||
- | **Transcribe acronyms and initials without spaces.** | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | <WRAP INDENT CENTERALIGN> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Abbreviations (RDA 1.7.8 and Appendix B) ==== | ||
- | |||
- | |||
- | Generally, RDA standards and guidelines are to avoid using abbreviations. The primary exceptions are for: | ||
- | |||
- | * Units of measurement | ||
- | * Abbreviations that are regularly used in resources and are commonly understood by users | ||
- | * Abbreviations that a resource uses to identify | ||
- | |||
- | Mostly, abbreviations are used only when they appear on the resource, although there are some exceptions in addition to those noted above. See RDA Appendix B for guidance. | ||
- | |||
- | < | ||
- | |||
- | Examples: | ||
- | {{tablelayout? | ||
- | ^ AACR2 ^ RDA ^ | ||
- | | p. | pages | | ||
- | | ca. | approximately | ||
- | | i.e. | that is | | ||
- | | acc. | accompanied | ||
- | | ill. | illustrations | ||
- | | col. | color | | ||
- | | facsim. | ||
- | | ed. | edition | ||
- | | S.l. | [place of publication not identified] | ||
- | | s.n. | [publisher not identified] | ||
- | | n.d. | [date of publication not identified] | ||
- | | 3 vol. | 3 volumes | ||
- | | ca. 200 p. | approximately 200 pages | | ||
- | | 48 [i.e. 96] p. | 48, that is, 96 pages | | ||
- | | [16] p. of plates | ||
- | |||
- | ==== Inaccuracies (RDA 1.7.9; 2.3.6) ==== | ||
- | |||
- | |||
- | Transcribe an inaccuracy or a misspelled word as it appears on the resource unless the instructions for a specific element differ. Make a note to explain, if necessary. Correct the inaccuracy note if it is important for identification or access. Add a variant title to record the correct form of the inaccuracies in a title to ensure identification and access. | ||
- | |||
- | |||
- | **On title page**: Oak Hill Methodist Church Cemetary\\ | ||
- | **Transcribe as**:\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | or | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | < | ||
- | </ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | ===== Source of Information guidelines (RDA 2.2.2) ===== | ||
- | |||
- | |||
- | **Preferred source of information: | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Other source of information: | ||
- | |||
- | Accompanying materials, etc. or any other available source. | ||
- | |||
- | If information outside of the resource is used in certain elements, indicate this by placing the information in brackets. These elements include: | ||
- | * title proper | ||
- | * parallel title proper | ||
- | * other title information | ||
- | * all the subelements under statements of responsibility: | ||
- | * edition statement | ||
- | * production statement | ||
- | * publication statement | ||
- | * distribution statement | ||
- | * manufacture statement | ||
- | * series statement | ||
- | |||
- | < | ||
- | |||
- | Putting data from sources outside your resource in brackets is enough. Notes on where you get the information are unnecessary. | ||
- | |||
- | |||
- | ===== Fixed Fields ===== | ||
- | |||
- | |||
- | In OCLC and Evergreen, the fixed field is a combination of the MARC Leader and the 008 field. They are identified by their positions within the Leader and 008 (Type=Leader/ | ||
- | |||
- | Of special note for original cataloging of books are: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | <wrap indent> | ||
- | * I (Full-level input by OCLC member library) | ||
- | <wrap indent> | ||
- | * K (Minimal-level input by OCLC participants member library) | ||
- | <wrap indent> | ||
- | * Be careful when coding Cont: (Contents). With the exception of “b” for bibliographical references (bibliographies), | ||
- | * For graphic novels, use “6”. | ||
- | * Code all blank ∎ areas, if required/ | ||
- | <wrap indent> | ||
- | |||
- | ===== 007 field ===== | ||
- | |||
- | |||
- | The 007, the physical description fixed field, is a variable control field used to define elements of the resource not included in the Leader/008. While OCLC uses subfields for elements in the 007, MARC 21 defines the elements by position. Codes differ dependent on the format of the resource. Traditionally used for non-print formats, more recently coding has been added to the 007 field for print resources. | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ===== Resource Identifiers (0xx fields) (RDA 2.15) ===== | ||
- | |||
- | |||
- | Identifiers for a manifestation | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | < | ||
- | |||
- | |||
- | ===== Other 0xx Fields ===== | ||
- | |||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | * 043 is added when a record has a geographic subject access point or has a geographic element in an access point: | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | < | ||
- | |||
- | |||
- | <wrap indent> | ||
- | * DDC call number. Apply one in a full-level record. Use [[http:// | ||
- | |||
- | ===== Access Points for Creators, 1xx fields (RDA 6.27.1.2) ===== | ||
- | |||
- | |||
- | Works created by persons, families, or corporate bodies | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | ==== Access Points for Personal Names (RDA 9.2) ==== | ||
- | |||
- | |||
- | <fc # | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | If a resource has a creator, make sure you search the OCLC authority file to see if a matching name authority record (NAR) for the creator exists. If there is, use it. If not, transcribe the creator’s name in 100 field as a place holder, and then send The PINES Cataloging Specialist all information about the creator from the resource, creator’s Webpages and other reliable online resources, and/or from a local creators themselves. | ||
- | |||
- | **Choice of a preferred name:** If varied forms of the name exist, one with or without middle initials, or fuller form of middle or first names, for example, the preferred name should be one following the book’s title either on title page or cover if there is no title page. | ||
- | |||
- | <wrap indent> | ||
- | |||
- | * The DOB is the most desirable information if available | ||
- | * Birthplace, places of residence | ||
- | * Occupation | ||
- | |||
- | |||
- | ==== Access Points for Corporate Bodies (RDA 8.1.2, 19.2.1.1.1) ==== | ||
- | |||
- | |||
- | **Corporate bodies as creators** | ||
- | |||
- | A corporate body can be a creator, if the content of its work falls into the following categories (outlined below are some key points; for more detail, check the RDA rule). | ||
- | * Works of an administrative nature. | ||
- | * Works that record the collective thought of the body (reports of commissions, | ||
- | * Works that record hearings conducted by legislative, | ||
- | * Works that report the collective activity of conference, expedition, an event, exhibition). | ||
- | * Works that result from the collective activity of a performing group. | ||
- | * Cartographic works. | ||
- | * Legal works. | ||
- | * Named individual works of art by two or more artists acting as a corporate body. | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | Examples: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Access Points for Family Names (RDA 8.1.2; 10.10.1.1) ==== | ||
- | |||
- | |||
- | **<fc # | ||
- | |||
- | When constructing an authorized access point to represent a family, use the preferred name for the family (RDA 10.2.2). | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | If no NAR exists in OCLC for the family name, create a placeholder 100 _3 in the record in the form:\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | For creation of a NAR, send the PINES Cataloging Specialist as much of the following family information as possible: | ||
- | |||
- | * Surname of the family. | ||
- | * Date associated with the family. | ||
- | * Place(s) associated with the family. | ||
- | * Prominent member(s) of the family. | ||
- | |||
- | ==== Relationship Designators ==== | ||
- | |||
- | |||
- | Relationship designators identify the relationship between a resource and associated agents. They provide specific information about the character of the relationship and as many can be used as needed to fully describe that relationship. They are optional, but strongly encouraged. PINES local policies recommend their addition. | ||
- | |||
- | Examples: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Common relationship designators for books format:** | ||
- | |||
- | <wrap indent>, | ||
- | <wrap indent>, ǂe illustrator. </ | ||
- | <wrap indent>, ǂe editor. </ | ||
- | <wrap indent>, ǂe compiler. </ | ||
- | <wrap indent>, ǂe translator. </ | ||
- | <wrap indent>, ǂe photographer. </ | ||
- | |||
- | See [[http:// | ||
- | For more information, | ||
- | |||
- | |||
- | ==== Access Points for Compilation - one agent (RDA 6.2.2.10.3) ==== | ||
- | |||
- | |||
- | **Collection of works by the same agent** | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | < | ||
- | |||
- | ==== Access Points for Collaboration (RDA 6.27.1.3, 19.2.1.1) ==== | ||
- | |||
- | |||
- | **Collaborative work with multiple agents** | ||
- | |||
- | RDA 6.27.1.3: If one principal name (person, corporate body, family) responsible for the work is indicated, make an access point for this named person/ | ||
- | |||
- | Creating access points for other creators/ | ||
- | |||
- | <wrap indent> | ||
- | <WRAP INDENT JUSTIFY> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Compilation with multiple agents (RDA 6.27.1.4) ==== | ||
- | |||
- | |||
- | **Work or works by multiple agents with a collective title** | ||
- | |||
- | For a compilation of works by multiple agents with a collective title, record the collective title in the 245 and omit a 1xx field. | ||
- | |||
- | Example : | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | The authorized access point is the preferred title and analytical authorized access points can be provided for each agent: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | **Work or works by multiple agents without a collective title** | ||
- | |||
- | Example: | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | Feramontiv / Desmond Cory. The graveyard shift / Harry Patterson.</ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | As an alternative, | ||
- | |||
- | Make a note to indicate the source of a title proper (RDA 2.17.2.3). | ||
- | |||
- | ==== Access points for adapters, etc. (RDA 6.27.1.5) ==== | ||
- | |||
- | |||
- | **Adaptations and revisions** | ||
- | |||
- | You may have to make a judgment call to determine if: </ | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | |||
- | ===== Preferred Title: 240 field (RDA 6.2.2, 6.11) ===== | ||
- | |||
- | <fc # | ||
- | |||
- | **Preferred title for Expression** | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | ===== Title (RDA 2.3) ===== | ||
- | |||
- | |||
- | <fc # | ||
- | |||
- | “A word, character, or group of words and/or characters that names a resource or a work contained in it” (RDA 2.3.1.1). | ||
- | |||
- | More than one title can be associated with the resource. Multiple titles can be found in: | ||
- | * Sources of information (title page, title frame; caption title, running title; cover, spine; title bar) | ||
- | * On a jacket, sleeve, container, etc. | ||
- | * In material accompanying it. | ||
- | * Through reference sources | ||
- | * Through assignment by a registration agency (for example, key title) | ||
- | * By an agency preparing a description of it (For example, a translation by the cataloger). | ||
- | |||
- | |||
- | ==== 245 Title field: 1st indicator (Title added entry: MARC coding) ==== | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | ==== 245 Title field: 2nd Indicator (Nonfiling characters: MARC coding) ==== | ||
- | |||
- | Indicator is coded with 0-9 for the number of nonfiling characters to be skipped in indexing or filing. | ||
- | |||
- | **0** is used when the title does not begin with an article an means no characters are skipped. | ||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | **1-9** is used when a Title begins with a definite or indefinite article that is skipped in sorting and filing. | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== 245 ǂa Title proper (RDA 1.3, 2.3.2, 2.3.4, 2.4.2) ==== | ||
- | |||
- | <fc # | ||
- | |||
- | A principal name of a manifestation, | ||
- | |||
- | **Examples: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | === Omission of Introductory Words, etc. (2.3.1.6) === | ||
- | |||
- | Do not transcribe words that serve as an introduction and are not intended to be part of the title. | ||
- | |||
- | Example:\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | === Preferred source of information (RDA 2.3.2.2) === | ||
- | |||
- | * The title proper should be taken from the preferred source of information as specified in RDA 2.2.2 and 2.2.3. | ||
- | * If the manifestation does not include a title proper, take it from a source specified in RDA 2.2.4. | ||
- | * If required (see RDA 2.17.2.3), make a note defining the source. | ||
- | |||
- | === Other elements recorded as part of the title proper: Titles of Parts, Sections, and Supplements (RDA 2.3.1.7) === | ||
- | |||
- | “If the title of the part, section, or supplement has a numeric and/or alphabetic designation, | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | === Supplied or devised title (RDA 2.2.4, 2.3.2.10, 2.34) === | ||
- | |||
- | |||
- | As a <fc # | ||
- | |||
- | Examples: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Other Title Information: | ||
- | |||
- | <fc # | ||
- | |||
- | “A word, character, or group of words and/or characters that appears in conjunction with, and is subordinate to, the title proper of a resource”. (RDA 2.3.4) | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | Examples: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | < | ||
- | |||
- | ==== Parallel Title Proper : 245 field, ǂb (RDA 2.3.3) ==== | ||
- | |||
- | |||
- | <fc # | ||
- | |||
- | A parallel title proper is a title proper in another language and/or script. | ||
- | |||
- | If a parallel title proper is taken from a different source than the title proper, and that fact is considered important for identification, | ||
- | |||
- | Example: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Variant Titles: 246 fields (RDA 2.3.6) ==== | ||
- | |||
- | |||
- | “A title associated with a resource that differs from a title recorded as a title proper, a parallel title proper, an other title information, | ||
- | |||
- | **Examples: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | If any sign/ | ||
- | |||
- | **Examples: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | Variant titles are not core elements, so tracing of them is optional; add as needed: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | < | ||
- | |||
- | <wrap indent> | ||
- | 500 At head of title: ….</ | ||
- | |||
- | <wrap indent> | ||
- | |||
- | |||
- | ==== Statement of Responsibility : 245 field, ǂc (RDA 2.4) ==== | ||
- | |||
- | <fc # | ||
- | |||
- | “A statement relating to the identification and/or function of any agents responsible for the creation of, or contributing to the realization of, the intellectual or artistic content of a resource.” RDA 2.4 | ||
- | |||
- | **Examples: | ||
- | |||
- | **On resource**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | **Record as**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | **On resource**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Record as**: | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | |||
- | |||
- | **On resource**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Record as**:\\ | ||
- | |||
- | <wrap indent> | ||
- | |||
- | === Statement naming more than one agent: 245 field, ǂc (RDA 2.4.1.5) === | ||
- | |||
- | |||
- | “Record a statement of responsibility naming more than one agent as a single statement whether those agents perform the same function or different functions”. -- RDA 2.4.1.5 | ||
- | |||
- | “If a single statement of responsibility names more than three agents performing the same function (or with the same degree of responsibility), | ||
- | |||
- | |||
- | **On resource**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Options for transcription**: | ||
- | |||
- | * ǂc by Nicholas Fraser, Frank Smith, Simon Lemon, Esther Ryde ; edited by Joe Jackson. | ||
- | * ǂc by Nicholas Fraser [and three others] ; edited by Joe Jackson. | ||
- | * ǂc by Nicholas Fraser, Frank Smith [and two others] … | ||
- | |||
- | |||
- | === Clarification of role 245 field, ǂc ( RDA 2.4.1.7) === | ||
- | |||
- | If the role of an agent is not clear, add a short phrase for clarification. | ||
- | |||
- | **On resource**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Record as**: | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | < | ||
- | |||
- | ==== Edition Statement: 250 field (RDA 2.5.1.4) ==== | ||
- | |||
- | <fc # | ||
- | |||
- | Transcribe any edition statement as it appears on the source. | ||
- | |||
- | **On resource**: | ||
- | <wrap indent> | ||
- | **Record as**: | ||
- | <wrap indent> | ||
- | |||
- | **On resource**: | ||
- | <wrap indent> | ||
- | |||
- | **Record as**: | ||
- | <wrap indent> | ||
- | |||
- | **Optional addition**: | ||
- | |||
- | “If a manifestation lacks an edition statement but is known to contain significant changes from other editions, supply an edition statement, if considered important for identification or access. Indicate that the information was taken from a source outside the manifestation itself” RDA 2.5.1.4. | ||
- | |||
- | **Example**: | ||
- | <wrap indent> | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | < | ||
- | |||
- | ==== Publication Statement (RDA 2.8) ==== | ||
- | |||
- | <fc # | ||
- | |||
- | “A statement identifying the place or places of publication, | ||
- | Publication statements include statements relating to the publication, | ||
- | Consider all online resources to be published. | ||
- | For early printed resources, distribution and manufacture statements relating to booksellers and printers may be treated as publication statements” RDA 2.8.1.1. | ||
- | |||
- | For statements relating to the production of manifestations in an unpublished form, see RDA 2.7. | ||
- | |||
- | === Place of Publication: | ||
- | |||
- | |||
- | <fc # | ||
- | |||
- | “Include both the local place name (city, town, etc.) and the name of the larger jurisdiction or jurisdictions (state, province, etc., and/or country) if present on the source of information” – RDA 2.8.2.3. | ||
- | |||
- | **On resource**: | ||
- | <wrap indent> | ||
- | |||
- | **Record as**: | ||
- | <wrap indent> | ||
- | |||
- | If more than one place of publication appears on the source of information, | ||
- | |||
- | **Example**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | **Optional addition**: | ||
- | |||
- | <WRAP INDENT JUSTIFY> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | == Place of Publication not identified: 264 field, ǂa (RDA 2.8.2.6) == | ||
- | |||
- | If a place of publication is not identified in the manifestation, | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | === Publishers : 264 field, | ||
- | |||
- | <fc # | ||
- | |||
- | “A name of an agent responsible for publishing, releasing, or issuing a resource. A publisher’s name may be represented by a characterizing word or phrase” RDA 2.8.4.1 | ||
- | |||
- | **On resource**: | ||
- | <wrap indent> | ||
- | **Record as**: | ||
- | <wrap indent> | ||
- | |||
- | **On resource**: | ||
- | <wrap indent> | ||
- | **Record as**: | ||
- | <wrap indent> | ||
- | |||
- | **More than one publisher**: | ||
- | “If more than one agent is named as a publisher of the manifestation, | ||
- | |||
- | <WRAP INDENT JUSIFY> | ||
- | |||
- | **Probable publisher**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | **No publisher identified**: | ||
- | <wrap indent> | ||
- | |||
- | RDA 2.8.4.3 includes an optional instruction to "Omit levels in a corporate hierarchy that are not required to identify the publisher." | ||
- | |||
- | PINES has decided to omit additional information not needed to identify the publisher. | ||
- | |||
- | === Producers/ | ||
- | |||
- | **Producer**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | **Distributor**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Manufacturer**: | ||
- | |||
- | **On resource**: | ||
- | <wrap indent> | ||
- | |||
- | **Record as**:\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | Or with just a 264 _3 field: \\ | ||
- | |||
- | <wrap indent> | ||
- | |||
- | |||
- | ==== Dates (RDA 2.7.6, 2.8.6, 2.9.6, 2.10.6, 2.11) ==== | ||
- | |||
- | <fc # | ||
- | |||
- | **Publication date**: “A date associated with the publication, | ||
- | |||
- | **Copyright date**: “A date associated with a claim of protection under copyright or a similar regime. Copyright dates include phonogram dates, that is, dates associated with claims of protection for audio recordings” – RDA 2.11.1.1 | ||
- | |||
- | **Production date**: “A date associated with the inscription, | ||
- | |||
- | **Distribution date**: “A date associated with the distribution of a resource in a published form” – RDA 2.9.6.1.\\ | ||
- | |||
- | **Manufacture date**: ”A date associated with the printing, duplicating, | ||
- | |||
- | Code all dates in MARC field 264, ǂc\\ | ||
- | Code OCLC fixed fields DtSt (MARC 008/06) using appropriate codes and Dates (MARC 008/07-14) | ||
- | |||
- | === Publication and Copyright Dates (RDA 2.8.6) === | ||
- | |||
- | **On resource**: | ||
- | |||
- | <wrap indent>A book of travelers’ tales</ | ||
- | <wrap indent> | ||
- | |||
- | **Code as**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Publication Date inferred from a copyright date**: (RDA 2.8.6.6, LC-PCC PS) | ||
- | |||
- | If an item has a copyright date but lacks a publication date, “[s]upply a date of publication that corresponds to the copyright date, in square brackets” -- RDA 2.8.6.6, LC-PCC PS. | ||
- | |||
- | **PINES local practice**: if a publication date is inferred from a copyright date, place the date in brackets for 264 _1 and record the copyright date in 264_4: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | < | ||
- | |||
- | OCLC Fixed Field DtSt: s Dates: 2013 | ||
- | |||
- | |||
- | **Publication Date that Differs from Copyright Date** (RDA 2.8.6.6) | ||
- | |||
- | **On resource**: | ||
- | |||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | --------------------------------- | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | |||
- | **Code as**:\\ | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | |||
- | === Publication Date Not Identified in a Single-Part Manifestation (RDA 2.8.6.6, LC-PCC PS 2.) === | ||
- | |||
- | |||
- | If the copyright date is the year following the year in which the publication is received, supply a date of publication that corresponds to the copyright date. | ||
- | |||
- | **Example**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | **Code as**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <note important> | ||
- | |||
- | |||
- | Publication Dates: Date of Related Manifestations (RDA 27.1) | ||
- | |||
- | **Title page on Resource**: | ||
- | |||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | < | ||
- | |||
- | <WRAP INDENT CENTERALIGN> | ||
- | |||
- | ---------------------------------------- | ||
- | **Verso of Title Page**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | **Code as**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | |||
- | === Multipart Monographs (RDA 2.7.6.5) === | ||
- | |||
- | |||
- | “If the first issue, part, or iteration of a multipart monograph … is available, record a date of production of that issue, part, or iteration, followed by a hyphen.” | ||
- | |||
- | **Example**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <WRAP INDENT JUSTIFY> | ||
- | <wrap indent> | ||
- | |||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | === Supplied Dates (RDA 1.9.2) === | ||
- | |||
- | |||
- | If a date does not appear or is unclear on the source of information, | ||
- | |||
- | Actual known record as: [2003]\\ | ||
- | Either one of two consecutive years record as: [1971 or 1972]\\ | ||
- | Probable year record as: [2000?]\\ | ||
- | Probable range of years record as: [between 1970 and 1979?]\\ | ||
- | Earliest possible date know record as: [not before August, 2011]\\ | ||
- | Latest possible date known record as: [not after 1865]\\ | ||
- | |||
- | **Examples of coding**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> DtSt: s Dates: 18uu</ | ||
- | |||
- | |||
- | **Example wording on resource**: | ||
- | |||
- | <wrap indent>" | ||
- | |||
- | |||
- | **Code as**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | === Fictitious or incorrect dates (RDA 2.8.6.3) === | ||
- | |||
- | “If the date as it appears in the resource is known to be fictitious or incorrect, make a note giving the actual date” – RDA 2.8.6.3. | ||
- | |||
- | **Examples**: | ||
- | |||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | Date of Publication Not Identified (RDA 2.8.6.6) | ||
- | |||
- | Follow LC-PCC PS guidelines and try to supply a probable date. If a date can be supplied, indicate if from a different source. If no date can be supplied, then record as: [date of publication not identified]. | ||
- | |||
- | 264 _1 Atlanta, Ga. : ǂb [publisher not identified], | ||
- | |||
- | === Manufacture Date (RDA 2.10.6) === | ||
- | |||
- | Date of manufacture (printing) in place of publication\\ | ||
- | |||
- | “If an item lacking a publication date contains a copyright date and a date of manufacture and the year is the same for both, supply a date of publication that corresponds to that date, in square brackets, if it seems reasonable to assume that date is a likely publication date” -- RDA 2.8.6.6 LC-PCC PS) | ||
- | |||
- | **On Resource**: | ||
- | |||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | ------------------------------------ | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | |||
- | **Code as**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | <wrap indent> | ||
- | |||
- | |||
- | **Date of publication not given** | ||
- | |||
- | **Example**: | ||
- | |||
- | <wrap indent> | ||
- | |||
- | |||
- | If it is determined the printing company on a resource also publishes, you may treat it as a publisher. | ||
- | |||
- | **Examples**: | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | 264 _ 3 : ǂb Dire Printing Sh. Co., ǂc September 2013. </ | ||
- | |||
- | For all above examples: | ||
- | |||
- | === Manufacture date with Publication Date: (RDA 2.17.13) === | ||
- | |||
- | **On Resource**: | ||
- | |||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | -------------------------------- | ||
- | <WRAP INDENT CENTERALIGN> | ||
- | |||
- | **Code as**:\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | ==== Coding publication dates: a summary ==== | ||
- | |||
- | 1. If there is a publication date found on the piece in hand (i.e. published in 2018), code your date as:\\ | ||
- | < | ||
- | |||
- | 2. If there is no publication date, and a copyright date is found on the piece (i.e. copyright or ©2018), infer a pub. date from it, and code your dates as:\\ | ||
- | <wrap indent> | ||
- | <wrap indent> | ||
- | |||
- | 3. If there is no publication date and no copyright date, look for a **first** printing date (i.e. May 2018 first printing), infer a publication date from the first printing date, and code your date as:\\ | ||
- | <wrap indent> | ||
- | |||
- | 4. If there is no publication date, no copyright date, and no **first** printing date, infer a publication date from any printing date on the resource (i.e. May 2018 printing), code your date as:\\ | ||
- | <wrap indent> | ||
- | |||
- | 5. If there is no publication date, no copyright date, and no first printing date anywhere on the resource; but, on the last inside page of a book, there is a phrase similar to “Made in USA May 2018, Charleston, SC.” This is likely the first printing (manufacture) date, and we code the publication date as in #3 above. | ||
cat/original-cataloging-book.1558536369.txt.gz · Last modified: 2019/05/22 14:46 by ehardy