too dynamic to describe?

66
1 Too Dynamic to Describe? NASIG Annual Conference June 2004, Milwaukee, Wis. Bonnie Parks, Oregon State Univ. Jian Wang, Portland State Univ.

Upload: piera

Post on 11-Jan-2016

24 views

Category:

Documents


0 download

DESCRIPTION

Too Dynamic to Describe?. NASIG Annual Conference June 2004, Milwaukee, Wis. Bonnie Parks, Oregon State Univ. Jian Wang, Portland State Univ. References. Anglo - American Cataloging Rules, Second Edition, 2002 Revision (AACR2) - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Too Dynamic to Describe?

1

Too Dynamic to Describe?

NASIG Annual Conference

June 2004, Milwaukee, Wis.

Bonnie Parks, Oregon State Univ.

Jian Wang, Portland State Univ.

Page 2: Too Dynamic to Describe?

2

References

Anglo - American Cataloging Rules, Second Edition, 2002 Revision (AACR2)

SCCTP Integrating Resources Cataloging Workshop prepared by Steve Miller

OCLC Technical Bulletin 247. Coding Practice for Integrating Resources: www.oclc.org/technicalbulletins/247/#1

CONSER Cataloging Manual (CCM) CONSER Editing Guide (CEG)

Page 3: Too Dynamic to Describe?

3

Issues to Contemplate

What is an integrating resource (IR)? Why/who catalog IRs? New concepts, rules, and principles in AACR2,

2002 Revision What are the challenges in cataloging IRs?

Page 4: Too Dynamic to Describe?

4

A New Concept

What is an Integrating Resource?

A bibliographic resource that is added to or changed by means of updates that do not remain discrete and are integrated into the whole. An integrating resource may be finite or continuing.

Examples include updating databases, updating loose-leafs, and updating websites.

Page 5: Too Dynamic to Describe?

5

Why Catalog Integrating Resources?

Proliferation of electronic materials Changing collections Provides one stop access Inclusive and flexible catalog New standards and rules

Page 6: Too Dynamic to Describe?

6

Who Catalogs Integrating Resources?

Serials catalogers Electronic resource catalogers Monographic catalogers Integrating resources catalogers Metadata catalogers

Page 7: Too Dynamic to Describe?

7

AACR2 Revisions – New Concepts

Chapter 9: Electronic Resources Chapter 12: Continuing Resources

– Serials– Integrating resources

Chapter 21: Choice of Access Points– Rules for title changes

Page 8: Too Dynamic to Describe?

8

Changes in Chapter 9

Old title: Computer Files New title: Electronic Resources Scope: covers all electronic resources,

including direct (local) or remote (networked) New GMD: [electronic resource] Chief Source Information: the resource itself

instead of the title screen

Page 9: Too Dynamic to Describe?

9

Changes in Chapter 12

Old title: Serials New title: Continuing Resources (serials and

integrating resources) New concept: Integrating Resources (used for

dynamic electronic resources) New issuance: Integrating (in addition to

monograph and serial)

Page 10: Too Dynamic to Describe?

10

Changes in Chapter 21

Integrating resources. If a change occurs in the title proper of the same integrating resource, do not make a new entry. Instead, replace the title proper with the new title and change the description to reflect the latest information. In general, give the earlier title in a note (see 12.7B4.2).

Page 11: Too Dynamic to Describe?

11

Highlights for Cataloging IRs

LCRI 1.0 AACR2 rules Bibliographic formats and standards Cataloging entry conventions MARC 21 coding changes 006 coding sheet for serials

Page 12: Too Dynamic to Describe?

12

How do I catalog this? Is this an integrating resource?

Does it fit the definition of an IR?– does not remain discrete– integrated into the whole– Is this an updating database/web site?

Refer to LCRI 1.0A for guidance:http://www.loc.gov/catdir/cpso/lcri1_0.html

Page 13: Too Dynamic to Describe?

13

AACR2 Rules

Strategy

Use rules in Chapter 12 in conjunction with other chapters in cataloging integrating resources:

Example

Use chapters 3, 9 & 12 for cataloging updating cartographic Web sites

Page 14: Too Dynamic to Describe?

14

MARC Codes

Bibliographic Formats and Standards has been updated to include OCLC Phase 1 changes:www.oclc.org/bibformats/en– Changes to fixed field elements Freq, S/L, SrTp– Scope of some variable fields redefined to include

both continuing & integrating resources: 022, 222, 247/547, 310, 321, 362, and some notes

Page 15: Too Dynamic to Describe?

15

Fixed Field: S/L (Entry Convention)

• Use code 2 to indicate that the record was formulated using the revised rules for integrated entry– The record is cataloged under latest title or issuing

body– Use for continuing & integrating resources that do

not retain their earlier titles.

Page 16: Too Dynamic to Describe?

16

What’s the difference between Integrating Resources and Serials?

Integrating resources: – Description based on the latest iteration– Use of integrated entry cataloging

