CatalogingRDA

Wikis > zluc2014 > Schedule > CatalogingRDA

Cataloging in RDA, led by Honor

RDA is based on FRBR, which is based on the WEMI model.

  • Work is largely conceptual,

  • Expression (language or format),

  • Manifestation (traditionally edition),

  • Item.

  • Challenge with cataloging in MARC is that you’re often collapsing the Work and Expression, and with a zine, sometimes collapsing Manifestation and the item.

Toolkit:

  • Constantly being updated

  • Costs money (challenge to access)

  • You can expand or contract the table of contents, updates to history in the RDA update history, or note the date of update posted by an individual section

  • LC-PCC PS stands for Library of Congress PCC Policy Statement. Some equivalent and some different from LCRIs

  • LC-PCC PS general guidelines on transcription is a useful section to read, an overview of these policies

  • Symbols section might be an area of interest for zine catalogers.

  • Relationship designators in Appendix I-L, but most likely to use I.

  • Lot of repetition and reference between / across chapters – you will be referred around the rules to get where you’re going.

Cataloging a Zine:

  • Fixed field: often repeat elements reflected in the bibliographic record, following the same rule.

    • Encoding standard: 040, add the $e rda; Desc. : i for isbd

    • Fixed fields Illustrative content (RDA 7.15) – not core for LC-PCC PS, not required except for children’s materials, we mostly capture it anyway, most librarians do. Ill in fixed field “a”

    • Bibliography in the content section, fixed field (a “b”) (RDA 7.16) supplementary content (Cont.) area.

    • Lang: an expression level element. eng if in English

    • Ctry: when we’re reading the place named in a zine, often the place of production rather than publication, but we may use it or infer.

  • Chapter 2 in RDA: where much of the standard cataloging information lives: Title, statement of responsibility, production statement, publication statement, dates, etc. These are all very closely related to MARC fields.

  • 264 is the new field we use for statement of place (production, publication, distribution)

  • if translation of multi-language zine, would have an 041 with original and translated language codes.

  • 100 field: the creator

  • 245 field: title — Title area of chapter 2, allows more flexibility with regard to title source than AACR2 did, but does want you to cite your source for the title. If resource Consists of multiple sheets (yes, a zine) will give you the order by which you should pursue sources for the title. So with a zine, look for a title, page, if not, use a cover title and add a 500 note, ‘Title from cover’. No GMD subfield “h” in RDA. You will capitalize as in AACR2, not transcribe exactly as you see (that’s more for machine read cataloging)

  • Putting in a symbol: may interpolate a symbol that cannot be reproduced so, if an anarchy symbol appears: 245 Bibilotech [anarchy symbol] but add as well a 246 Bibliotecha  for searchable access.

  • RDA 2.4: statement of responsibility, again you have expandable menus.

  • 250 field: edition statement. if an edition, in this case happens to have one – “draft”; spell it out.

  • Place of publication: a rare case when you can’t get to some statement here, you do need one. LC-PCC PS for publication is in RDA 2.8.1.1.

    • Privately printed works – the rule is to treat a privately printed work as published.. treat zines as published works.

    • 264 _ 1 (publisher) not 264 _ 0 (production)

  • Punctuation question – is it significant to the title to use capitalization on the piece – what about the lower case i? Honor sticks with standard capitalization, but accepts records with transcription as seen on the piece.

  • 33x fields:

    • 336 content type (relates to the work)

    • 337 media and 338 carrier type refer to the manifestation/item.

    • There is controlled vocabulary for these fields within the RDA rules.

    • Zines in paper format are considered 336 unmediated (don’t require technologies to view them, like a book.

    • Carrier type is the format itself (sheet and volume are the ones you see more with a zine – if stapled, it’s a volume, if folded sheet it’s a sheet – which applies to a one-page folding zine).

    • 337 and 338 are repeatable so if you have additional media and carrier types, you can code for multiple forms. for example a comic might be considered “text” and “still image”.

    • Content type is a work level element, and relates to the extent. You can have more than one 336 as well.

 

  • 300 field: (RDA 3.4.5): extent of the text.

    • cm is a symbol, not an abbreviation, so it does not get a period at the end.

    • If a zine has page numbers, record according to what’s printed. If not paginated, you can count them and say 48 unnumbered pages, or, you can say 1 volume (unpaged).

    • If you have multiple sequences, separate sequences by commas.

  • RDA 6.27: constructing access points to relationships in works and expression..

  • Split zines treated slightly differently in terms of access points

  • In RDA, both creators and titles when acting as authorized access points, have to be disambiguated. So choosing the more unique title is the better way to go if you have to choose a title as the authorized access point.

  • Relationship designators: in Appendices, primarily using the Appendix I (between persons and works they’re creating). You might use author, illustrator.. Take a look at the LC special topics for compilations to get more information on the distinction between contributor and author. If there is no relationship that’s specific relationship to what you’re looking for, you can use “contributor” – the higher level of the relationship, at the expression level.

Final Questions

Concerns about getting to quick cataloging guidelines for folks without access to the toolkit. Jenna mentioned using Bib formats and standards as a reference: http://oclc.org/bibformats/en.html

For folks with the toolkit who are used to cataloging in MARC, the “mappings” area can be useful.