Introduction to Cataloging Integrating Resources

1. Introduction to Cataloging Integrating Resources Debra F. SpidalWashington State University, Pullman Idaho Library Association Region 2 Conference, 8 May 2009, Moscow, ID

2. Presentation Overview • Cataloging Resources • First Steps in Cataloging • Step by Step through the MARC tags • Discussion/Questions

3. Cataloging Resources • Integrating Resources: a Cataloging Manual http://www.loc.gov/catdir/pcc/bibco/irman.pdf • Cataloging Electronic Resources: OCLC-MARC Coding Guidelines http://www.oclc.org/support/documentation/worldcat/cataloging/electronicresources/ • Guidelines for Coding Electronic Resources in Leader/06 http://www.loc.gov/marc/ldr06guide.html • Guidelines for the Use of Field 856 http://www.loc.gov/marc/856guide.html • SCCTP: Integrating Resources Cataloginghttp://www.loc.gov/acq/conser/scctp/scctp-courdesc.html#IR

4. First Steps in Cataloging • Determine aspect you are cataloging, e.g. whole or part • Determine issuance • Determine primary content (MARC Type of Record and OCLC workform) • Determine iteration you have

5. Type of Issuance Finite resources Continuing resources Monographs Integrating resources Serials Multi-parts Updates remain discrete Updates do not remain discrete This slide is borrowed from the Library of Congress

6. Types of Integrating Resources • Updating loose-leaf materials • Updating databases • Updating websites • Finite • Ongoing

7. Bibliographic Level • “i” for integrating resources • “m” for monographs • “s” for serials

8. Type of Record • Type “a”- Online texts even with search engines- Aggregator services- Portal pages of text links to other resources- Online catalogs- Numeric data in tabular form • Type “m”- Computer software- Numeric data- Computer-oriented multimedia- Online systems or services

9. Type of Record – Cont. • Type “e” for Cartographic content • Type “i” or “j” for Sound recordings • Type “g” for Video recordings Use “m” when in doubt.

10. 008 • Record Type = “a” or other as appropriate • Bib Lvl = “i” • S/L = “2” • Form = “s” • Srce = “d” • Place of publicationfrom 260 $a

11. 008 Cont. • Type of date“c” = currently published“d” = ceased“u” = unknown • Date 1Give date from 260 $c or 362 • Date 29999 if active or date from 260 or 362 if ceased

12. 006 Additional Material Characteristics • Continuing resource/serialalways add 006 with form “m”

13. 007 Physical Description • Code at least the first two positions for electronic resources007 c $b r $d m $e n $f u

14. 008 for City of Moscow website CR workform Type: a ELvl: k Srce: d GPub: Ctrl: Lang: eng BLvl: i Form: s Conf: 0 Freq: u MRec: Ctry: idu S/L: 2 Orig: s EntW: Regl: x Alph: Desc: a SrTp: w Cont: DtSt: c Dates:200u,9999 006 ER: Form: m File: d 007 c $b r $d m $e n

15. Author • Very unusual to have Author main entry; sometimes corporate author main entry for government websites 110 1_ Moscow (Idaho) 110 2_ Library of Congress

16. Title $h [GMD] 245 00 City of Moscow $h [electronic resource] Use 246 for variant titles 246 1_ $i Title in HTML header: $a City of Moscow, Idaho home page

17. Statement of Responsibility • Optional under CONSER Standard Record • Give if explicit on website • Use notes for ambiguous information 245 00 / $c City of Moscow 245 00 / $c by Bill Arnett

18. Edition • Give if present. May be Version or Update statement 250 Version 2009.1 250 Release no. 12

19. Publication, Distribution, Etc. • The whole website is the Chief source 260 Moscow, Idaho : $b City of Moscow. Generally do not include date here unless you know you have the first or last iteration.

20. Physical Description • Do not use for websites

21. Current Publication Frequency • Give if known310 Updated daily310 Updated monthly310 Updated continuously • Should match fixed fields

22. Dates of Publication • Record beginning and ending dates. 362 1_ Began ca. 2000.362 1_ Began between 1995 and 1999. Do not use both 362 and 260 $c, one or the other.

23. Mode of Access Note • Use only for access methods other than World Wide Web 538 Mode of Access: Gopher

24. System Requirements • Give system requirements only for non-standard software, not for free downloads e.g. Adobe Reader 538 System requirements: Microsoft Word 2000 or later

25. Source of Title Proper • Combine with latest issue consulted note 500 Title from home page (viewed Apr. 22, 2009).

26. Summary Note • Include brief summary of contents520 __ City of Moscow, Idaho home page provides access to local event, city employment opportunities, city government information and contacts.

27. Added Entries • Add as needed to provide controlled access point 710 2_ Smithsonian Institution.

28. 856 Field(s) 856 40 $u http://www.moscow.id.us/ Do not include public notes in master records.

29. Subject Headings and Classification • Provide general topical or geographic headings as appropriate • Use form headings with caution; read scope notes carefully • Classification provides an additional access point for browsing the OPAC

30. Title Changes • Record new title in 245; old title in 247 245 00 Moscow, Idaho live $h [electronic resource]. 247 10 City of Moscow $f <Apr. 22, 2007> 500 __ Title from home page (viewed on June 22, 2009). Add additional notes if explanation is needed. Do not create new records for title changes.

31. Copy Cataloging & Major Changes • Searching for Copy • When to create a new record • When to go back to the books

32. Something to Consider • Just because it is on the World Wide Web does not mean it is an Integrating Resource • Just because it is an Integrating Resource does not mean you use the Continuing Resources Workform

33. Discussion/Questions?