Serials:– Description based on the earliest issue– Use of successive entry cataloging

Page 17: Too Dynamic to Describe?

17

MARC Tagging

• Before code “i” implementation:

Code IR as monographs: Bib level “m”

Add Serials 006 for integrating resources

• After code “i” implementation:

Code IR as integrating resources: Bib level “i”

Most will have Type of Record “a” and Serials 008

Page 18: Too Dynamic to Describe?

18

New MARC 21Tags

022– ISSN247/547– Change in title proper310/321– Frequency362 1– Beginning/ending date of publication550 – Issuing body note580, 76X-78X– Relationships with other resources

Page 19: Too Dynamic to Describe?

19

Case Study # 1

How do I select the Type of Record and Type of Computer File codes that best characterize the content of the resource?

Page 20: Too Dynamic to Describe?

20

Type of Record (Leader/06)

OCLC Fixed Field “Type”Examples:

– Type “a” (document)– Type “e” (map)– Type “i” (nonmusical sound recording)– Type “m” (computer game)

Page 21: Too Dynamic to Describe?

21

Type of Record (Leader/06), 2

Type “a” vs. Type “m”– Use Type “a” Language Material

for textual electronic resources– Use Type “m” Computer File for

non- textual electronic materials

Page 22: Too Dynamic to Describe?

22

Is this web site Type “a” or “m”?

Type “a”

Page 23: Too Dynamic to Describe?

23

Is this web site Type “a” or “m”?

Type “m”

Page 24: Too Dynamic to Describe?

24

In Case of Doubt?

Code the resource “m” (computer file)

“Guidelines for Coding Electronic Resource in Leader/06/ Library of Congress”

Page 25: Too Dynamic to Describe?

25

Field 006/09 (Computer files/Electronic resources)

Required by OCLC for text-based electronic resources.Example:

Type = aBLvl = m (“i” in the future)006 (Computer files)006 (Continuing resources)

Page 26: Too Dynamic to Describe?

26

Field 006/09 & 008/26 (Type of Computer File Codes)

a = Numeric datab = Computer programd = Documente = Bibliographic datah = Soundi = Interactive multimediaj = Online system or servicem = Combination

Page 27: Too Dynamic to Describe?

27

am

For computer files/electronic resources

Page 28: Too Dynamic to Describe?

28

006 for Continuing resourcesFreq: _ Regl: x ISSN: SrTp: d Orig: s Form: s EntW: Cont: GPub: Conf: 0 Alph: a S/L: 2

006 for Computer filesAudn: File: e GPub:

Page 29: Too Dynamic to Describe?

29

Type of Record & Type of Computer File?

jm

j

Page 30: Too Dynamic to Describe?

30

Page 31: Too Dynamic to Describe?

31

am

Type of Record & Type of Computer File?

Page 32: Too Dynamic to Describe?

32

Additional Guidelines

Guidelines for Coding Electronic Resource in Leader/06/ Library of Congress:

– http://lcweb.loc.gov/marc/ldr06guide.html

Cataloging Electronic Resources: OCLC-MARC Coding Guidelines:

– http://www.oclc.org/oclc/cataloging/type.htm

Use of Fixed Fields 006/007/008 and Leader Codes in CONSER Records:

– http://lcweb.loc.gov/acq/conser/ffuse.html

Page 33: Too Dynamic to Describe?

33

Case Study #2

What do I consider the best choice for chief source of information and title proper?

Page 34: Too Dynamic to Describe?

34

Chief Source of Information

What is the chief source of information?– the resource itself (AACR2R 9.0B1)

How to determine the best choice for chief source?– the source that provides the most

complete information

Page 35: Too Dynamic to Describe?

35

Title Proper – How do you transcribe title (245) and variant forms of title (246)?

Do not record introductory words not intended to be part of the title, such as “Welcome to” (1.1B1).

The title may be noted and treated as a variant title (1.B1 and 1.7B4).

Page 36: Too Dynamic to Describe?

36

Title Proper?

Three options for title proper:Plants databaseWelcome to plants national databasePlants national database

Page 37: Too Dynamic to Describe?

37

Which is the best choice for title proper for this web site?

Four options for title proper:AgeLine database AgeLineAARP AgeLineAARP

Page 38: Too Dynamic to Describe?

38

Other Title Information

AACR212.1E1: Transcribe other title information if considered to be important for integrating resources.

Page 39: Too Dynamic to Describe?

39

Would you transcribe other title info. after the title proper?

245 00 MedlinePlus $h [electronic resource].OR

245 00 MedlinePlus $h [electronic resource] : $b trusted health information for you.

Which would you choose?

Page 40: Too Dynamic to Describe?

40

Additional Guidelines

AACR2 Chapter 9 and 12 rules for chief source of information, Area 1 (title and statement of responsibility)

Page 41: Too Dynamic to Describe?

41

Case Study # 3

Where do I locate information on publisher, place, and dates of publication?

