Your SlideShare is downloading. ×
RDA & serials-transitioning to rda within a marc 21 framework
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

RDA & serials-transitioning to rda within a marc 21 framework

747
views

Published on

Published in: Education, Business, Technology

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
747
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Thank you for coming to this workshop. We will begin with acknowledgements and overview of the topics we will be covering today and tomorrow.
  • In this session: We will take a look at the CONSER RDA Core elements list and provide some background on how those developed and were reconciled with the CONSER Standard Record (CSR) elements. 2) We’ll make sure you know how to identify RDA records in OCLC, which is very important! 3) While this may repeat some things you have already been exposed to in any previous RDA training, it is important to review some general RDA principles. 4) We’ll look at the transcribed versus “record with modification” elements. 5) This presentation will be posted on the Catalogers’ Learning Workshop Web site (http://www.loc.gov/catworkshop/RDA%20training%20materials/index.html). All links shown in the slides can be accessed while viewing the PowerPoint slides online.
  • The content of this workshop is based on these three documents, found on the CONSER Web site. There was a year long plus process to meld the CONSER Standard Record with RDA and agree upon a CONSER set of record elements. These elements are presented in these three documents. The first two are the same elements, one in RDA instruction order and the other in order of the MARC 21 fields. The third document is a step-by-step process based on those elements. We used this document to organize this workshop. All three of these documents are available as RDA MAPs. Trainers are encouraged to link to the documents, to show the structure and type of information in these three essential documents.
  • In addition, CONSER practice will be guided by the new Provider-neutral guidelines and the PCC task group reports, especially those from the Hybrid Record Guidelines Task Group and Relationship Designator Guidelines Task Group. Note: This slide will change over time, as approved content from the reports is incorporated into PCC documentation.
  • RDA records are identified by $e rda in the 040 field. The PCC preferred best practice is to enter the $e rda immediately after the subfield $b. This element says: “RDA was used as the content standard in this record.” Historically in WorldCat the absence of subfield $b has indicated that English is the language of cataloging. OCLC now recommends always coding this element . (http://www.oclc.org/bibformats/en/0xx/040.shtm) Additionally, PCC has decided that members will code Leader/18 as “i” since PCC libraries use ISBD punctuation in the bibliographic records created.
  • Here is an example of these two coded elements in an OCLC bib record (selected fields only). Note on 040: This shows a preferred order that PCC and OCLC have endorsed. The order is not enforced by OCLC validation, work forms or formal PCC statement on best practice … yet! However, you are highly encouraged to follow the order: $b eng $e rda $c etc. when adding $e rda to a record. If you encounter an 040 coded as an English-language RDA record but find that the record lacks fixed field Desc “i“ and/or the description doesn’t follow RDA conventions, assume that the record is supposed to be an English language RDA record and edit accordingly.
  • Other clues, but not sure bets: New MARC 21 fields developed for RDA: 264, 336, 337, 338 – but these fields can also be added to AACR2 records, so taken by themselves, they may not indicate that a record is cataloged according to RDA. 264 = Production, Publication, Distribution, Manufacture, and Copyright Notice
  • Treat as “clues” only!
  • PCC allows elements like the 264 and 33X fields to be added to pre-RDA records and gives guidance on how to do that without converting the record completely to RDA. These have been in effect since 2011 and so you may see some pre-RDA records that contain these three new fields; but that was all the “hybrid-ness” allowed prior to implementation! PCC Guidelines for Enhancing & Editing non-RDA Serial Records available http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Hybrid-Guidelines-Serials-Post-Impl.docx provides instructions on how to add or edit data elements in non-RDA bibliographic records. The Post-Implementation Hybrid report contains general guidelines for working with non-RDA bibliographic records after the implementation of RDA, which is identified as March 31, 2013, the date established by the Library of Congress for its implementation of RDA and generally considered to be the beginning of wider adoption of RDA.
  • This is a record for a CD-ROM. Notice that a carrier term “computer discs” has been used in $a of the 300 field, and the term “illustrations” has been spelled out. Note that the abbreviated form of inches has been used according to the instructions in the alternative in 3.5.1.3 and the LC-PCC PS. We see also that the 264, 336, 337, and 338 fields are in this record. The 33X fields are controlled by lists in RDA. There are also associated codes defined for the MARC 21 format that correspond to these terms. Note to trainer: Content from this screen will be explored in more detail in module 3b
  • A title of a work is just a word or character or group of words and/or characters by which a work is known. A work can have a number of different titles, but only one is the preferred title. The preferred title of a work is the title that is chosen as the basis for the authorized access point representing the work. For most resources, it is based on the title proper of the first manifestation. If the title proper varies on later manifestations, the preferred title is the “title by which the work has become known through use in resources embodying the work or in reference sources.”
  • An access point is just a name, term, code, etc., representing an entity. There could be a number of access points for an entity. For example, Bill Gates, William Gates, and William Henry Gates refer to the same person. An authorized access point is the standardized access point representing an entity. In our current MARC structure, it would be the 1XX in an authority record.
  • And now, finally, we get to the authorized access point representing the work. It is the preferred title for the work, preceded by the authorized access point representing a person, family, or corporate body responsible for the work, if appropriate. It can also include additional elements if necessary to distinguish one work from another, which we will discuss later.
  • For many serials, if there is no creator responsible for the work in 1XX, the authorized access point is the preferred title (based on the title proper of the manifestation) plus an addition if necessary to distinguish the work from a work with the same authorized access point. If there is a creator for the serial, the authorized access point is constructed by preceding the preferred title of the work by the authorized access point for the creator.
  • Statement of International Cataloguing Principles by IFLA Cataloguing Section and IFLA Meetings of Experts on an International Cataloguing Code is available online: http://www.ifla.org/publications/statement-of-international-cataloguing-principles
  • Serial manifestation “identifying” information – instructions found in Chapter 2. Follow 1.7 (and LC-PCC PS) for transcription instructions. All this being said, be aware that there are quite a few exceptions for serials, whenever variable data is involved in the title, numbering, and other “transcribed” fields. We will look at these in more detail further into this training.
  • Here are some reminders about RDA and transcribed elements. If you have had previous RDA training, you have probably have already heard about these.
  • Here are some reminders about RDA and transcribed elements. If you have had previous RDA training, you have probably have already heard about these. Do not abbreviate full forms of found information
  • Generally, do not convert one form of found information to another form
  • Generally, do not omit information (e.g., part of a publisher name, responsible bodies beyond three in a statement of responsibility)
  • Serial manifestation “identifying” information – see RDA Chapter 2.
  • Manifestation: carrier characteristics are recorded elements. Expressed in new ways in RDA.
  • Suggest using the OCLC macro to add these or include the proper term in the constant data record. Note: 300 $a and $c contain carrier information at the manifestation level. 300 $b contains expression level information illustrations in this example. 337 and 338 contain carrier information at the manifestation level 336 contains expression level information
  • The decision-making process for cataloging a serial in RDA follows the same general philosophical steps as in AACR2. Ask yourself three questions: Is this a serial? (Consider the mode of issuance) 2) Which issue should I use to create the catalog record? (Consider the basis of identification of the resource) 3) What sources within this issue should I use to transcribe/record the RDA elements? (Consider preferred sources of information)
  • This session deals with creating original records only. In module 4 we will talk about how to work with and edit existing records, including maintaining serial records for changes over time. All that being said, it’s good to be aware of the OCLC guidelines for RDA cataloging, which were put into effect during the U.S. testing period and are still in effect. The “new policy,” to take effect March 31, outlines changes that catalogers can make to pre-RDA records now, as well as the machine manipulations that OCLC will be undertaking. We’ll discuss this in greater depth in module 6 http://www.oclc.org/en-US/rda/old-policy.html (ends 3/30/13)
  • These PCC guidelines provide guidance for working in a mixed environment where we all have to work with both RDA and AACR2 records. We will talk more about this in a later session, but general principles apply (and mostly reiterate those found in the OCLC guidelines): Duplicate AACR2 and RDA records are not allowed Never convert an RDA record to AACR2 Generally, it is up to catalogers and/or institutional policy whether to convert existing bibliographic AACR2 records to RDA (there is no requirement to do so). CONSER has some best practices on when to convert AACR2 records to RDA as part of record authentication For additional guidance on maintaining CONSER records over time, please see Guidelines for working with RDA and non-RDA records prior to implementation of RDA.
  • The very first thing you need to determine is whether you have a serial -- in other words, determining the mode of issuance. See LC-PCC PS for 0.0 – Purpose and scope, taken from former LCRI for AACR2 1.0. Note that this is the very first thing you encounter in RDA! Definition of serial found in RDA 2. 13: “ A resource issued in successive parts, usually bearing numbering, that has no predetermined conclusion (e.g., a periodical, a monographic series, a newspaper). Includes resources that exhibit characteristics of serials, such as successive issues, numbering, and frequency, but whose duration is limited (e.g., newsletters of events) and reproductions of serials.” As compared to an integrating resource: “ A resource that is added to or changed by means of updates that do not remain discrete but are integrated into the whole. An integrating resource may be tangible (e.g., a loose-leaf manual that is updated by means of replacement pages) or intangible (e.g., a Web site that is updated either continuously or on a cyclical basis).” Be very careful in situations involving changes in physical format that may require creating a new catalog record. Just because the former title is a serial, don’t assume the new one is (e.g., an online publication that was formerly issued in print). Perform the analysis for each title you catalog.
  • Example of a serial, an annual directory in paper format. It’s cataloged as a serial.
  • In online format, the directory is a database. It provides a search interface for two primatology related databases (people, organizations, field studies descriptions and more). The databases are called “Organizations” and “Field Studies”, seen at the bottom of the slide. It also provides a form for adding new entries to the database. In the online format, this would be cataloged as an integrating resource, since there are no discrete issues available. The user searches this online database and retrieves records which provide information about a particular person or organization. New records are added on a continuous basis.
  • “ Basis for identification of the resource” is what we currently call “Description based on.” (And CONSER will continue to recommend using that phrase – RDA does not prescribe language for note fields.) For resources issued in more than one part, choose a source of information identifying the lowest numbered issue or part available. This is the same as what we did in AACR2.
  • RDA 2.2.2.4 Other Resources For a resource other than one covered under 2.2.2.2—2.2.2.3, use as the preferred source of information, as applicable: either a) a label bearing a title that is permanently printed on or affixed to the resource, excluding accompanying textual material or a container (e.g., a label on an audio CD, or a model) or b) embedded metadata in textual form that contains a title (e.g., metadata embedded in an MP3 audio file). If the resource does not contain a source of information falling into either category a) or b) above, use as the preferred source of information another source forming part of the resource itself, giving preference to sources in which the information is formally presented. Not a problem for some e-resources, see current issue of Amazonas: http://www.amazonasmagazine.com/ This applies to electronic integrating resources and maybe some types of html serials; could be bit of a problem. In November 2012, the Joint Steering Committee for Development of RDA (JSC) approved with revision a proposal to allow catalogers to use eye-readable textual content as a preferred source 6JSC/ALA/21) for online resources such as IRs. See: http://www.rda-jsc.org/2012JSCdocumentoutcomes.html
  • Remember for e-serials to include the provider and date viewed in your notes.
  • The first example shows a pair: DBO and LIC. The second example show a serial that has a date of coverage (=chronological designation), but not numbering. Only the DBO is shown (for reasons of space). The third example has numbering, but lacks a chronological designation. Only the DBO is shown (for reasons of space).
  • Serials: Retrospective Cataloging LC practice/PCC practice: The following are exceptions to the preferred source of information only when cataloging retrospectively and only when there are no existing records to be cancelled: If an issue has two or more different titles and the title that appears in a less preferred source is known (because of a trademark or other symbol that appears with it) to be the stable title that does not vary from issue to issue, use the source with the stable title as the preferred source of information. 2. If two or more issues are available and the title appearing in a less preferred source remains stable from issue to issue (e.g., if the masthead title remains stable but the cover title changes from issue to issue), use the source with the stable title as the preferred source of information. 3. If a title page is added to or dropped from issues, consider that the serial lacks a title page and identify the preferred source of information according to the priority order of sources. Include other titles as variant titles (RDA 2.3.6) if important for identification or access.
  • In sections 3a and 3b, we will be identifying manifestation elements. Section 3c will look at three special cases.
  • The following slides will take a step by step look at the elements added to a serial bibliographic record. We will point out where in RDA the instructions are and take a look at examples along the way. We will also highlight new practices for RDA and point out what hasn’t changed
  • In this session, we will touch on three special cases: microform reproductions, print reproductions, and provider-neutral serials. Due to time constraints, we cannot explore these situations in depth. Watch for future PCC training if you are interested in any of these topics.
  • The following slides will take a step by step look at the elements added to a serial bibliographic record. We will point out where in RDA the instructions are and take a look at examples along the way. We will also highlight new practices for RDA and point out what hasn’t changed
  • ISSN is core for RDA. As the ISSN may come from any source, catalogers may choose to use the ISSN Portal as an authoritative source. Also of possible interest: The CODEN is another manifestation identifier. It is a six-character code used for scientific publications, both serials and conference proceedings. Copy Trainer’s note from VB’s PPT.
  • RDA 1.7.1 has two LC-PCC PS, the first general LC-PCC PS describes transcription and punctuation. The second PS is attached to the Alternative in 1.7.1 and talks about Capitalization: LC and PCC catalogers may transcribe what they see or use Appendix A. 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.’
  • Note: include marks of omission, even if they occur at the beginning of the title. Reminder: The 245 field, second Indicator is zero when the title begins with an ellipsis ; e llipses count as nonfiling characters if they follow the initial article .
  • Note: Exceptions to transcription
  • If the title is the name of a body, supply resource information in a note. This is a change from pre-RDA rules when catalogers gave bracketed other title information: Pre-RDA: 245 00 $a Conference on Tax Planning for 501(c)(3) Organizations : $b [proceedings]. RDA generally doesn’t allow such cataloger additions.
  • Note: Exceptions to transcription
  • Note: Exceptions to transcription Note: Only consider acronym v. full form if both appear on the preferred source. Record acronym as a variant title as in the example shown.
  • Note: Exceptions to transcription Do not supply square brackets for devised title. Instead, give a note. Trainer could introduce this slide: How many of you encounter situations where resources lack a source that could be used as the preferred source? This may not be common in some libraries, but may be encountered for specialized collections, especially collections including local documents. For example, minutes of meetings, especially serials consisting of mimeographed, stapled pages.
  • RDA glossary definition of parallel title proper: The title proper in another language and/or script. Under RDA 2.3.3.2, parallel titles may be taken from any source within resource Consult the CONSER RDA Core Elements table and CONSER RDA Cataloging Checklist #12 for assistance.
  • The example shows the recording and MARC 21 coding of a parallel title that appears on an issue of serial later than the issue used as the basis of identification. The example also shows the addition of the non-Latin form of the parallel title according to instructions in LC-PCC PS 1.4, first alternative and PCC Guidelines for Creating Bibliographic Records in Multiple Character Sets (http://www.loc.gov/aba/pcc/bibco/documents/PCCNonLatinGuidelines.pdf)
  • Variant titles may be taken from anywhere within the resource or may be associated with the resource. Variant titles could come from pages within a serial (running title) or reference sources. Some may reflect later titles (minor title change); this will be discussed in a later session.
  • Other title information must come from same source as title proper, and this is a transcribed element. In the example, the other title information comes from the same source as title proper and the cataloger added it because it was thought it would help clarify the title.
  • Take statements of responsibility relating to title proper from the following sources (in order of preference): a) the same source as the title proper (see 2.3.2.2) b) another source within the resource itself (see 2.2.2) c) one of the other sources of information specified under 2.2.4. Note: Statement of responsibility is a CORE element in RDA, but it is not CORE for CONSER. For CONSER, a statement of responsibility is not required if NARs are established. Catalogers creating RDA records without NARs, should transcribe names, whether in statement of responsibility or note (550 for issuing body). Catalogers are also encouraged to add a statement of responsibility or note whenever the name is important for identification. See CONSER RDA Cataloging Checklist #14 and CONSER RDA Core Elements documents
  • Example of using 550
  • Here are examples of authorized access points for corporate bodies, showing the use of one or multiple relationship designators. On this slide, all of the relationships are work-level; but “author” is the only one that designates a creator. Both “issuing body” and “sponsoring body” are other entities associated with the work designators.
  • If the hyperlink does not work, use: http://www.loc.gov/aba/pcc/documents/264-Guidelines.doc Note: Multiple 246 fields will appear for simultaneous occurrence of multiple roles (e.g. publisher, distributor, manufacturer).
  • Why is Virginia spelled out in the example? Appendix B.4 Transcribed Elements: For transcribed elements, use only those abbreviations found in the sources of information for the element. If supplying all or part of a transcribed element, generally do not abbreviate words.
  • Note: While RDA 2.8.1.4 provides for optionally omitting levels of corporate hierarchy not required to identify the publisher name, it is LC/PCC practice according to LC-PCC PS 2.8.1.4 to generally not omit levels in corporate hierarchy. [Reminder from Bob Maxwell]]
  • Date of publication -- MARC 264 (second indicator 1) $c (RDA 2.8.6; also see LC-PCC PS information) Record Publication Date of first and last issue if the dates are known and the first or last issues are in hand . Do not apply second to last sentence in 2.8.6.5: Do not supply an approximate date or dates if the first and/or last issue, part, or iteration is not available. Do not supply Publication Date of first and last issue if the dates are not known (final sentence in 2.8.6.5).
  • Not required for serials (LC-PCC PS 2.11)
  • Extent is core in RDA only if the serial is ceased. However, CONSER practice is to provide extent for tangible non-print serials such as CD-ROMs or microforms whether the serial is live or dead. For a ceased serial, the extent element (MARC 300 $a ) can consist of just the term, e.g., “300 ## $a volumes” Per 3.4.1.5, catalogers may use the terms listed in Chapter 3 or a commonly-used term, e.g., CD-ROMs From Chapter 3 Common carrier characteristics Extent Dimensions Carrier type Media type Characteristics for other than volumes as carriers (e.g., CD-ROMs, digitized files, videotapes) Illustrative content -- MARC 300 $b (RDA 7.15) Dimensions -- MARC 300 $c (RDA 3.5)
  • Ceased serials: RDA Core requires the carrier term to be specified for all ceased serials. However, per CONSER RDA Cataloging Checklist #19, only the term (e.g., “volumes” or “computer discs”) is required. Provide extent and carrier term if known (e.g., 300 ## $a 16 volumes) From Chapter 3 Common carrier characteristics Extent Dimensions Carrier type Media type Characteristics for other than volumes as carriers (e.g., CD-ROMs, digitized files, videotapes) Illustrative content -- MARC 300 $b (RDA 7.15) Dimensions -- MARC 300 $c (RDA 3.5)
  • Currently-published serials: CONSER RDA Core Elements Metadata Application Profile (MAP) further instructs catalogers to provide a term for type of carrier for tangible, non-print formats. Some people prefer to always provide extent (300 $a volumes) whether or not the serial has ceased, to help identify a resource as being print. That’s ok. Provide carrier term for tangible non-print whether live or dead per CSR, optional for giving carrier term Q: Should we always include 1 online resource for online? A: it is not required to include extent for online resources for serials. From Chapter 3 Common carrier characteristics Extent Dimensions Carrier type Media type Characteristics for other than volumes as carriers (e.g., CD-ROMs, digitized files, videotapes) Illustrative content -- MARC 300 $b (RDA 7.15) Dimensions -- MARC 300 $c (RDA 3.5)
  • Training note re 300 $c (Dimensions of carrier): LC practice Record the diameter of discs in inches ( RDA 3.5.1.4.4 ) and for all audio carriers; otherwise, follow the RDA instruction as written. Note that the abbreviated form of inches has been used according to the instructions in the alternative in 3.5.1.3 and the LC-PCC PS
  • Credit for slide: Bob Maxwell
  • Each of these three fields work the same way. Terms for subfield $a are derived from controlled RDA lists: Content type 6.9.1.3 Media type: 3.2 Table 3.1 Carrier type; 3.3.1.3 For 336-338, subfield $b is the coded form for the term in $a. The codes are derived from lists maintained in MARC 21 documentation: http://www.loc.gov/standards/valuelist/rdacontent.html http://www.loc.gov/standards/valuelist/rdamedia.html http://www.loc.gov/standards/valuelist/rdacarrier.html For PCC only the term is required for each field. The codes are optional and are easily added by using the OCLC Connexion macro for them “Add 33x” or added to a template or constant data form. Please don’t remove the code in existing copy even if your institution would not optionally add them. The entire 33x field can be repeated or subfields can be repeated.
  • RDA 6.9.1.1 Content type: “… a categorization reflecting the fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived. For content expressed in the form of an image or images, content type also reflects the number of spatial dimensions in which the content is intended to be perceived and the perceived presence or absence of movement.” Terms for content type come from: RDA 6.9.1.3, Table 6.1 Content type is a controlled, closed vocabulary. Terms can only be used as they appear on the list. Terms are used exactly as they appear on the list. Other and Unspecified are also on the list If you have a content type that does not appear on the list, use “other.” If you cannot determine the content type you have use unspecified. Catalogers not finding a term should use “other”; and should request that a term be created. Requests may be sent to: LChelp4rda@loc.gov or if PCC members to the Standing Committee on Standards
  • RDA 3.2.1.1: Media type: is a categorization reflecting the general type of intermediation device required to view, play, run, etc., the content of a resource. Terms are listed in RDA 3.2.1.3
  • Media type example for a textual serial: term = unmediated code= n
  • Categorization reflecting the format of the storage medium and housing of a carrier in combination with the type of intermediation device required to view, play, run, etc., the content of a resource. (RDA 3.3.1.1) The examples listed here are the broad carrier types, an example of specific carrier terms is given in a later slide.
  • Example: carrier term and code for a print serial: carrier term = volume code = nc
  • This slide and the next illustrate a partial description for a print serial and an online serial
  • This slide and the next illustrate a partial description for a print serial and a CD-ROM serial
  • Training note re 300 $c (Dimensions of carrier): LC practice Record the diameter of discs in inches ( RDA 3.5.1.4.4 ) and for all audio carriers; otherwise, follow the RDA instruction as written. Note that the abbreviated form of inches has been used according to the instructions in the alternative in 3.5.1.3 and the LC-PCC PS
  • “ Frequency” is not core for RDA, but current frequency is core for CONSER. Reminder: This slide regards creating a new record. CONSER practice is that for original cataloging, only current frequency is required. (This practice differs from maintenance, where former frequency data are retained.)
  • Record Numbering in 362 1 note field according to CONSER RDA practices Record numerals in the form in which they appear on the source of information (LC-PCC PS 1.8.2. first alternative) 1.8.2-4, LC-PCC PS apply first alternative, don't apply second alternative Substitute numerals for numbers expressed as words. When recording inclusive dates and other inclusive numbers, record both the first and last number in full. EXAMPLE 1967–1972 Source of information reads: 1967–72 When recording ordinal numbers (expressed either as numerals or as words) taken from an English-language source, record them as numerals in the form 1st, 2nd, 3rd, 4th, etc.
  • RDA gives no guidance on: Preferring the source with the most complete numbering (although often it may be the source with the title) Piecing together numbering from different sources
  • BACKGROUND on piecing together numbering: Dave Reser email: 2/15/2012 Those cancelled LCRIs were not brought over to the LC-PCC PSs for the same reason they were cancelled in the first place.  Since the LC-PCC PSs at 2.6.2.3, 2.6.3.3, 2.6.4.3, 2.6.5.3 say to generally give the note (2.20.5) which allows you to use "any source," I suspect you can give the more complete presentation in an un-formatted 362.  You do seem to be stuck, however, if you are giving a formatted 362 to the order of the sources specified. How to remedy?  1)  ignore, thinking that most would use the un-formatted, so not a problem. 2)  issue an LC-PCC PS at those instructions to restore the wording about the most complete presentation. 3)  suggest that the RDA source instructions be changed. Are any of those a possibility, and if so, is there a CONSER preference? Other options? CCM 8.3 b. Preferred sources While numbering may be taken from any source when needed, generally prefer a source with the most complete presentation of the numbering provided that it appears prominently or is stated formally (LCRI 12.3). “Most complete” does not necessarily mean that the components of the numbering are spelled out, only that they are present. For example “1:1" would be preferred over “vol. 1, no. 1" if this form were given more prominently in the issue. When choosing among multiple sources that are equally prominent and each bear the numbering, consider the check-in of future issues and the ability for the numbering to be easily located in the issue.
  • CCM 8.3 d. Piecing together the numeric designation and the chronological designation The numeric designation may be taken from one source and the chronological from another (LCRI 12.3). The numeric designation may be pieced together from various sources when it is clear that the publisher intended both parts to constitute the numeric designation. When this is not clear, do not piece together the numeric designation from more than one source. For example, "volume 1" appears on the cover and "issue 1" appears on the editorial page. Is "issue 1" another way of saying "volume 1" or is it a part of the volume (i.e., vol. 1, issue 1)? If a later issue is also in hand showing volume 1, issue 2, then the publisher's intent is clear and both may be transcribed as the numeric designation.
  • The CONSER RDA CORE Elements table instructs catalogers to use a note to describe numbering (2.20.5). The note, coded as MARC 362 first indicator 1, allows catalogers to use numbering from any source. So, if the preferred source has only part of the numbering (e.g., volume but not issue number), then the cataloger may use numbering from another source--such as the masthead--to precisely identify the issue. BACKGROUND on capitalization in this example: Appendix A6: Capitalize the first word or abbreviation of the first word of the numeric and/or alphabetic designation of the first issue or part of a sequence of numbering (see 2.6.2). If that element is lacking, capitalize the first word or abbreviation of the first word of the chronological designation of the first issue or part of the sequence (see 2.6.3).
  • When recording inclusive dates and other inclusive numbers, record both the first and last number in full. EXAMPLE 1967–1972 [Source of information reads: 1967–72 ] RDA 1.8.5, LC-PCC PS: When recording ordinal numbers (expressed either as numerals or as words) taken from an English-language source, record them as numerals in the form 1st, 2nd, 3rd, 4th, etc. LC practice: For ordinal numerals in languages other than English, Chinese, Japanese, and Korean, use the form 1., 2., 3., etc.
  • 2.6.1.4 Substitute a slash for a hyphen, as necessary, for clarity 2.6.2.3 If the designation consists of a year and a number that is a division of the year, record the year before the number. EXAMPLE 97-1 Designation appears on part as: 1–97
  • When is a preliminary issue used as the basis for identification? The LC-PCC PS provides useful tips on when to consider an issue to be the first true issue. The term “premier” usually indicates the true inaugural issue. However, issues labeled “sample” or “preview” are generally not production issues; instead, they are used to test the potential audience for the serial. An issue with numbering “0” may be treated as the inaugural issue. According to the LC-PCC PS to 2.1.2.3: An issue that bears numbering that precedes "1," such as "Vol. 1, no. 0," "Number 0," or "Volume 0," may be treated as the first issue, provided that there is clear evidence that the issue is not merely serving as a sample or introductory issue. RDA 2.6.2.3, 2.6.3.3 When the first issue of a sequence lacks numeric or chronological designation, but later issues define a pattern, then the cataloger should supply the designation of the first issue in brackets. 2.6.2.3 “ If the first issue or part of a sequence lacks any numeric and/or alphabetic designation, but subsequent issues or parts define a numeric and/or alphabetic designation pattern for the sequence, supply a numeric and/or alphabetic designation for the first issue or part of the sequence based on that pattern. Indicate that the information was taken from a source outside the resource itself as instructed under 2.2.” 2.6.3.3 “ If the first issue or part of a sequence lacks any chronological designation, but subsequent issues or parts define a chronological designation pattern for the sequence, supply a chronological designation for the first issue or part of the sequence based on that pattern. Indicate that the information was taken from a source outside the resource itself as instructed under 2.2.4.”
  • ISSN: Occasionally, participants will ask about the entry of ISSN in the series statement v. the authorized access point. Q: Where does the series ISSN go, in the 830 field? (similar comment made on slide 82) A: In a subfield $x. can be entered in a 490 or 830 field.
  • In this session, we will touch on three special cases: microform reproductions, print reproductions, and provider-neutral serials. Due to time constraints, we cannot explore these situations in depth. Watch for future PCC training if you are interested in any of these topics.
  • One area in which PCC cataloging practice has changed dramatically under RDA is in the description of reproductions. Instead of describing the original, we will be describing the reproduction. Any information pertaining to the original resource that is deemed important should be added to the description. CONSER practice is to include the information in a linking entry field pointing to the original. We will discuss linking entries in more detail later in the presentation (sessions 5-6). Note that some information in the fixed fields will still relate to the original, not the reproduction. Reproductions of serials will be coded as serials even if the mode of issuance is single-unit or multipart monograph. Date information will also be coded for the original. Some helpful information: all RDA instructions pertaining to manifestation level attributes for reproductions are labeled “Facsimiles and Reproductions.” Simply search for that phrase and you should find the information you need.
  • Notes: Due to space, the DBO and LIC are omitted from this slide; but it may be of interest. DBO: Caption used in DBO: According to 2.6.1.3. “When describing a facsimile or reproduction that has numbering relating to the original manifestation as well as to the facsimile or reproduction, record the numbering relating to the facsimile or reproduction. Record the numbering relating to the original manifestation as numbering pertaining to a related manifestation.” So if the Source of title: 2.2.2.2 LC-PCC PS: LC practice for Alternative : Do not apply the alternative to microforms. If the CONSER cataloger chooses to follow LC practice, then the preferred source for the title will be the image of the title page, cover, etc. (2) Related manifestations: LC-PCC PS for 27.1.1.3 describes MARC coding for related manifestations. OCLC# 797175756
  • Here is an example of a regular print reprint. For reasons of space, the 336-338 and 588 DBO and LIC have been removed from the record. In this case, the title of the reproduction on the reproduction title page differs from that on the original publication. This is one of a group of reproduction publications, all of which bear a collective title: Kurdish newspapers (even though not all are newspapers). The part title is “Hiwa magazine,” which appeared as “Hîwa” on the original source. The numbering in the record reflects the numbering for the reproduction. Here again, LC-PCC PS provides practical advice on MARC coding for reproductions when the carrier of the reproduction is the same carrier as the original.
  • In contrast with the previous examples, CONSER will not be applying the instructions regarding reproductions to online serials. Instead, CONSER has decided to continue to apply a provider-neutral strategy while we are creating records in a MARC environment. Records will be coded as RDA and will reflect RDA instructions EXCEPT for the instructions 1.11, 2.2.3.3 etc., regarding cataloging of facsimiles and reproductions. Online serials are often distributed by a variety of online providers; as in the past, details regarding these providers will be omitted from the description. A special code for the 040 field, subfield $e “pn” has been approved, so that these records can be identified. However, the new descriptive convention source code pn has not yet been implemented by OCLC; watch for an announcement. LC-PCC PS for 27.1.1.3 specifically mentions: “The guidelines do not apply when the “single-record” or “provider neutral” technique is being used.”
  • Here is an example of an e-journal record. The record should look familiar to those who commonly catalog online serials. Changes include: Lack of General Material Designator (GMD) in the title statement Use of the 264 #1 tag for the publisher statement 336, 337, and 338 fields to code content type, media type, and carrier type
  • In Module 4 we will cover how to identify and create authorized access points for works and expressions, including additions needed when there is a conflict with another authorized access point.
  • As we briefly discussed on earlier, the authorized access point representing a work is simply the preferred title for the work preceded by the authorized access point for the creator responsible for the work. Please note that relationship designators are not included in the authorized access point for the creator. Only the controlled portion is included. So in this example, the $e author and $e issuing body in the 110 field would not be included in the authorized access point for the creator. Thus, the authorized access point would be United Nations Population Fund. Maternal Health Thematic Fund annual report.
  • However, for serials, often there is no “creator” responsible for the work, meaning there would be no 1XX name access point present in the MARC record. In these cases, the authorized access point for the work is simply the preferred title of the work. And remember, the preferred title of the work only includes subfields a, n, and p, so in the first example, the preferred title is simply “Region.”
  • Now that we have briefly introduced the topic of authorized access points for works, let’s determine how to identify and construct authorized access points for works. The best place to start is by referring to 6.27.1.2 – 6.27.1.8. These instructions provide a walkthrough on how to determine authorized access points for various types of works. These instructions refer to RDA 6.2.1 - 6.2.2 and their LC-PCC PSs for guidance on how to record the preferred title of a work. As we discussed on Tuesday, the preferred title for the work is based on the title proper of the first manifestation. Next, if we are dealing with a work created by one person, family, or corporate body, we would refer to 19.2.1.1 to determine if the person, family, or corporate body was responsible for creating the work. This instruction is basically the RDA equivalent of AACR2 21.1. If we determine that the body is not responsible, we simply accept the preferred title of the work as the entire authorized access point for the work. If the body is responsible, however, we would refer to one of three RDA instructions on how to construct the authorized access point based on whether the creator is a person, family, or corporate body. Note that we would be able to skip this step if the authorized access point for the creator is already established in the NACO file. Finally, we would combine the authorized access point for the creator and the preferred title of the work to form the authorized access point for the work.
  • Let’s try a quick exercise to determine the authorized access point for a particular work. In this example, the preferred source of information states that the title of this serial is Annual Report and that it was created by the Mohamed bin Zayed Species Conservation Fund. What would the authorized access point be for this work and how would we determine it? Hint: the resource describes the internal policies and finances of the corporate body. Also, assume no conflict.
  • The first thing to do is determine the preferred title of the work which will be based on the title proper of the manifestation. Next, we need to determine the nature of the work. In this case, the serial was created by one corporate body. RDA 6.27.1.2 then instructs us check 19.2.1.1.1 to determine if the corporate body is considered to be the creator. Based on the nature of the work, we determined that it did meet the instruction criteria so our next step is to construct the authorized access point for it using 11.13.1. Luckily for us, there is no conflict so the authorized access point is simply the name of the corporate body with no additions. So after all this, we get … [move to next slide]
  • Unfortunately, it is possible that the authorized access point for a work may be in conflict with a different work. Consult LC-PCC PS 6.27.1.9 for instructions on when and how to modify an access point for a work. One difference to note between previous and current CONSER practice is that we must check for conflicts in all types of resources, not just serials. Additions to the authorized access point of a work are required when it is exactly the same as the authorized access point of a different work. Use cataloger’s judgment when authorized access points are “similar.”
  • In this scenario, the authorized access points for each work are the same, so an addition would be required for the authorized access point of the incoming work.
  • In this completely made up scenario, it would be cataloger’s judgment whether or not to include an addition to the authorized access point of the incoming work.
  • There is no prescriptive list of terms that can be used as qualifiers for authorized access points, though common qualifiers include corporate body, date of publication, descriptive data elements, and the place of publication. This example shows the place of publication as the qualifier. Note that if you use the place of publication as a qualifier, you should use the form of the place as found in the NACO file.
  • Here is an example of publication date used as a qualifier
  • And this is an example of a corporate body used as a qualifier.
  • Note: The use of date as a qualifier is often used when a serial has changed title, then changed back.
  • The authorized access point for an expression is constructed simply by adding to the authorized access point for the work. Consult LC-PCC PS 6.27.3 for when and how to create an authorized access point for an expression. This is following LC practice. PCC practice is still pending.
  • This example of a language edition shows the authorized access point for an expression in the 130 field. In this case, the authorized access point for the expression is formed by adding $l English to the authorized access point for the work, which was simply the preferred title of the work in Hebrew.
  • Remember to consider the entire authorized access point for a work when checking for conflicts. If a monograph and serial share the same preferred title, but the monograph also has a 1XX name field while the serial does not, the authorized access points are not the same.
  • Finally in session 5, we will discuss relationship designators and linking relationships in RDA and MARC, including some common serial relationships.
  • RDA provides a long list of relationship designators in several appendices. Appendix I is for relating resources with people, families, or corporate bodies and appendix J is for relating resources with other resources. However, if you are unable to find a term in the appendices that is appropriate, you may supply your own.
  • Not all relationship designators are taken from RDA. Some are directly encoded in MARC. Note: For catalogers of integrating resources, beware that the corresponding RDA relationship for earlier/later titles is: “supersedes (work)” and “superseded by (work)” (Appendix J.2.6)
  • http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Relat-Desig-Guidelines.docx
  • While RDA provides many relationship designators, it is CONSER practice to designate some relationships with MARC 21 coding definitions or in some cases using terms that are not in the RDA relationship designator lists. For example, it is CONSER practice to designate “Continues/Continued by” relationships using 780/785 00, format relationships using 776 08 $i Print/Online version, and language versions using 775 08 $i English edition, etc.
  • List of the common serial relationships in our records. We will continue to relate earlier/later works. At the expression level, we will continue to relate language expressions. And at the manifestation level, we will continue to relate manifestations in different formats or modes of issuance, as well as original and reproduction.
  • This first example indicates that the work being described is a supplement to another work, and the second and third examples show earlier and later works. No relationship designator is needed because the MARC tag number and indicators tell what the relationship is. In the last two examples, $i has been added to indicate what the relationship is because the 787 just means “other relationship.” In the last example, the relationship designator was taken from RDA Appendix J.
  • The first example here shows a related expression, or other language edition, the next two examples show related manifestations of different formats, and the last example shows a reproduction relationship. The format of the relationship designators in $i follows CONSER practice for the first three examples, and use of a relationship designator (RDA Appendix J.4.2, per ) for the last example. If a serial changes media type, CONSER practice is to include only a 776 linking entry relationship rather than also including a 780/785 relationship. A similar practice is used for changes to mode of issuance Two notes on reproductions: first, if the reproduction is the same format as the original, a 775 is used. If the format is different, a 776 is used. Second, related manifestation is a core element for LC for reproductions.
  • While it is CONSER practice to generally enter relationships in 1XX or 7XX fields, they can be included in 5XX note fields in some instances. These are some examples of relationship notes.
  • So far, we have covered RDA terminology and the initial decisions that need to be made when creating a new record for a serial. We have followed, step by step, the creation of a new manifestation description. Then, we explored the attributes of works and expressions for serials and practiced creation of work authorized access point. Finally, we have looked at relationship designators and how to express them in RDA (and in accordance with CONSER practice). Now, we will turn to questions related to change over time. [next slide]
  • In Session 6, we’ll explore the questions: --What kinds of change can be accommodated in the existing RDA description? --How can we modify our legacy pre-RDA records using RDA? --When should we consider re-describing pre-RDA records? --What are the situations requiring creation of a new description?
  • Starting with the first question… the list on this slide and the next show types of changes that can be accommodated in existing records. Carrier types, coded in MARC 338 field and in MARC 300 subfield $a extent, are below the level of media type. For example, within the media type “computer” carriers, a serial may be issued in CD-ROM, DVD-ROM, or online format. Since all are formats of the same media type, they may be accommodated in the same bibliographic record—the same manifestation-level description. All of the minor title changes defined under AACR2 were migrated without change to RDA. These include change from full form to acronym; addition, deletion, or re-ordering of resource terms; and addition, deletion, or re-ordering of names representing the same corporate body. Some changes to edition statements are minor, others major. This represents no change from AACR2. If, for example, an annual serial has an edition statement “World edition” that is dropped without change to the type of content, the change can be accommodated in a note (coded 500). Publisher, distributor, or manufacturer statements, coded in MARC 264, may be accommodated in existing records. Let’s look at a few more situations, and then we’ll try them out.
  • 5. Changes in series appearing on a serial can be accommodated by multiple statements coded in MARC 490 fields (and, if controlled, 8XX—usually 830—fields). 6. Changes to issue numbering (as in AACR2) are never considered “major” changes. If the cataloger has the first issue under the new numbering, that can be recorded in a numbering note coded MARC 362 first indicator “1.” If the first issue is lacking, the MARC code will be a 515 note. 7. As under previous rules, current frequency is coded in MARC 310; earlier frequencies are coded, MARC 321 fields. Following the convention beginning with the CONSER standard record, catalogers are encouraged to leave existing data in the record even if the number of historic frequency notes exceeds three statements. 8. Finally, sponsors, issuing bodies, and other associated persons, families, and corporate bodies may be recorded in an existing record. Now, let’s go back and look at some examples. We will only be looking at a few changes: Carrier type, minor title changes, publisher changes,
  • Let’s return to the first case: Changes to carrier types below the level of media type. Here are some specific instances. For serials catalogers, a significant change in RDA to past practice has beenthat when publications in CD-ROM change to DVD-ROM or go online, no new record has been needed. Instead, RDA catalogers were to accommodate these changes on existing records. In November 2012, JSC approved with revision a proposal submitted by ISSN (6JSC/ISSN/1) related to the last example on this slide. The proposal affects multipart monographs and serials (3.1.6.1, LC-PCC PS 1.6.2.2) and instructs catalogers to “Create a new description if there is a change in the carrier type of a serial to online resource from another computer carrier, or vice versa.” After this JSC revision is implemented, a serial that changes from CD-ROM to online will require a new description.
  • How would you edit this record to show that the carrier changed from CD-ROM to DVD-ROM? NOTE: Since the media type (computer) and carrier type (computer disc) remain the same, the MARC 337 and 338 fields are not included.
  • Options: Could change 300: 300 ## $a computer discs ; $c 4 ¾ in. Add 500 note, e.g.: 500 ## $a Issues for 1989/1992-1997/2001 on CD-ROM; issues for 1998/2002- on DVD-ROM. Note that the abbreviated form of inches has been used according to the instructions in the alternative in 3.5.1.3 and the LC-PCC PS Note (in case of question): The fuller version of the record for this serial shows a related cumulation of content published monthly as U.S. exports of merchandise (OCLC 23886398). For more information about serial cumulations (as well as supplements and indexes), see: LC/PCC PS 0.0. Example: index medicus / Cumulated Index medicus.
  • No changes have been made to the criteria for considering major and minor changes to the title proper of serials. No changes have been made to consideration of how to accommodate variant titles appearing on later issues. For more guidance on coding, consult: step 15 of the CONSER RDA Cataloging Checklist and page 2 of the CONSER Core Elements MAP.
  • But just as a reminder, this slide shows the general pattern for coding minor changes of title, changes to parallel titles, and title variants appearing on later issues.
  • Minor edition changes, just as with AACR2, may be handled with notes. This example, as many of you will recognize, is taken directly from the SCCTP Advanced Serials Workshop
  • Publisher/distributor/manufacturer/copyright: Beginning in September 2011, CONSER catalogers have been using the 264 field to code publisher, distributor, and manufacturer data For simplicity, the current screen shows coding for publishers. Distributor data would be coded in a 264 field with second indicator 2; manufacturer data would be coded in a 264 field with second indicator 3. There is also a second indicator 4 for copyright data; but for serials, copyright data is less commonly coded. Let’s try this out. ---------- Additional note: RDA 2.11 LC-PCC PS: LC Practice for core element: It is not required to record copyright dates for multipart monographs, serials, and integrating resources.
  • The journal Cognitive dissidents began in 1987, but the first issue received by the library was for Volume 1, number 5 Nov 15, 1987. Note that “Nov” appeared that way on the issue. Later, the library received more issues, though not a complete run. The earliest issue showing a move of the publisher to Tonawanda was “February 1990”; and the earliest issue showing that the publisher moved to Las Vegas had a coverage date of February 1991. The last issue received by the library was for Volume 7, issue #1 with coverage date May 15, 1993. How would you show this information?
  • Possible answer. Recording the change to Tonawanda is cataloger judgment, since the state did not change from New York. But the change to Las Vegas should be recorded since it involves a different state. Note that currently, there is no requirement to change a 260 if the original record has data coded in a 260 field. In any case, a subfield $3 materials specified note would be added to the beginning of the field. Then additional 264 fields would be added.
  • CONSER practices for recording changes to frequency have not changed since the CONSER Standard Record guidelines were issued. Catalogers still code current content in the 310 field and earlier frequency (from earliest to most recent) in sequential 321 fields. In contrast to CONSER practice when creating original records, CONSER practice for maintenance is still to keep all historic data unless it is inaccurate.
  • The RDA instructions for when to record numbering changes follow the previous CONSER practice. How to record the numbers themselves has changed, as we saw in Session 3. The first example illustrates a cessation. The second example illustrates a new series, where the cataloger lacked the first issue of the series. The issue in hand is shown in angle brackets. Note that spacing conventions for angle brackets have changed somewhat. See LC/PCC PS 1.7.1 [If a further review is needed: The change is that numbering, even in a note field, is given in a modified transcribed form. That is, captions such as “volume” and dates such as “February” are spelled out if found that way on the issue. However, as was also mentioned in session 3, numbers themselves are given in numerals if they appear as spelled out; and ordinal numbers for European language serials may appear with a numeral plus period (e.g., 2. for segundo)] For Trainers: see: 2.6.1, 1.7, 1.8 and LC/PCC PSs 2.6.2.3: If a new sequence with the same system as before is not accompanied by wording such as new series, supply new series or another appropriate term. Indicate that the information was taken from a source outside the resource itself as instructed under 2.2.4.
  • CCM13.2.2 promotes a preferred style that makes it easier for future record maintainers to extend the note. While this preference was developed prior to RDA, the examples in RDA 2.20.3.6.2 also illustrate this model.
  • When maintaining records, the CONSER practices regarding maintenance of Fixed Field elements and entry of a Latest issue consulted note still apply. We have completed our consideration of RDA changes at the manifestation level. Now let’s turn our attention to Expression-level change…
  • While OCLC CONSER records in MARC have always included expression-level data, RDA considers this data explicitly. So far, RDA instructions related to serials and integrating resources only address expression-level changes that can be accommodated in the existing description. Please keep in mind that this situation, where the title is constant but the language (or script) of the content changes, is different than the more common situation where a serial undergoes a major change of title at the same time that the language changes. A major change of title requires a new description for a serial per 1.6.2.3 (with 2.3.2.13.1). Additional note: For the benefit of the trainer, here is the text of 7.29.2.3.1 7.29.2.3.1 Multipart Monographs and Serials: If a content characteristic is changed in a subsequent issue or part, make a note if the change is considered important for identification or selection. If the changes have been numerous, a general statement may be made. 7.29.2.3.2 Integrating resources: Make notes on content characteristics no longer present on the current iteration if the change is considered important for identification or selection. If the changes have been numerous, a general statement may be made.
  • Work-level records may also accommodate change. In our current environment, catalogers may not be aware of the elements of the record that contribute to enhancing the work-level description. The most common work-level enhancement that catalogers will be making is to record minor changes to the title proper, parallel language titles, and variant titles that appear on later issues.
  • These bullet points reflect guidelines for editing AACR2/CSR records. Interim report: http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Bib-Interim-RDA.html Final report of the PCC Post-Implementation Hybrid Bibliographic Records Guidelines Task Group (chair, Gene Dickerson): http://www.loc.gov/aba/pcc/rda/RDA Task Groups.html The final report of the Post-Implementation Hybrid Records Task Group was issued in October 2012; it is pending approval of the PCC Policy Committee. If approved, the content will be incorporated into CONSER documentation and practices. In general, AACR2/CSR records can be maintained using RDA instructions on change. If the data coded in the 260 field has changed, and if the role of the body named is known, the cataloger may choose to recode the 260 field to a 264 field. If the role is not known, then the cataloger would leave the tag as 260. In either case, insert a subfield $3 materials specified note to show coverage range and then add new 264 fields. In addition to changes in issues, without removing the General Material Designator (245 $h), catalogers may add 336-338 fields.
  • Take a few minutes to consider this exercise. This AACR2 record is coded 042=pcc FF: Ctry: pau 264 #1 $3 1923- : $a [if the College is considered to be acting as a publisher] 264 31 $3 <2012-> : $a Philadelphia, PA : $b Taylor and Francis 310 ## $a Five times a year, $b <2012-> 321 … 321 # # $a Four no. a year, $b 1970- 588 ## $a LIC: Volume 87, issue 4 (2012). ------------- Could also add 336-338
  • Here is one possibility. FF: Ctry: pau 260 ## $3 1923- : $a [if the College is considered to be acting as a publisher, cataloger could also re-code to 264] 264 31 $3 <2012-> : $a Philadelphia, PA : $b Taylor and Francis 310 ## $a Five times a year, $b <2012-> 321 … 321 # # $a Four no. a year, $b 1970- 588 ## $a LIC: Volume 87, issue 4 (2012). ------------- Could also add 336-338 NOTE: Participants may wish to discuss whether CONSER should establish some sort of practice regarding the 500 Published: note (recognizing that some of these notes lack adequate information to convert.)
  • Building on the report issues by the Interim Hybrid Record Task Group, in November 2011, CONSER discussed a proposal for editing pre-AACR2 successive entry records using RDA (“Proposal: Maintaining AACR1 Records in a Mixed Code Environment”). This document is still available for use, but will be replaced once the Final Report of the Post-Implementation Hybrid Records Guidelines Task Group has been approved. Before editing a pre-AACR2 successive-entry record, the cataloger needs to identify the issue used as the basis of identification. Reminder: The latest, rather than earliest issue, was used as the basis of description for these records. As a result, minor changes to the title proper were reflected in the 245 field. If a 936 field is present, use the last issue coded. For example, if the record has 936 ## $a 1974 $a v. 18, no. 9 (May 1999) … then the “Description based on:” will be “v. 18, no. 9 (May 1999)” If there is no 936 and no evidence of other dates, but a formatted 362 field, then use the issue in the 362 field for the DBO. Otherwise, omit the DBO. After establishing a DBO, follow RDA instructions in maintaining the record. In addition to data from the issue in hand, the cataloger may add 336-338 fields. Always check for a truncated title (“Report” rather than “Report of the [Body].” If the cataloger has an issue or surrogate, replace the truncated title with a title proper transcribed according to RDA. Note for trainers: This introduces a new technique in order to get around the problem that pre-AACR2 records have a description based on the latest issue rather than the earliest issue. By explicitly specifying the issue used as the basis for description (wherever practical), we can establish a stable start point for the description. This allows us to build on the description as we would an AACR2 description, as long as the cataloger watches out for partial titles in the 245 field. The hope is that with this technique, catalogers who learn RDA as their first code will be able to apply RDA guidelines to maintenance of all legacy records except those reflecting latest entry cataloging. But this does reflect a change from the CONSER practice of editing a record according to the code used to create it.
  • How could this record be edited to reflect the change? FF Ctry: mdu 260 ## $3 Feb. 1979- : $a [Tempe, Az.] $b German Studies Association [etc.] 264 3 1 $3 <May 2012-> : $a Baltimore, Maryland USA : $b The Johns Hopkins University Press 588 ## $a Description based on: Feb. 1979. 588 ## $a Latest issue consulted: Volume 35, number 2 (May 2012). 776 0 8 $i Online version: $t … Could also add 336-338 So far, we have been focusing on building on existing records with RDA elements, without changing the coding to RDA. But are there any situations when catalogers might prefer to re-describe a serial (if the appropriate issues are available and if supported by institutional policy)?
  • Following hybrid record guidelines 33X fields were added to this Pre-AACR2 record
  • If the cataloger is unable to determine the basis of description on a pre-AACR2 record, at a minimum, the 264 and other fields can be added to the record based on the latest issue and a 588 Latest issue consulted note added.
  • Discussion item: Here are three situations meriting consideration. In which cases would you recommend re-description? (1) How many would re-describe to RDA in the first case, where a pre-publication record is being described based on volume 1, issue 1? (2) Assuming issues (or surrogates) were available, how many would re-describe in the second situation, where a serial entered under society would require a new record; and entry under title would not? (3) How many would re-describe if backing up a record?
  • The preceding slides have discussed accommodating new data in existing records. Now, we will turn to situations requiring a new record. This slide considers changes that require a new description either because a new the work-level record is needed or because a manifestation-level record is needed. As a reminder, when a new description is needed for a manifestation alone, both the ceased record and the current record are part of the same work. Work: Any changes that affect the authorized access point representing the work require a new record. If a serial has a creator and the name of the creator requires a new name authority record, then a new work-level record is required. Whenever a new work-record is required, a new manifestation record is also required. A single manifestation record cannot link to two different work records. Beyond work-level changes, new descriptions are needed for changes to mode of issuance, e.g., from serial to integrating resource; for changes to media type, e.g., print to online; and for major changes to edition. Let’s see how this works…
  • The American Health Foundation changed in 2004 to the Institute for Cancer Prevention. Is a new description needed? (major or minor title change)? Will a new work-level record be needed, or does this just affect the manifestation? Answer: This is a major change in title proper, requiring a new work authorized access point and a new manifestation description. RDA 1.6.2.3 and 2.3.2.13.1 (iii): “In general, consider the following to be major changes in a title proper: … a change in a corporate body name given anywhere in the title if it is a different corporate body.”
  • In this case, a loose-leaf (integrating resource) is now being published as a print serial. At the same time, the cataloger determined that a personal-name creator was not warranted. Is a new description needed? A new work? Answer: If the serial publication has a title but no person, family, or corporate body in the role of creator, then: Yes, this is a new work; and yes, this requires a new manifestation description. RDA: 1.6.2.1: Change in mode of issuance of a serial  new manifestation description. If this were the only change, then, both manifestation descriptions would be part of the same work. RDA: 1.6.4.2 plus 6.1.3.2: A change in responsibility requires a new authorized access point representing the work Background information: It depends in part on whether you think a work of personal author creatorship is still true when the resource changes its mode of issuance. If you think the serial can't have a personal creator, then you've hit 6.1.3.2.1 and you would have to construct the authorized access points differently (but you could relate them). --Dave Reser, email to Melissa Beck
  • This fictional situation shows a case where a title was published in CD-ROM, then on DVD-ROM. New description? New work? After that, the directory was published for a brief time as an online serial. New description? New work? Finally, in 2012, the directory is available as a database, an integrating resource. New description? New work? Answer: CD-ROM to DVD-ROM This is a change of carrier, below the level of media type. Does not meet the criterion for 1.6.2.2, so a new description is NOT needed.  accommodate in existing record CD-ROM to online: According to the original wording of RDA, this does not meet the criterion for 1.6.2.2, so a new description is NOT needed.  accommodate in existing record According to the revised wording of 1.6.2.2 and 3.1.6.1, a new description is needed. However, not a new work. Issued online as a database: According to 1.6.2.1, this involves a change of mode of issuance. A new description is needed, but this is not a new work .
  • Finally, here is a case of a work in Spanish, translated from English. The Spanish-language publication did not change, but the original publication went from “Worldnet at a glance” to “Worldnet” Is a new record needed for the Spanish-language publication? Under the same work, or a new work? Answer: Yes, new description is needed; and the description will be considered an expression of a new work (along with the English-language edition) Per RDA 1.6.2.3 and 2.3.2.13.1(i) in conjunction with 6.1.3.2, the record for the first manifestation received (in English) has undergone a major title change from Worldnet at a glance to Worldnet. Therefore, a new work authorized access point is needed. As a result, for the Spanish-language expression, the work authorized access point for title would also change.
  • Bonus exercise: Very early in RDA is an outline of types of changes requiring a new record. This familiar list is both reassuring and somewhat unsettling. It’s reassuring because it appears to mirror our previous practices. It is unsettling because the list does not clearly show which FRBR levels are affected: Work, expression, or manifestation. Now that you have considered the levels of change, how would you enhance this list to show which changes require: New work/expression AND manifestation records? New manifestation records alone? 1.6.2.1: M 1.6.2.2: M 1.6.2.3: W 1.6.2.4: W 1.6.2.5: M
  • Transcript

    • 1. RDA & SerialsTransitioning to RDA withina MARC 21 FrameworkCo-Presenters:Les Hawkins & Hien NguyenLibrary of CongressNASIG 28th Annual ConferenceBuffalo, New YorkJune 2013Accompanying handout
    • 2. Acknowledgements• Special thanks are due to:– Renette Davis– Judy Kuhagen– Robert Maxwell– UCLA RDA Continuing Resources StudyGroup– UCSD colleagues• Used with permission2
    • 3. Topics1. Introduction to CONSER RDA cataloging2. Getting started3. Description of manifestation4. Identifying work and expression5. Related works, expressions, andmanifestations6. Working with copy/When to create a newrecord3
    • 4. 1: Introduction• CONSER RDA documents• Identifying RDA records• Terminology• Transcribed vs. recorded elements5
    • 5. CONSER RDA Documents• RDA documentation on CONSER Web site:http://www.loc.gov/aba/pcc/conser/index.html• CONSER RDA core elements• CONSER MARC 21 to RDA coreelements• CONSER RDA cataloging checklist6
    • 6. Other RDA Documents• Electronic serials:Provider-neutral E-resource MARC record guidehttp://www.loc.gov/aba/pcc/scs/documents/PCC-PN-guidelines.html• Post RDA Implementation Guidelines andStandards:http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Post-RDA-Implementation-Guidelines.html7
    • 7. How to identify RDA recordsMARC coding for RDA bibliographic records:040 $a ____ $b eng $e rda $c ____PCC practice:Code for (and use) ISBD punctuation:Leader/18: value “i”8
    • 8. RDA records always have: 040 $e rdaPCC Practice: Fixed field Desc “i”9
    • 9. Other elements in RDA records• MARC fields:Production, publication, distribution,manufacture, and copyright notice (264)Content type (336)Media type (337)Carrier type (338)• Spelled out descriptionse.g., volumes, edition, illustrations10
    • 10. Other elements in RDA recordsTreat as “clues” only:• MARC fields:Production, publication, distribution,manufacture, and copyright notice (264)Content type (336)Media type (337)Carrier type (338)• Spelled out descriptionse.g., volumes, edition, illustrations11
    • 11. RDA records vs. RDA-like elementsallowed in pre-RDA records• 264 field(s)• 33X fields– May see some PCC AACR2 records withthese elements– PCC Guidelines for Enhancing & Editing non-RDA Serial Recordshttp://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Hybrid-Guidelines-Serials-Post-Impl.docx12
    • 12. RDA (and some AACR2) records have:New MARC fields, fuller transcription13
    • 13. Terminology comparison• AACR2◦ Rules◦ Areas of description◦ Physical description◦ Classes of material◦ General materialdesignation [GMD]◦ Notes• RDA◦ Instructions◦ Elements◦ Describing carriers◦ Types of content andcarrier◦ Media, carrier, and contenttype◦ Describing content andrecording relationships14
    • 14. Terminology comparison• AACR2◦ [Controlled] Heading◦ Main entry◦ Added entriesfor uncontrolled headings◦ Author◦ Uniform title• RDA◦ [Authorized] access point◦ Preferred name / preferred title(authorized access point forcreator +/or preferred title)◦ Access points◦ Creator (also author)◦ Preferred title (title proper +qualifiers to distinguish from titleof another work)15
    • 15. 161616Terminology• Title of a work: words or characters bywhich a work is known• Preferred title of a work (6.2.2.4)– Basis for authorized access point– Based on title proper of first manifestation• Variant title(s) of a work– Other title(s) in addition to the title or form of titlechosen as the preferred title for the work
    • 16. 171717Terminology• Access point – name, term, code, etc.representing an entityExamples:Title of a work, a name of person, or corporate body• Authorized access point – the standardizedaccess point representing an entityExample:110 2# $a Society of Linguists
    • 17. 181818Terminology• Authorized access point representing awork– Preferred title for the work preceded by• Authorized access point representing the creator, aperson, family, or corporate body responsible forthe work– May include additional elements if necessaryto distinguish one work from another– May be the preferred title if no creator and noconflict
    • 18. Terminology• For serials, often the authorized accesspoint is the preferred title if no creator in1XX• Conflict with the authorized access pointof another work?– Add a term to distinguish and recordauthorized access point in the 130 field– Not limited to other serial works19
    • 19. Transcription vs. Recording• ICP principle of representation = informationtranscribed as found on the resource• Other information may be manipulated whenrecorded by the cataloger (either when takenfrom the resource or from another source)2020International cataloging principles:http://www.ifla.org/publications/statement-of-international-cataloguing-principles
    • 20. Transcribed manifestationelements• Title proper and parallel title proper• Other title information• Statement of responsibility• Edition information• Numbering information• Place of publisher, distributor, manufacturer• Name of publisher, distributor, manufacturer• Series information other than ISSN2121
    • 21. Reminders about transcribed elements• Do not abbreviate full forms of foundinformation• Generally, do not convert one form of foundinformation to another form• Generally, do not omit information (e.g., partof a publisher name, responsible bodiesbeyond three in a statement of responsibility)2525
    • 22. Exceptions and options• Omit numbering from title proper or paralleltitle (use mark of omission wherever in title)• Some alternatives allow some conversionsand some omissions for some elements2626
    • 23. Recorded manifestation elements• Date of publication, distribution, manufacture• Copyright date• Mode of issuance• Frequency• Identifier of the manifestation (e.g., ISSNusually)• Key title• Notes about element (e.g., source of title)• Issue or part used as basis of description(DBO and LIC)• Notes about changes over time2727
    • 24. Recorded carrier characteristics ch. 3• Common carrier characteristics– Extent– Dimensions– Carrier type– Media type– Characteristics for other than volumes ascarriers (e.g., CD-ROMs, digitized files,videotapes)2828
    • 25. Common carrier characteristics29
    • 26. Summary• CONSER RDA core elements• RDA records identified by coding• Familiar concepts, new terminology in RDA• Some manifestation elements are transcribed• Other manifestation elements can be recorded withsome adjustment• There are many exceptions to transcriptioninstructions for serials (variable data)30
    • 27. 2: Getting started• Is this a serial?– Mode of issuance• Which issue should I use?– Basis for identification of the resource• What sources within this issue?– Preferred sources of information32
    • 28. OCLC guidelines• OCLC policy statement on RDA cataloging inWorldCat:http://www.oclc.org/en-US/rda/new-policy.html (3/31/13- )• AACR2 records may be converted to RDA• Never convert an RDA record to an AACR2record• Okay to add some RDA elements to AACR2records33
    • 29. PCC guidelines• Enhancing & Editing RDA Serial Recordshttp://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Serial-RDA.doc• PCC Guidelines for Enhancing & Editing non-RDA Serial Recordshttp://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Hybrid-Guidelines-Serials-Post-Impl.docx• Enhancing & Editing RDA Integrating ResourceRecords http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/IR-RDA.doc• Guidelines for creating a hybrid record from apre-RDA record for Integrating Resourceshttp://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Hybrid-Guidelines-IRs-Post-Impl.docx34
    • 30. Is it a serial?• RDA 2.13 (also: LC/PCC PS for RDA 0.0)• Same definition as in AACR2– Successive parts– Usually bears numbering– No predetermined conclusion• Do not assume “once a serial always aserial”35
    • 31. Serial in print formatInternational DirectoryofPrimatology1st edWisconsin Primate Research CenterMadison, Wis.36
    • 32. Database in online formatPrimate info netWisconsin Regional Primate Research CenterInternational Directory ofPrimatologyAbout IDPSearch IDPCreate or revise an entryTable of ContentsOrganizationsField studiesPart of…37
    • 33. 383838Basis for identification of theresource• If issues or parts are sequentiallynumbered, use the lowest numbered issueor part available• If issues are unnumbered or notsequentially numbered, use the issue orpart with the earliest date of issue• CONSER will continue to use the phrase“Description based on”
    • 34. 393939Preferred source: one or more pages,leaves, etc.; or images (2.2.2.2)• Title page• If there is none, use the first of the following(or images of them) that bears a title:– Cover– Caption– Masthead– Colophon• If none of these have a title, use anothersource within the resource, giving preferenceto sources where information is formallypresented
    • 35. Preferred source – other resources(2.2.2.4)• Permanently affixed label(e.g., label on a CD)or:• “Embedded metadata in textual form thatcontains a title”(e.g., metadata embedded in an MP3 audio file)• Failing these: Prefer sources that formallypresent the data40
    • 36. Source of Description (2.20.2.3)Always provide:–588 description based on note–Source of title with 588 combined withdescription based on note–588 Latest issue consulted note41
    • 37. Source of Description (2.20.2.3)588 ## $a Description based on: Volume 1, Number 4(April 2008); title from masthead.588 ## $a Latest issue consulted: Volume 2, Number 3(March 2009).***588 ## $a Description based on: June 2012; title fromPDF title page (publisher’s Web site, viewedSeptember 12, 2012).588 ## $a Description based on: Volume 10, Number11, published 2013.43
    • 38. Retrospective cataloging (2.2.2)“Serial Retrospective Exception” LC-PCC PS 2.2.2– Use stable title, even if from a less-preferred source–Consider that a serial lacks title page if the title pageis added to or dropped from issues44
    • 39. Summary• RDA decision-making process same as AACR2:– Determine that the resource is a serial– Use first or earliest available issue– Prefer sources of information as instructed• Provide information about your cataloging:– Issue used– Source of title– Latest issue consulted– Provider and date viewed (for online serials)45
    • 40. 3: Identifying manifestations• 3a: Identifying manifestations• 3b. Describing carriers, numbering, etc.• 3c: Special cases46
    • 41. 3a: Identifying manifestations (pt. 1)• Identifiers: ISSN• Title statement: Title proper, paralleltitle, other title information, variant title• Statement of responsibility• Edition statement• Publication statement51
    • 42. ISSN (2.15)• Core for RDA• Recorded element• Record as found• Take from any source• No change in practice for recording52022 ## $a 2165-476X $y 1096-1844
    • 43. Title proper (2.3, 2.3.2)• Transcribe in field 245 $a $n $p• Follow RDA 1.7.1 and LC-PCC PS– Capitalization: “encouraged” to followAppendix A, may “take what you see”• Include initial articles53
    • 44. Title proper (2.3.1.4)• Omit date, name, number that varies:245 00 $a Supply estimates for the year ending…Source of information reads: Supply estimatesfor the year ending 1997245 10 $a ... end of session report.Source of information reads: 2005/06 end ofsession report245 18 $a The ... annual report to the GovernorSource of information reads: The 2001 annualreport to the Governor54
    • 45. Title proper (2.3.1.4)• Correct obvious typographical errors245 00 $a Housing startsSource of information reads: Housing sarts• Title includes earlier title, etc.245 00 $a International gas reportSource of information reads: International gasreport, including World gas report55
    • 46. Title proper (2.3.1.5)Titles that consist solely of corporate bodies, etc.• Transcribe the name as title245 10 $a Conference on Tax Planning for 501(c)(3)Organizations.• Supply a note rather than providing bracketedother title information in 245500 ## $a Proceedings of the conference.Not 245 10 $a Conference on Tax Planning for 501(c)(3)Organizations : $b [proceedings]56
    • 47. Title proper (2.3.1.6)• Omit introductory words:“Disney presents …”• May transcribe the form with introductorywording in 246 as a variant title245 00 $a Joy of kosher with Jamie Geller.246 1 $i At head of title: $a HamodiaPresents57
    • 48. Title proper (2.3.2.5)Acronym/initialism vs. full form• Select full form if both appear on thepreferred source:245 00 $a Linguistics and languagebehavior abstracts246 1# $a LLBA58
    • 49. Title proper (2.3.2.10)Devised title (e.g., minutes of meetings)• No brackets245 00 $a Education reports• Explain in a note that the title was devised500 ## $a Title devised by cataloger.59
    • 50. Parallel titles (2.3.3.2)• Parallel title proper: The title proper inanother language and/or script.• Parallel titles can come from any sourcewithin resource.245 00 $a Shi chao246 11 $a Poetry waves6060
    • 51. Parallel titles (2.3.3.2)Recording parallel titles from later issues:245 00 $a Artmap.246 1# $i Issues for 2012- also have Arabictitle: $a ‫الفن‬ ‫خريطة‬246 1# $i Issues for 2012- also have Arabictitle: $a Khariṭat al-fann̄
    • 52. Variant titles (2.3.6)245 00 $a Toxic release inventory246 1# $i Also known as: $a TRI CD-ROM246 1# $i Issues for 1987/1993- have title:$a Toxics release inventory245 00 $a Energy & climate report.246 1# $a Energy and climate report
    • 53. Other title information (2.3.4)• Transcribe if it helps the user!– Clarify the title proper– Support the title proper• Must come from the same source as titleproper (if included)245 00 $a Moral cents : $b the journal ofethics and finance. 63
    • 54. Statement of responsibility• Provide if important for identification of theserial• Provide if it helps document usage of thecorporate body, person or family• Provide as part of authorized access point• Can record responsibility in 500 or 550 toset up pattern of usage64
    • 55. Responsible bodies: 550550 ## $a Issued by: United Nations Centre forHuman Settlements (Habitat), 1987-2001;United Nations Human SettlementsProgramme, 2003-710 2# $a United Nations Centre for HumanSettlements, e issuing body.ǂ710 2# $a United Nations Human SettlementsProgramme, e issuing body.ǂ
    • 56. Other ways to showresponsibilityRelationship designators, joint authors:• 110 2# $a Society of Linguists, $e author.• 710 2# $a Linguists International, $eauthor.66
    • 57. 710 2# $3 <2013-> $a ACM SpecialInterest Group on ProgrammingLanguages, $e sponsoringbody.Other ways to showresponsibility
    • 58. Edition statement (2.5)Transcribe as it appears:If not abbreviated on resource:250 ## $a Western Washington.250 ## $a Industrial edition.250 ## $a Red edition.If abbreviated on resource:250 ## $a Professional ed.250 ## $a Cons.68
    • 59. Publication statement (2.8)• Transcribe as it appears– Capitalization: encouraged to follow AppendixA or “take what you see”• Use 264 field in new records and forshowing changes• Only the first place and first publisher arerequired• Date required if first or last issue in hand69
    • 60. 264 field: Production, Publication, Distribution,Manufacture Statements and Copyright NoticeDate• PCC guidelines for the 264 fieldhttp://www.loc.gov/aba/pcc/documents/264-Guidelines.doc• First indicator = Sequence of statements:blank #: Not applicable/No information provided/Earliest2: Intervening3: Current/latest• Second indicator = Function of entity:0: Production; 1: Publication; 2: Distribution;3: Manufacture Statements; and4: Copyright notice date70
    • 61. Place of publication (2.8.2)• Transcribe as it appears on resource• Transcribe larger jurisdictions if theyappear on source as part of place name• Prefer to supply a place from any sourcerather than supplying:[Place of publication not identified]264 #1 $a [Fairfax, Virginia] : $b RoyRosenzweig Center for History and NewMedia, $c [2011?]-71
    • 62. Publisher name (2.8.4)• Transcribe as it appears on resource• Don’t omit hierarchies from publisher name• Prefer to supply a probable name rather thansupplying: [Publisher not identified]110 1# $a Monrovia (Calif.), $e author, $e issuingbody.245 10 $a Statement of financial transactions forthe year ...264 #1 $a Monrovia, California : $b [City ofMonrovia] 72
    • 63. Date of publication (2.8.6.5)• Record only if first or last issue is in hand• Supply an approximate publication date ifno publication date is given on first or lastissue• Omit a date of publication if the datecannot be approximated264 #1 $a [Fairfax, Virginia] : $b RoyRosenzweig Center for History and NewMedia, $c [2011?]- 73
    • 64. Copyright notice date (2.11)• RDA 2.11 and LC-PCC PS• 264 second indicator 4• Not required for serials (LC-PCC PS 2.11)– Which © date would you supply for a serial?No instructions for serials, so not required toprovide for serials74
    • 65. Summary• In describing manifestations, many stepsare familiar• Watch for subtle differences:– Omissions from beginning / end of title– Corporate name titles (with note describingtype of resource formerly bracketed as othertitle information)75
    • 66. 3b. Identifying manifestations (pt. 2)• Extent• Content type• Media type• Carrier type• Frequency• Numbering76
    • 67. 3b. Extent (3.4.1.10)• The number and type of units and/orsubunits making up a resource (MARC300 subfield $a)• Give complete and full extent for ceasedserial if known (RDA and LC-PCC PS3.4.1.10)• If the actual number is not known for aceased serial, give at least the term“volumes” or other appropriate carrier type77
    • 68. Extent• RDA Core: Provide carrier term for ceasedserials in all formats. May enter carrierterm alone. E.g.:300 ## $a volumes300 ## $a 1 online resource
    • 69. Extent• CONSER practice: Always provide carrierterm for tangible, live non-print serials• Live serials in other formats– Can optionally provide carrier terms such as“volumes” even if not ceased
    • 70. Example: Extent80
    • 71. Replacement of GMD• RDA has no provision for General MaterialDesignation (GMD)• RDA introduces instead– Content type (6.9)– Media type (3.2)– Carrier type (3.3)
    • 72. MARC 336, 337, and 338• Content type = 336• Media type = 337• Carrier type = 338• Subfields: $a term $b code $2 source• May repeat 33X field or repeat subfield $awithin a single 33X field
    • 73. Content type• The fundamental form of communication inwhich the content is expressed and the humansense through which it is intended to beperceived. (RDA 6.9.1)• Content type RDA 6.9.1.3, Table 6.1– cartographic image, computer dataset, notated music,performed music, sounds, text, three-dimensionalmoving image– If none apply, use “other”; if not certain, use“unspecified”
    • 74. Content type• RDA core element for expression• MARC 21 field 336Example:336 ## $a text $b txt $2 rdacontent
    • 75. Media type• The general type of intermediation devicerequired to view, play, run, etc., thecontent of a resource. (RDA 3.2.1.1)• Media type RDA 3.2.1.3, Table 3.1– Audio, computer, microform, microscopic,projected, stereographic, unmediated, video;– If none apply, use “other”; if not certain, use“unspecified”
    • 76. Media type• RDA core element for manifestation• MARC 21 field 337Example:337 ## $a unmediated $b n $2 rdamedia
    • 77. Carrier type• The format of the storage medium andhousing of a carrier in combination withthe type of intermediation device requiredto view, play, run, etc., the content of aresource. (RDA 3.3.1.1)• Carrier type RDA 3.3.1.3– Specific terms for audio, computer, microform,carriers, etc. carriers– If none apply, use “other”; if not certain, use“unspecified
    • 78. Carrier type• RDA core element for manifestation• MARC 21 field 338Example:338 ## $a volume $b nc $2 rdacarrier
    • 79. Carrier type terms89
    • 80. Example: print90
    • 81. Example: online91
    • 82. Example: print92
    • 83. Example: Computer discs93
    • 84. Frequency (2.1.4)• Not RDA core– RDA 2.14 and 2.20.12.4• Current frequency required for CONSER• Former frequency: not required, whencreating an original record94
    • 85. Numbering (1.7, 1.8, 2.6)• RDA 1.7: Transcription• RDA 1.8: Record numbers expressed asnumerals and words (numeric andchronological)• RDA 2.6: Basic instructions on recordingnumbering– Sources– Specific situations• Recorded in 362 1 note field95
    • 86. Numbering: sources (2.6.1.2)• Prefer source on the first/last issue thatbears the title proper• Another source within the first/last issue• Other sources specified under 2.2.4.– Accompanying material– Container– Published description– Other available source96
    • 87. Numbering: sources• RDA does not address:– Preferring a source with the most completenumbering:CCM 8.3, Prefer a source:– With the most complete presentation– With numbering that appears prominently or isstated formally
    • 88. Numbering: sources• RDA does not address:– Piecing together numbering from differentsourcesCCM 8.3:– Numeric and chronological designations maybe taken from different sources– Numeric designation may be pieced togetheronly when clear that is the intention
    • 89. Numbering: sources• Provide designation of first and/or lastissue• Transcribe elements as found– Capitalization: follow Appendix A or “takewhat you see”99
    • 90. Numbering• Substitute numerals for numbersexpressed as words• Inclusive dates and other inclusivenumbers:Source: 1967–72Record: 1967–1972• Ordinal numbers from English source:1st, 2nd, 3rd, 4th… (RDA 1.8.5)100
    • 91. Numbering• Substitute hyphen with slash for clarity– Source: 2008-2009– Record: 2008/2009• Number that is a division of a year– Source: 1-97– Record 97-1101101
    • 92. Numbering• For preliminary or trial issues of serials,"volume 0," etc., see LC-PCC PS for2.1.2.3• First issue lacks numbering, but laterissues have numbering?[Part 1]Subsequent issues numbered: Part 2, Part 3,etc.102
    • 93. Summary• Remember when to transcribe and whenyou can record with alteration to data• Several fields developed for RDA– 336 = content– 337 = media– 338 = carrier• Use the most complete numbering thatappears on source103
    • 94. Session 3c: Special cases• Microform reproductions• Facsimile print reproductions• Provider-neutral record104
    • 95. Reproductions• Follow RDA instructions (1.11)• Describe the reproduction• Include information about the original in a linkingentry field (27.1)• Some information from original in fixed fields– Leader/07: “s”– 008/06 (Type of Date)– 008/07-14 (Dates)• “Facsimiles and Reproductions”105
    • 96. Example: MicroformFF: 008/23(Form): a 008/15-17(Ctry): miu 008/07-14 (Dates): 1934, 9999245 00 $a Downbeat.264 #1 $a Ann Arbor, MI : $b NA Publishing, Inc., $c [2005]-300 ## $a microfilm reels ; $c 35 mm336 ## $a text $b txt $2 rdacontent337 ## $a microform $b h $2 rdamedia338 ## $a microfilm reel $b hd $2 rdacarrier362 1# $a Began with reel 1 (1934).776 08 $i Reproduction of (manifestation): $t Downbeat. $d Elmhurst, IL :Maher Publications, 1934- $h volumes ; 29-44 cm $w (DLC)63004684 $w (OCoLC)2260489106
    • 97. Example: Facsimile PrintFF: 008/23(Form): r 008/15-17(Ctry): iq 008/07- 14 (Dates): 1957,1963130 0# $a Hiwa (Baghdad, Iraq)̂245 10 $a Rojnamewaniy Kurdi. $p Govari hiwa, 1957-1963.̂ ̂ ̂ ̂246 1# $a Govari hiwa, 1957-1963̂ ̂264 #1 $a Hewler : $b Dezgay Cap u Biławkirdinewey Aras, $c 2010.̂ ̧300 ## $a 5 volumes : $b illustrations ; $c 24 cm362 1# $a Began with bergi 1; ceased with bergi 5.̂ ̂775 08 $i Reproduction of (manifestation): $t Hiwa (Baghdad, Iraq).̂$m Sałi 1, jimare 1 (Temuz 1957)-Sałi 6, jimare 38 (Subati 1963).̂ ̂ ̂ ̧ ̂ ̂$d Bexdad : Capxaney Temedun, [1957-1963]. $n Issue for Adarï ̧ ̂1961 called also jimare taybeti (new ruz)̂107
    • 98. Provider-neutral online serial• Follow the PCC Provider-Neutral Guidelines:http://www.loc.gov/aba/pcc/scs/documents/PCC-PN-guidelines.html• Consult CONSER Cataloging Manualmodule 31 for assistance with catalogingcomplexities• Watch for implementation of new code:040 ## … $e pn108
    • 99. Example: online serial (P-N)109
    • 100. SummaryMicroform reproductions• Follow RDA instructions (1.11)• Describe the reproductionProvider-neutral record• Follow the PCC Provider-Neutral Guidelines• Consult CONSER Cataloging Manualmodule 31• Watch for implementation of new code:040 ## … $e pn110
    • 101. 4: Identifying works andexpressions• Authorized access points representingworks• Making additions to authorized accesspoints• Authorized access points representingexpressions112
    • 102. 113113113Authorized access point for awork• RDA 5.5– 2 parts:• Creator of the work• Preferred title for the work• Does not include relationship designators
    • 103. Authorized access point for awork• A work does not necessarily have a“creator”114
    • 104. Identifying and constructing theauthorized access point for a work• RDA 6.27.1.2 - 6.27.1.8– Preferred title of the work (6.2.1 - 6.2.2)– Creator• Determine if there is a creator (19.2.1.1)• Construct authorized access point (9.19.1 forpersons), (10.10.1 for families), (11.13.1 forcorporate bodies)115
    • 105. ExercisePreferred source of information:• Title: Annual Report• Created by: Mohamed bin Zayed SpeciesConservation Fund- Hint: the resource describes the internal policiesand finances of the corporate body.- Also, assume no conflict.116
    • 106. Show Your Work• What is the preferred title (6.2.1-6.2.2)?• “Created by one person, family, orcorporate body” (6.27.1.2)• Does it fulfill any of the criteria listed in19.2.1.1.1?• If so, what is the authorized access pointfor the creator (11.13.1)?117
    • 107. SolutionAuthorized access point:• Mohamed bin Zayed SpeciesConservation Fund. Annual report.118
    • 108. Additions to the authorizedaccess point for a work• LC-PCC PS 6.27.1.9– Consider authorized access point conflictsamong all resources, not just serials• Authorized access points are identical:addition is required• Authorized access points are similar:cataloger’s judgment119
    • 109. Identical authorized accesspoint120
    • 110. Similar authorized access pointSerial in hand:245 00 $a Hogs and cows today.Serial in catalog:245 00 $a Hogs & cows today.121Result:130 0# $a Hogs and cows today (Fresno, Calif.)245 10 $a Hogs and cows today
    • 111. Additions to authorizedaccess points122
    • 112. Additions to authorizedaccess points123123
    • 113. Additions to authorizedaccess points124
    • 114. Additions to authorizedaccess points125
    • 115. Authorized access point foran expression• LC-PCC PS 6.27.3– Music resources (6.28.3)– Sacred scriptures (6.30.3)– Translations (described in the LC-PCC PS)– Language editions (described in the LC-PCC PS)126
    • 116. Authorized access point for anexpression130 0# $a Duaḥ ha-inflatsyah. $l English.245 10 $a Inflation report / $c Bank of Israel.775 08 $i Hebrew version: $t Duaḥ ha-inflatsyah $w (DLC) 00207719 $w(OCoLC)45203459127
    • 117. Summary• Authorized access point for a work:– Authorized access point for creator– Preferred title of work• Additions to authorized access point for awork– Add parenthetically to authorized access point• Authorized access point for an expression– Added to authorized access point for the work128
    • 118. 5: Related works,expressions, manifestations• Relationship Designators in MARC 21• Citing linking relationships in MARC 21• Common serial relationships130
    • 119. Relationship Designators inMARC bibliographic recordsRDA Appendix MARCI $e of 100-110 and 700-710I $j of 111 and 711J $i of 700-730J $i of 76X-78X linking entryfields131
    • 120. Relationship Designators inMARC bibliographic recordsMARC Coding Meaning780 00 “Continues”785 00 “Continued by”264 2ndindicator Function of entity132
    • 121. PCC Guidelines for theApplication of RelationshipDesignators• RD in Bibliographic Recordshttp://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Relat-Desig-Guidelines.docx• Include a relationship designator for allcreators133
    • 122. CONSER Practice forRelationship Designators inlinking entry fields• 780 00• 785 00• 776 08 $i Online version:• 775 08 $i English edition:134
    • 123. In MARC 700-730 fields• Give the form represented by NAR if RDA• If there is no NAR, give the RDA form• (follow DCM Z1 guidelines about when tomake a NAR)135
    • 124. Editing Tips for linking entry fields76X-78X• In OCLC, use “insert from cited record”• If pasting 1XX/24X text, remove subfieldcoding within:– $a [author]– $t [title]136
    • 125. Common serial relationships• Related serial works:– Supplement – whole/part– Earlier, later title• Expressions– Language expressions• Manifestations– Other formats– Change in mode of issuance– Reproductions137
    • 126. 138138Related works772 0# $t Leadership (Cape Town, South Africa)780 00 $t Australian & New Zealand apparel785 00 $t Morren Galleries journal787 08 $i Preliminary report issued as: $t English housingsurvey. Headline report787 08 $i Complemented by (work): $t English housingsurvey. Household report
    • 127. 139139Related expressions andmanifestations775 08 $i English edition: $t Azerbaijan focus776 08 $i Print version: $t Proceedings of the …Western Dairy Management Conference776 08 $i Online version: $t Bone bouquet776 08 $i Continued by online database: $t Antarcticbibliography $w (OCoLC) 52065227775 08 $i Reproduction of (manifestation): $t Hiwâ(Baghdad, Iraq)
    • 128. Relationships in note fields• 525 (supplement) - use for supplements notinput as separate records• 530 (additional physical form) - prefer 776 $i• 533 (reproduction) - use only for digitalpreservation project records with $5140
    • 129. Relationships in note fields• 534 (original version) - do not use inCONSER records• 550 (issuing body) - use to justify 7XX• 580 (linking entry complexity note) - use toexpress complex note in conjunction with7XX141
    • 130. Summary• Record relationships authorized access points,notes, & linking fields• Provide reciprocal relationship fields for serials• 700-730:– Use form from NAR– If no NAR, give RDA form• 760-787 fields:– Authorized access point of related record(minus subfield codes)– Appropriate designators (excluding 780, 785)142
    • 131. Summary• Include a relationship designator for allcreators• Apply relationship designators inaccordance with their definitions• PCC highly encourages includingrelationship designators for all accesspoints whenever it is clear what therelationship is143
    • 132. Session 6Working with Copy&When to Create a NewRecord145
    • 133. Change over Time• Using existing copy– What types of change can beaccommodated?– How to edit?• RDA & AACR2/CSR records• Pre-AACR2 successive entry records• When to consider re-describing to RDA?• Creating a new record– When? 146
    • 134. Manifestation: Types of change (1)• Carrier type (3.22.6)• Minor title changes (2.3.2.13.2)• Edition not changing scope of publication(2.5.1.6)• Publisher/distributor/manufacturer (2.8-2.11)– Publisher: Place (2.8.2.7) 148
    • 135. Manifestation: Types of change (2)• Series (2.12.1.6)• Numbering (2.6.1)• Frequency (2.14.1.4)• Editors, issuing bodies, etc. (2.4.1.10)149
    • 136. Carrier types (3.22.6)• Minor changes:– Broadsheet to volume (Media type: unmediated)– Microfiche to microfilm (Media type: microform)– CD-ROM to DVD-ROM (Media type: computer)• New record required:– CD-ROM to online (Media type: computer)150
    • 137. Exercise: Carrier typeThe last CD-ROM issue was: 1997/2001.The first DVD-ROM issue was: 1998/2002.151
    • 138. Exercise: Carrier type (2)300 ## $a computer discs ; $c 4 3/4 in.500 ## $a Issues for 1989/1992-1997/2001 on CD-ROM; issues for 1998/2002- onDVD-ROM.152
    • 139. Minor Title Changes & Variant Titles• Changes in title proper of serials:– RDA 2.3.2.12.2• Major and minor changes– RDA 2.3.2.13– LC-PCC PS general guidelines and LC-PCCPS for minor change categories• Title changes: no change in practice!153
    • 140. Minor title changes (2.3.2.13.2, 2.20.2) ,parallel (2.3.3.5), and variant titles (2.20.2.4)Coding for CONSER core:– 245 00 $a Title– 246 1# $i Issues for … have title: $a [later title]– 246 1# $i Issues for … have English title: $a[later parallel title]– 246 1# $a [variant title] $f <Nov. 2011->Example245 00 $a Géologie de la France246 1# $i Issues for 1988-1989 have title: $a Géol. Fr.246 1# $i Issues for 1994-2000 have also English title: $a Geology ofFrance and surrounding areas246 1# $a GFSA $f <1995>-1999154
    • 141. Edition statement (2.5.1.6, 2.20.4)Changes in edition statement:• No change in scope? → Record changes fromlater issues if important for identification• Example250 ## $a Property & casualty insurance edition.500 ## $a Issues for Dec. 29, 1986-Jan. 2, 1989 calledProperty & casualty/employee benefits edition; issues forJan. 9, 1989 called Property & casualty/risk & benefitsmanagement edition.155
    • 142. Publisher change (2.8, 2.20.7)• Reminder:– Existing:• 260 # # (if 260 is present, leave tag as-is) OR264 # 1 (for RDA record created after August 2011)• Add: $3 Coverage– New:• 264 2 1 (intermediate)264 3 1 (most recent)• $3 Coverage [recorded]• $a Place : $b Publisher [transcribed]• $c Date (if ceased) [transcribed] 156
    • 143. Exercise: PublisherAfter this record was created, the cataloger received some additional issues (thoughnot a complete run). Here are some changes discovered:--By the “February 1990” issue, the place of publication moved to: Tonawanda, NY--By the “February 1991” issue, the place of publication moved to: Las Vegas, NVThe Raving Lunatic Society remained the publisher throughout the life of the serial.The latest issue received was: Volume 7, issue #1 (May 15, 1993).Fixed field: 008/15-17 (Ctry): nyu157
    • 144. Exercise: Publisher change (2)Fixed field: 008/15-17 (Ctry): nvu158
    • 145. Frequency change (2.14.1.4, 2.20.12)Coding: Recorded; CONSER practice: keep all– 310 ## $a Frequency, $b coverage [current]– 321 ## $a Frequency, $b coverage [oldest]– 321 ## $a Frequency, $b coverage [next]159
    • 146. Numbering (2.6.1, 2.20.5)• Coding: Partially transcribed• Reminder: If numbering starts over withoutseries designation, supply [new series]• Options:– 362 1# $a If have first/last in range– 515 ## $a In all situationsExample 1362 1# $a Began with: No 7 (année judiciaire 1998/1999); ceased with no 13(année judiciaire 2004/2005).--------------------------------Example 2362 1# $a Began with December 1971.515 ## $a Issues for <May 2010-> called: <2nd series, volume 1, issue 5->160
    • 147. Issuing body (2.20.3.6.2)• CONSER practice: [introductory word(s)]:[information], [dates]Example550 ## $a Issued by: Bureau of Vital Statistics,1964–1977; by: Bureau of Vital Records, 1978–161
    • 148. Other considerations• CEG B4• FF Dates: If most recent issue (or known issue) isolder than 3 years:– 008/06 (Status): u– 008/11-14 (Date2): uuuu• Basis of identification: If have later issue than waspreviously been entered:588 ## $a Latest issue consulted: … .588 ## $a Latest issue consulted: … (publisher’sWeb site, viewed …). 162
    • 149. Expression-level change (7.29.2.3)• So far, ALL changes can be accommodated• Types of change common to serials:– Language– Script• Examples:546 ## $a Volumes 1-3 in French, volumes 4-7 inGerman.546 ## $a In Azerbaijani (Cyrillic), <1999->;(Latin), <2002-2003> 163
    • 150. Work-level change (Chapter6)• Parallel language titles appearing on laterissues (6.2.3.4)• Variant titles that differ significantly fromthe preferred title and might reasonably besought (6.2.3.3)• Nature of the content (7.2.1.3)164
    • 151. Hybrid: Editing AACR2/CSR Records• Documentation: Post RDA ImplementationGuidelines and Standardshttp://www.loc.gov/aba/pcc/• May follow RDA conventions to maintainAACR2/CSR records• May add (or add to) 336-338 fields• Should create RDA NARs if additional nameheadings are needed (e.g., issuing body)• Many changes can be made without re-describingserial using RDA165
    • 152. Exercise: CSR record maintenanceFF: LDR/18 (Desc) = a 008/18-19 (Freq/Regl) =q/x 008/15-17 (Ctry) = njuIssue : Volume 87, issue 4 2012Philadelphia, PA * Taylor and Francis * Published 5 times a yearWhat enhancements could/should be made to reflect this issue? 166
    • 153. Exercise: CSR record maintenance (2)FF: LDR/18 (Desc) = a 008/18-19 (Freq/Regl) =q/x 008/15-17 (Ctry) = pau167
    • 154. Editing pre-AACR2 records using RDA• Watch for: Partial title that needs to bereconsidered• Before editing:– Create DBO to reflect issue used fordescription if known, based on 362, 936, andany other data:– Remove 936• Update the record, add 588 Latest issue168
    • 155. Exercise: Pre-AACR MaintenanceIssue: Volume 35, Number 2, May 2012Published: Baltimore, Maryland, USA * The Johns Hopkins University Press169
    • 156. Exercise: Pre-AACR Maintenance170
    • 157. Pre-AACR MaintenanceIf not converting to RDA at a minimum:• Add 264 31 if needed for currentpublishing statement• Do not recode or change an existing 260• Add additional fields from latest issue– e.g. 710’s 550 note to cite issues• Add 588 “Latest issue consulted note”
    • 158. Would you re-describe to RDA if …?• CSR CONSER Record: e-Level 8 (ISSN Pre-pub)Cataloger has first issue in hand.• Pre-AACR2 Record:– 110 2# $a Society of Archivists– 245 10 $a Journal of the Society of Archivists.2011: Name of body changed to: Archives & RecordsAssociation.No change to title (oddly enough).• AACR2 CONSER Record based on: Vol. 8, no. 3245 00 $a ME insights.Cataloger has volume 1, number 1 with title:172
    • 159. When do you need a new record?W Change to authorized access point representing work 6.1.3.2.1Title proper--Major change to title proper--Major change to original title for language expression6.1.3.2.2Creator--Authorized access point for person, family, or corporate bodyused in identifying the work--Change affecting name of person, family, or corporate body usedas an addition to authorized access point for the work6.1.3.2--Work under title changes to work under creatorM Change to manifestation that cannot be accommodated indescriptionMode of issuance 1.6.2.1Media type of a serial 1.6.2.2Edition affecting scope or coverage 1.6.2.5173
    • 160. New record? New work?Situation245 00 $a Newsletter of the American HealthFoundationChange: Newsletter of the Institute for CancerPrevention174
    • 161. New record? New work?Situation: Loose-leaf publication100 1# $a Dobbs, Marian F.245 10 $a Determining child & spousalsupportChange: Serial publication245 00 $a Determining child & spousalsupport175
    • 162. New record? New work?Situation:245 00 $a Hong Kong business directory.300 ## $a CD-ROMsChange in 2007: Issued only on DVD-ROMsChange in 2009: Issued only online as pdf fileChange in 2012: Issued online as a database176
    • 163. New record? New work?Situation: Spanish-language edition130 0# $a Worldnet at a glance. $l Spanish.245 10 $a Worldnet en un vistazo.----------------------------------------------------------Change:--New English-language title is: Worldnet--Spanish-language title is: Worldnet en unvistazo 177
    • 164. RDA: Requiring a new description178
    • 165. Summary• Change within: Manifestation, Expression,and Work-level change• Hybrid-Record techniques• Re-description to RDA• Change without: Work/Expression,Manifestation179