Page 42: Too Dynamic to Describe?

42

Publisher vs. Host?

s

Page 43: Too Dynamic to Describe?

43

Where is the Place of Publication?

Page 44: Too Dynamic to Describe?

44

Dates of Publication?

s

Page 45: Too Dynamic to Describe?

45

260 [Atlanta, Ga.?] : $b American Cancer Society

362 1# Probably began after 1997.

Page 46: Too Dynamic to Describe?

46

Additional Guidelines

AACR2 Chapter 9 and 12 rules for chief source of information, Area 4 (publication, etc.)

Page 47: Too Dynamic to Describe?

47

Case Study # 4

The title has changed, now what do I do?

Page 48: Too Dynamic to Describe?

48

When a Data Element Changes (LCRI 12.7A2)

Give exact information about the timing of the change if it is available

If exact information is not available, use information that already exists in the record. – Use the date from the “viewed on” note (500 field)

and put the date in angle brackets: <Mar, 24, 2004>

Page 49: Too Dynamic to Describe?

49

Changes to title proper

If changes occur in the title proper in a later iteration:– Do not create a new record– Modify the title and statement of responsibility area

(245 $a/n/p/c) to reflect the current iteration.– Data elements of previous iterations are recorded in

notes if considered important– If needed for access, make added entry for earlier

title proper (247/547)

Page 50: Too Dynamic to Describe?

50

MARC Tagging for Change in Title Proper

247 Former title proper– Generates a title added entry

547 Former title proper complexity note– Used for complex situations, or when a title added

entry is not needed– LCRI 12.7B42 says to give a separate 547 “title

history” note in addition to the 247 field if the 247 does not provide adequate explanation.

Page 51: Too Dynamic to Describe?

51

Reflecting Changes in the Title Proper

Page 52: Too Dynamic to Describe?

52

Page 53: Too Dynamic to Describe?

53

Page 54: Too Dynamic to Describe?

54

http://www.archive.org/

Page 55: Too Dynamic to Describe?

55

MARC Record Example

245 00 CQ electronic library $h [electronic resource].

247 10 CQ library $f <Oct. 25, 1999>

260 Washington, D.C. : $b CQ Press

500 Title from homepage (viewed on May 21, 2004).

Page 56: Too Dynamic to Describe?

56

Page 57: Too Dynamic to Describe?

57

MARC Coding

245 04 The world Shakespeare bibliography online $h [electronic resource]

246 1 $i Also called: $a WSB online

247 10 World Shakespeare bibliography $f <Oct. 11, 2001>

310 Updated monthly, $f <Feb. 27, 2004>

321 Updated quarterly, $f <June 15, 2001>

ER 006 [m e ]

CR 006 [suu d 0 2] (Integrating Entry)

Page 58: Too Dynamic to Describe?

58

Case Study # 5

How do I use field 547 to reflect a change in title?

Page 59: Too Dynamic to Describe?

59

Using 247/547

245 00 BMC biochemistry database $h [electronic resource].

247 11 BMC biochemistry and structural biology database $f<Dec. 10, 2002>

500 Title from home page (viewed on Mar. 4, 2004)

547 Originally titled: BMC biochemistry and structural biology database. Original title was split into: BMC biochemistry database, and: BMC structural biology database. A new web site was created for BMC structural biology database and all articles were reformatted with the later titles.

245 00 BMC biochemistry and structural biology database $h [electronic resource]

500 Title from home page (viewed on Dec. 10, 2002)

Earlier record Later record

Page 60: Too Dynamic to Describe?

60

Case Study #6Representing bibliographic

relationships (linking)

Page 61: Too Dynamic to Describe?

61

Linking between records

You can link – IR IR – IR serial– IR monograph

– But monograph to monograph

Page 62: Too Dynamic to Describe?

62

Example:Philosopher’s Index (IR version)

006 [m e ] 006 [sqr d 0 2] 007 c $b r 001 42827211 130 0 Philosopher's index (Online) 245 10 Philosopher's index $h [electronic resource]. 310 Updated quarterly 776 08 $i Issued also in print format: $t Philosopher's

index $x 0031-7993 $w (DLC)sf 85003080 $w (OCoLC)4187784

Page 63: Too Dynamic to Describe?

63

Philosopher’s Index (Print serial)

001 4187784 245 04 The Philosopher's index. 300 v. ; $c 24-28 cm. 776 1# $t Philosopher's index (Online) $w

(OCoLC)42827211

Page 64: Too Dynamic to Describe?

64

Summary

IR – dynamic in nature Basic principles for cataloging IRs

– Focus on whole publication – Focus on identification

Use cataloger’s judgment to determine the best solutions

Page 65: Too Dynamic to Describe?

65

Group Discussion

What other issues/challenges have you encountered in cataloging electronic integrating resources?

Page 66: Too Dynamic to Describe?

66

Thank You!

Slides for this presentation may be found at :

http://www.bonster.com/NASIG

[email protected]

[email protected]