This document provides an overview of a preconference on applying RDA and serials in both theoretical and practical ways. It discusses key concepts like FRBR and FRAD models, the transition from AACR2 to RDA, and how to identify serial attributes and relationships according to RDA. The preconference covers RDA implementation scenarios, exercises to practice concepts, and a webliography of additional resources.
Visit to a blind student's school🧑🦯🧑🦯(community medicine)
RDA and Serials: Theoretical and Practical Applications
1. RDA and Serials: Theoretical
and Practical Applications
Implementation scenarios
Exercises & Answers
Attributes relationships worksheets Judith A. Kuhagen
Webliography JSC Secretary
NASIG Preconference
Nashville – June 6-7, 2012
2. Theoretical and practical ????
• Theoretical:
– How did we get from AACR2 to RDA?
– What are the concepts and principles of RDA?
• Practical:
– Where do I find what I need in RDA?
– What elements do I select to identify serial
resources and how do I transcribe/record them?
– How do I identify serial relationships?
Kuhagen (NASIG June 2012) 2
3. Additional topics inserted
here and there
• Other resources available in the RDA Toolkit
• RDA changes in the April 2012 update of the
RDA Toolkit affecting serials
• Current and upcoming JSC activities
• Related initiatives and activities
• Availability of other training materials and
resources of information
Kuhagen (NASIG June 2012) 3
4. 1997 international conference - Toronto
• Joint Steering Committee for Revision of AACR
(JSC) realized the need to revise AACR2:
– Increasing complexity of content/carriers of
resources being acquired
– More and more digital resources being acquired
– Internet: cataloging data no longer “local”
– Cataloging data no longer created just in libraries
– FRBR conceptual model draft reported published in
1996
– Internationalization more and more important
Kuhagen (NASIG June 2012) 4
5. Initial Toronto conference outcomes
related to serials
• Harmonization efforts by JSC with ISBD-S and
ISSN communities (resumed in late 2011)
• Publication of revised AACR2 chapter 12 for
continuing resources in 2002
– More complete coverage for serial situations
– Addition of integrating resources (both finite and
ongoing)
Kuhagen (NASIG June 2012) 5
6. 2005 AACR3 draft’s problems
• Needed to move closer to the Functional
Requirements of Bibliographic Records (FRBR)
conceptual model
• Needed to be based on principles (not “case law”
of specific situations)
• Needed the structure of an element set
• So, JSC started over: AACR3 became RDA with
conceptual models, principles, and element set
(latter on Tools tab in the RDA Toolkit) with more
of an international focus
Kuhagen (NASIG June 2012) 6
7. IFLA’s international models and
principles – worldwide input
• Functional Requirements for Bibliographic
Records (FRBR; 1998)
• Functional Requirements for Authority Data
(FRAD; 2009)
• Statement of International Cataloguing
Principles (ICP; 2009)
Kuhagen (NASIG June 2012) 7
8. IFLA Statement of International
Cataloguing Principles (ICP)
• Update of the 1961 IFLA Statement of Principles
– aka Paris Principles (its focus = textual
resources, choice and form of entry; Europe
and North America)
• 5 regional meetings of cataloging experts
(2003-2007): Frankfurt, Buenos
Aires, Cairo, Seoul, Pretoria
– All resources: description and all forms of access
– Bibliographic and authority data (includes subjects
but no subject thesauri principles yet)
Kuhagen (NASIG June 2012) 8
9. User tasks important in IFLA models
and principles
FRBR: FRAD:
• Find • Find
• Identify • Identify
• Select • Contextualize
• Obtain • Justify
• ICP’s highest principle = “convenience of
the user”
Kuhagen (NASIG June 2012) 9
10. FRBR published 1998
• Functional Requirements of Bibliographic Records
(perhaps … Data in future)
• Conceptual model – not a cataloging code
– E.g. won’t say when to create a new serial description
• A few differences between FRBR and RDA
• IFLA Cataloguing Section FRBR Review Group
oversees its revision
– E.g., the JSC is asking the Review Group to reconsider
if frequency is assigned to the correct entity
Kuhagen (NASIG June 2012) 10
11. FRAD published 2009
• Functional Requirements of Authority Data
(had been FRAR: … Records)
• Also a conceptual model
• Added “family” to the Group 2 entities
• Some differences between FRAD and RDA
• Eventually will be merged with FRBR
• Name authority data not addressed in AACR2
Kuhagen (NASIG June 2012) 11
12. FRSAD published 2010
• Functional Requirements for Subject Authority Data
• Also a conceptual model
• RDA chapters 12-16 for subject entities and
chapters 33-37 for subject relationships still
placeholders – JSC discussing scope of chapters
• Eventually will be merged with FRBR
• Subject authority data not in AACR2
Kuhagen (NASIG June 2012) 12
13. Implementation scenarios
• RDA doesn’t prescribe an implementation
scenario
• Goal: well-labeled metadata that can be
searched, indexed, displayed, etc., as needed
by users in a linked-data environment
• RDA elements and vocabularies at
http://metadataregistry.org/
Kuhagen (NASIG June 2012) 13
14. 3 possible implementation scenarios
• Scenario 3: ‘Flat file’ database structure (no
links, e.g., card catalog)
• Scenario 2: Linked bibliographic and authority
records (many ILSs now)
• Scenario 1: Relational/object-oriented
database structure – goal for future!
• Separate LC handout; also available at:
http://www.rda-jsc.org/working2.html#ed-2
Kuhagen (NASIG June 2012) 14
15. Encoding schema for RDA?
• RDA doesn’t prescribe an encoding schema
• Yes, most will encode RDA content in MARC 21
formats for some time
– Appendices D and E in RDA
– RDA/MARC mappings on Tools tab in RDA Toolkit
– Examples on Tools tab in RDA Toolkit, on LC’s RDA
preparation site, and on CLW site
Kuhagen (NASIG June 2012) 15
16. LC’s Bibliographic Framework
Transition Initiative
• Website: http://www.loc.gov/marc/transition/
• To move from current MARC framework to one
for a “linked data” world
• May 22 announcement on the site about next
step: contractor for model or models
Kuhagen (NASIG June 2012) 16
17. Until we reach that future
• Many parts of current RDA records will “look
the same” as the same parts in AACR2 records
– In transition mode: important that we’re adding
more labeled attributes and relationships in our
bibliographic and authority data for users now and
in the future
• Opportunities for learning more about linked
data in listing of resources
Kuhagen (NASIG June 2012) 17
18. Need to understand FRBR/FRAD?
• Yes, do need to understand FRBR concepts of
entities and relationships to understand:
– Practical: which RDA chapter for which concept
– Theoretical: discussions about future of
bibliographic control, especially “linked data”
– “FR” namespaces published:
http://iflastandards.info/ns/fr/
• Helpful free tool = RIMMF (RDA in Many
Metadata Formats):
http://www.marcofquality.com/soft/softindex.html
Kuhagen (NASIG June 2012) 18
19. RIMFF
• Developed by Deborah and Richard Fritz
– “as a visualization tool for catalogers, to help them to
get used to thinking RDA, instead of thinking
AACR/MARC”
– “as a cataloging training tool, to help educators teach
RDA thinking”
– not as a cataloging tool – vendors need to develop
cataloging interfaces; catalogers not creating four
separate records for
work, expression, manifestation, and item (system
should do that!)
Kuhagen (NASIG June 2012) 19
20. FRBR/FRAD entities
• Group 1
– Work, Expression, Manifestation, Item (“WEMI”)
• Group 2
– Person, Family, Corporate body
• Group 3
– Group 1 & 2 entities + Concept, Object, Event, and
Place
Kuhagen (NASIG June 2012) 20
21. Entities: attributes & relationships
• Attributes: characteristics of the entities
– What identifies (or describes) the entities
– Called “elements” in RDA
• Relationships
– To which entities (some both directions)
– What types of relationships
Kuhagen (NASIG June 2012) 21
22. RDA Structure
• General introduction (ch. 0)
• Identifying elements (entities and their
attributes)
– Ch. 1-4: manifestation and item
– Ch. 5-7: work and expression
– Ch. 8-11: person, family, corporate body
– Ch. 16: place [now in RDA only as a jurisdiction –
really a Group 3 entity]
Kuhagen (NASIG June 2012) 22
23. RDA Structure
• Identifying relationships:
– Ch. 17: primary relationships
– Ch. 18-22: Group 1 with Group 2
– Ch. 24-28: within Group 1
– Ch. 29-32: within Group 2
• Appendices (I, J, and K = relationships)
• Glossary; Index
Kuhagen (NASIG June 2012) 23
24. Ch. 17: primary relationships
• Work expression manifestation
item of the same resource
• Not appropriate for current implementation
scenario where elements of all four entities in
a single MARC bibliographic record
• JSC will be adding an introduction to the
chapter explaining context for use of ch. 17
Kuhagen (NASIG June 2012) 24
25. MARC bibl. record & FRBR Group 1
1XX/240 = work, expression [& manifestation]
245-260, 490 = manifestation
300 = expression, manifestation
other 3XX = work, expression, manifestation
5XX = work, expression, manifestation
700-730 = related work, related expression
760-787 = related work, related expression,
related manifestation
8XX = work, expression [& manifestation]
ALCTS RDA 201: Serials (2011) 25
26. FRBR entities’ relationships
• With others in different groups (ch. 18-22)
– Creator to work; issuing body to work, etc.
– Translator to expression, etc.
– Publisher to manifestation; owner to item, etc.
• With others in same group (ch. 24-32)
– Work and work (e.g., earlier/later serials; merger)
– Expression and expression (e.g., translation)
– Corporate body and another body (e.g., earlier/later)
Kuhagen (NASIG June 2012) 26
27. FRBR/FRAD Group 1 Vocabulary
• “Book”
– Door prop
(item)
– “publication”
any copy at
bookstore
(manifestation)
27
28. FRBR/FRAD Group 1 Vocabulary
• “Book”
– Who translated?
(expression)
– Who wrote?
(work)
28
29. Serial WEMI
Work (Idea of
annual report)
Expression (to be Expression (to be
expressed In translated in
English text) French text)
*becomes “physical”
as manifestation]
Manifestation Manifestation Manifestation
(published by ABC (published by JKL (published by QRS
in paper) as CD-ROM) in paper)
Item (v. 1 in your Item (v. 1 access in Item (v. 1 in your
library) your library) library)
Kuhagen (NASIG June 2012) 29
30. Some serials = aggregate works
• An article embodies a work
• An issue has multiple articles
• A volume has multiple issues
• A serial resource has multiple volumes
• In FRBR, work is “recursive” (can repeat)
• Aggregates = compilations (broader scope in
RDA than in AACR2)
Kuhagen (NASIG June 2012) 30
31. EXERCISE: Identify Group 1 entities
• Page 1 of Exercise packet
• Indicate on the blank line which Group 1
entity (work, expression, manifestation, or
item) is illustrated
Kuhagen (NASIG June 2012) 31
32. Focus for remainder of preconference
• Identifying attributes of serial resources (FRBR
“attributes” are RDA “elements”)
• Identifying relationships of serial resources
• Some authority data elements for serials
(including for series authority records)
Kuhagen (NASIG June 2012) 32
33. Not focus of preconference
• Not MARC fields for RDA elements and not
MARC bibliographic records
• Not element-by-element discussion of RDA
instructions
– Many presentations for your use/modification at
these and other sites (including NASIG 2011
preconference at 2nd link below):
http://www.loc.gov/aba/rda/
http://www.rda-jsc.org/rdapresentations.html
• Not RDA instructions for Group 2 entities
• Not CONSER Standard Record
Kuhagen (NASIG June 2012) 33
34. RDA “core” elements
• Some always required and some only in certain
situations (blue text at beginning of element in
the RDA text)
• Identified as part of worldwide review of FRBR
• Program (e.g., CONSER) or library policy decisions
or cataloger judgment for additional elements
• Non-core are called “enhanced” in the RDA
Element Set in the RDA Toolkit
Kuhagen (NASIG June 2012) 34
35. Serial pre-cataloging decisions
• If online resource, separate description or
provider-neutral record or link on record for
print?
• Applying CONSER Standard Record guidelines?
Adding more elements?
• If covered by existing AACR2 record, adding
information or converting record to RDA?
– OCLC and SkyRIver policies, CONSER guidelines
• Deciding if covered by existing record or if
creating a new description
Kuhagen (NASIG June 2012) 35
36. New description needed (RDA 1.6.2)
• Change in mode of issuance
• Change in media type
• Major change in title proper
• Change in responsibility requiring change
in identification of the serial work
• Change in edition statement indicating
significant change in subject or scope
Kuhagen (NASIG June 2012) 36
37. Change in identifying the serial work
• Change in responsibility for the work
(6.1.3.2.1):
– Change in authorized access point for
person, family, or corporate body used in
identifying the work
– Change affecting name of
person, family, or corporate body used as
an addition to authorized access point for
the work
• Major change in title proper (6.1.3.2.2)
Kuhagen (NASIG June 2012) 37
38. New descriptions but not new works?
• “Gap” in RDA because no instructions yet for
authorized access points for manifestations (RDA
Editor said mainly for subject relationships)
• But need them for these 1.6.2 categories:
– Change in mode of issuance
– Change in media type
– Change in edition statement … significant …
• Follow LCPS 6.27.1.9 to break conflicts
Kuhagen (NASIG June 2012) 38
39. EXERCISE: New description/new work
• Pages 2-3 in Exercise packet
• Indicate if the condition following the arrow
will result in:
– a new description
– if a new description, also a new work
Kuhagen (NASIG June 2012) 39
40. User tasks part of RDA instructions
• “… if considered important for identification or
access”
• “… if considered important for identification or
selection”
• “… if considered important for access”
• “… to justify the … form of the access point”
Kuhagen (NASIG June 2012) 40
41. Attributes: manifestations and items
• Chapter 1: General guidelines …
• Chapter 2: Identifying manifestations and items
(mostly self-reporting attributes)
• Chapter 3: Describing carriers *user task “select”+
• Chapter 4: Providing acquisition and access
information *user task “obtain”+
Kuhagen (NASIG June 2012) 41
42. Attributes: works and expressions
• Chapter 5: General guidelines …
• Chapter 6: Identifying works and expressions
– 6.2-6.26: attributes (general; special categories)
– 6.27-6.31: authorized and variant access points *
• Chapter 7: Describing content
– 7.2-7.9: works
– 7.10-7.29: expressions
Kuhagen (NASIG June 2012) 42
43. * from previous slide
• Ch. 19 = Persons, Families, and Corporate
Bodies Associated with a Work – a relationship
chapter
• But need RDA 19.2 (Creator) when constructing
authorized access point for a work
– In “linked data” future, we won’t need to construct
an authorized access point – we’ll just establish the
relationship
Kuhagen (NASIG June 2012) 43
44. Serial manifestations/items
• ICP principle of representation = information
transcribed as found on the resource
– Sources expanded in RDA to entire resource
(exception is “other title information” – must
be on same source as title proper)
– Indicate if beyond resource (e.g., enclose in
square brackets)
• Other information may be manipulated when
recorded by the cataloger – presented by the
resource or from another source
Kuhagen (NASIG June 2012) 44
45. Transcribed serial manifestation
“identifying” information – ch. 2
• Title proper & parallel title proper
• Other title information & parallel o.t.i.
• Statement of responsibility & parallel s.o.r.
• Edition information
• Numbering information
• Place of publisher, distributor, manufacturer
• Name of publisher, distributor, manufacturer
• Series information other than ISSN
Kuhagen (NASIG June 2012) 45
46. Reminders about transcribed elements
• Not abbreviating full forms of found information
• Generally, not converting one form of found
information to another form
• Generally, not omitting information (e.g., part of a
publisher name, responsible bodies beyond three in
a statement of responsibility)
– Except omit numbering from title proper or parallel
title (use mark of omission wherever in title)
• Some alternatives allow some conversions and
some omissions for some elements
Kuhagen (NASIG June 2012) 46
47. Recorded serial manifestation
“identifying” information – ch. 2
• Date of publication, distribution, manufacture
• Copyright date
• Mode of issuance
• Frequency
• Identifier of the manifestation (e.g., ISSN usually)
• Key title
• Notes about element (e.g., source of title)
• Issue or part used as basis of description
• Notes about changes over time
Kuhagen (NASIG June 2012) 47
48. Recorded serial manifestation
“identifying” information – ch. 3
• Common carrier characteristics
– Extent
– Dimensions
– Carrier type
– Media type
– Characteristics for other than volumes as carriers
(e.g., CD-ROMs, digitized files, videotapes)
• Notes about changes over time
Kuhagen (NASIG June 2012) 48
49. Recorded serial item information
– ch. 2 and 3
• Identifier for the item
• Item-specific carrier characteristics, e.g.
– Imperfections in an issue or volume
– A library’s holdings of a serial resource
• Notes on extent of item or dimensions of item
apply more to monographs
Kuhagen (NASIG June 2012) 49
50. Reminders about carrier
characteristics (ch. 3)
• Carrier type and Media type have controlled
vocabularies
– If more than one applies, pick main one or give all
– If none in list apply, use “other”
– If cannot determine, use “unspecified”
• Extent for all resources, including online
resources
Kuhagen (NASIG June 2012) 50
51. Acquisition and access information for
manifestations and items – ch. 4
• Terms of availability
• Restrictions on access/use
• Uniform Resource Locator (URL) for remote
access resources
• Some may be item-specific
Kuhagen (NASIG June 2012) 51
52. Elements for identifying works – ch. 6
• Title of the work: preferred & variant
• Form of the work
• Date of the work
• Place of origin of the work
• Other distinguishing characteristic of the work
• Identifier for the work
• Creator not in ch. 6 – it’s a relationship
Kuhagen (NASIG June 2012) 52
53. Preferred title for the work
• For works after 1500, usually the title proper
on the first manifestation
• If published simultaneously in same language
with different titles, the title proper of the
resource received first
Kuhagen (NASIG June 2012) 53
54. Preferred title for the work
• If published simultaneously in different
languages, the title proper of the resource
received first (LCPS for 6.2.2.4)
• 6.2.1.7 changed in April 2012 update to retain
initial article
– Most/all in U.S. will apply new alternative at
6.2.1.7 to delete initial article
Kuhagen (NASIG June 2012) 54
55. Preferred title for the work – why?
• Becomes the authorized access point or the
base of the authorized access point
• If the same as the title proper and it doesn’t
conflict with the preferred title for another
work, why is it important?
– Is a different element for a different entity
– Shortcut to omit this element in past/current MARC
records when the same made us “unaware” of its
role – or perhaps even of its separate existence
Kuhagen (NASIG June 2012) 55
56. Reminders about other work elements
• Used when needed as additions to the
authorized access point and can be used in
name and series authority records for serials:
– Form of the work
– Date of the work *
– Place of origin of the work *
– Other distinguishing characteristic of the work
* -- may be information from the manifestation if don’t
know information about the work
Kuhagen (NASIG June 2012) 56
57. Authorized access point for the work –
RDA 6.27
• For serials, the “work” is the work as a
whole, NOT an individual issue or part
• Works created by one person, family, or
corporate body (6.27.1.2) – combine:
– Authorized access point for person, family, or
corporate body responsible for creating the
work (see 19.2.1.1), and
– Preferred title for the work
Kuhagen (NASIG June 2012) 57
58. Authorized access point for the work –
RDA 6.27
• Collaborative works (6.27.1.3) -- combine
– Authorized access point for person, family, or
corporate body principally responsible [or first-
named] for creating the work (see 19.2.1.1), and
– Preferred title for the work
• Compilations of works by different
persons, families, or corporate bodies (6.27.1.4):
– Preferred title for the compilation
Kuhagen (NASIG June 2012) 58
59. Creator element in access point
• Not explained in chapter 6 where instructions
about attributes of the work and access points for
works are found
• Is really a relationship to the work being identified
(not an attribute of the work)
• So, is explained in relationship chapter 19:
“Persons, Families and Corporate Bodies
Associated with a Work” (references from 6.27.1)
Kuhagen (NASIG June 2012) 59
60. RDA 19.2 = Creator
• 19.2.1.1.1: “Corporate Bodies Considered to Be
Creators”
– Body becomes creator if resource fits one of the
categories listed (not the role of the body):
administrative, proceedings, policies, laws, etc.
– Continues current U.S. practice
• 19.2.1.1.2: “Government and Religious Officials
Considered to Be Creators”
– Official becomes creator if resource fits one of
the categories listed (not the role of the official)
Kuhagen (NASIG June 2012) 60
61. RDA 19.2 = Creator
• 19.2.1.1.3: “Persons or Families Considered to
be Creators of Serials”
– Instruction added in April 2012 update of RDA is
consistent with U.S. practice (clues: opinions of
person, entity is publisher, name part of title
proper, etc.)
– Decision on creator or no creator is based on
role played by the person or family for the
whole serial; default = no creator
Kuhagen (NASIG June 2012) 61
62. Not a creator but important for the
serial work?
• 19.3: “Other Person, Family, or Corporate
Body Associated with a Work”
– Additional relationships that can be included
for a serial
– We’ll return to 19.3 when we get to
relationships
Kuhagen (NASIG June 2012) 62
63. EXERCISE: Serial creator
• Page 4 in Exercise packet
• Indicate
– which serials have a creator for the serial as a
whole
– for those serials, what entity would be used in
the authorized access point for the serial work
Kuhagen (NASIG June 2012) 63
64. Authorized access point
is for a conference -- reminders
• Retain frequency word in preferred name of
conference
• If the access point is for a serial conference:
– Do not add location (11.13.1.8)
– Do not add numbers or dates (LCPS for
11.13.1.8 – LC is proposing revision to fix RDA
error)
Kuhagen (NASIG June 2012) 64
65. Authorized access point for the creator
– April 2012 RDA changes
• If creator is a person, do not include field of
activity to break a conflict with access point
for another person
• If creator is a head of government, use term in
language preferred by cataloging agency
Kuhagen (NASIG June 2012) 65
66. Authorized access point conflicts
• 6.27.1.9: add one or more of the following if
same as authorized access point for another
work or for a person, family, corporate body:
– Form of work
– Date of work
– Place of origin of the work
– Another distinguishing characteristic of the
work
Kuhagen (NASIG June 2012) 66
67. Work elements in authority records
• If creating NAR or SAR for a serial work, can
include attributes of the work:
– Form of work (380)
– Date of work (046 $k, $l)
– Place of origin of the work (370 $g)
– Another distinguishing characteristic of the
work (381)
Kuhagen (NASIG June 2012) 67
68. Elements for identifying expressions –
ch. 6
• Content type
• Date of expression
• Language of expression
• Other distinguishing characteristic of the
expression
• Identifier for the expression
Kuhagen (NASIG June 2012) 68
69. Reminders about expression elements
• Content type has controlled vocabulary
– If more than one applies, pick main one or give all
– If none in list apply, use “other”
– If cannot determine, use “unspecified”
• Date of expression – may need to use date of
earliest manifestation
• Language of expression – use name from
standard list (in U.S., use the MARC code list)
Kuhagen (NASIG June 2012) 69
70. Content, Media, & Carrier Types
• Will need some of these terms taken from
RDA vocabularies for later exercise
– Content (expression attribute): text; performed
music; still image; spoken word
– Media (manifestation attribute): audio;
computer; unmediated [i.e., no device needed]
– Carrier (manifestation attribute): audio disc;
computer disc; online resource; volume
Kuhagen (NASIG June 2012) 70
71. Authorized access point
for the expression
• Start with the authorized access point for the
work
• Add one or more of the following to identify
the expression (6.27.3):
– content type
– date of expression
– language of expression
– other distinguishing characteristic of
expression
Kuhagen (NASIG June 2012) 71
72. Always identify expression in
authorized access point?
• LCPS for 6.27.3 gives LC practice to identify by
adding attribute to authorized access point for
work in these serial situations:
– Translations
– Language editions
• LC policy for non-LCPS situations: identifying
attribute will be part of the bibliographic data
but not in the authorized access point
• PCC still discussing its policy
Kuhagen (NASIG June 2012) 72
73. Expression elements in
authority records
• If creating NAR or SAR for a serial expression
work, can include attributes of the expression:
– Content type (336)
– Date of expression (046 $k, $l)
– Language of expression (377)
– Another distinguishing characteristic of the
expression (381)
Kuhagen (NASIG June 2012) 73
74. Describing content of
works and expressions – ch. 7
• Not included in authorized access points
• In current implementation, may be in
bibliographic records for manifestations
embodying work/expression
– E.g., illustrations, duration, colour
content, scale, performers, awards
Kuhagen (NASIG June 2012) 74
75. Wide range of work
and expression attributes
• Review ch. 7 to see which ones apply to
resources you’re cataloging:
textual, cartographic, moving
image, music, digital, etc., resources
• Many of these attributes (e.g., duration, color
content, illustrations) recorded now in MARC
300 field – is confusing because others in that
field are carrier characteristics of the
manifestation
Kuhagen (NASIG June 2012) 75
76. Other ch. 7 serial aspects
• Presence of supplementary content (e.g.,
indexes and bibliographies) in the resource
• Details on language of content
• RDA 7.29: New element (Note on expression)
and element sub-type (Note on changes in
content characteristics)
– Just added to RDA in the April 2012 update
– Confirms that new descriptions aren’t required
due to changes in expression attributes
Kuhagen (NASIG June 2012) 76
77. EXERCISE: Attributes identifying serials
• Pages 5-6 (5 surrogates) in Exercise packet and
separate worksheets
• For each resource, fill in attributes for sections
A-D on worksheets – also see instructions at
top of page 1 of worksheets
• If place and/or date of publication
missing, supply probable place/date or give
“*Place of publication not identified+” and/or
“*Date of publication not identified+”
Kuhagen (NASIG June 2012) 77
78. Relationships
• The “other half” of the conceptual model
• Ch. 17’s context – remember not to apply now
• Relationships between and among Group 1 and
Group 2 entities
– No core relationships identified – so, judgment
or policy
Kuhagen (NASIG June 2012) 78
79. Ch. 18-22: between Group 1
and Group 2
• Ch. 18: general guidelines on recording
relationships to persons, families, and
corporate bodies associated with …
• Ch. 19: … a work
• Ch. 20: … an expression
• Ch. 21: … a manifestation
• Ch. 22: … an item
Kuhagen (NASIG June 2012) 79
80. Ch. 18 general guidelines
• Give relationships that are “applicable and
readily ascertainable” (18.3) – cataloger
judgment/policy
• Two conventions for expressing relationship:
– Identifier for the person, family, or corporate
body (LCPS: don’t use identifier alone due to
current implementation)
– Authorized access point for the person, family, or
corporate body
Kuhagen (NASIG June 2012) 80
81. More in chapter 18
• 18.4.2.2: If there is a change in responsibility
for the serial but a new description isn’t
required (check categories in 1.6.2):
– Give additional access points for Group 2 entities
associated with later issues or parts
(e.g., different issuing body for later issues of a
journal)
– If important for access – cataloger judgment or
policy
Kuhagen (NASIG June 2012) 81
82. More in chapter 18
• 18.5: Relationship designator: explains nature
of the relationship (i.e., the role played by the
Group 2 entity)
– In current implementation, add designator in
subfield at end of the authorized access point
($e for X00, X10; $j for X11)
– Designators for ch. 19-22 in RDA appendix I with
definitions for role played (if role not included in
appendix, can supply own term)
– Some general roles subdivided into specific roles
Kuhagen (NASIG June 2012) 82
83. Returning to ch. 19: … to work
• 19.2: Creator – precedes preferred title in the
authorized access point (covered earlier)
– If more than one creator at same time (a
collaborative work) , additional creators as
additional access points in current implementation
(only first is core)
110 $a First-named creator on issue,
$e author.
710 $a Second-named creator on same
issue, $e author.
Kuhagen (NASIG June 2012) 83
84. Non-creator roles related to the work
• 19.3: Other roles (i.e., non-creator) related to
the work
• Loophole in 19.3: a few situations where a
non-creator is used in authorized access point
to identify the work (read the “core when”
statement)
– E.g., when laws governing one jurisdiction are
enacted by another jurisdiction (6.29.1.2 says to
use the jurisdiction governed + preferred title)
Kuhagen (NASIG June 2012) 84
85. Common Group 2 designators for
serial work relationships
• Creator roles (I.2.1):
– Author
– Compiler [e.g., of a directory or bibliography]
– Enacting jurisdiction
• Non-creator roles (I.2.2.):
– Host institution
– Issuing body
– Sponsoring body
• Non-creator used to identify the work (I.2.2):
– Jurisdiction governed
Kuhagen (NASIG June 2012) 85
86. Ch. 19 on JSC’s to-do list
• Discuss revision to emphasize role of
corporate body and government/religious
official rather than the category of resource
• Result of such a change: many fewer
situations of “creator” for serial works
• Not enough time before first release of RDA to
discuss revision with constituencies and
consider impact on existing records
Kuhagen (NASIG June 2012) 86
87. Ch. 20: … to an expression
• 20.2: “Contributor” (the general term for all
roles relating to an expression)
• Common serial contributor roles:
– Editor of compilation [for an editor of a
journal] – definition being clarified in the June
12 release of the RDA Toolkit
– Translator
Kuhagen (NASIG June 2012) 87
88. Ch. 21: … to a manifestation
• Four of the possible roles for some serial
manifestations –but no relationship designators
for these roles in appendix I because they are
elements in chapter 2:
– Producer (unpublished resource)
– Publisher
– Distributor
– Manufacturer
Kuhagen (NASIG June 2012) 88
89. Ch. 22: … to an item
• For relationships to a single copy of a
manifestation
• Not that common for serial resources
– More likely for rare serials or special collection
materials when might be important to note
relationship to former owner or current custodian
Kuhagen (NASIG June 2012) 89
90. Ch. 24-28: within Group 1
• Ch. 24: general guidelines
• Ch. 25: related works
• Ch. 26: related expressions
• Ch. 27: related manifestations
• Ch. 28: related items
• Can be included in bibliographic and authority
records
Kuhagen (NASIG June 2012) 90
91. Ch. 24
• Three conventions for expressing relationships:
– Identifier for the related
work, expression, manifestation, or item (LCPS:
don’t use identifier alone due to current
implementation)
– Authorized access point for the work or
expression (remember: no RDA instructions yet
for authorized access point for a manifestation
or item)
– Description of the related
work, expression, manifestation or item
Kuhagen (NASIG June 2012) 91
92. Description convention
• Structured: full or partial description written
with same structure as resource being
described (serials usually are “partial”)
Continues (work): ______(___).
Translated as: ______ [language]. ______
• Unstructured: written as a sentence/paragraph
Merged with: _______, to form: _______
Kuhagen (NASIG June 2012) 92
93. More in chapter 24
• 24.5: Relationship designator: explains nature
of the relationship between resources
– In current implementation, add designator in
subfield $i at beginning of the authorized access
point or at beginning of description
– In current implementation, relationship may
already be indicated in MARC linking fields
– Designators for ch. 25-28 in RDA appendix J with
definitions for relationship (if missing in
appendix, can supply own term)
Kuhagen (NASIG June 2012) 93
94. Organization of appendix J
• By categories of relationships, then general
relationships followed in some cases by specific
relationships
• Most repeat at each of the Group 1 entities (why
there is a parenthetical qualifier with a Group 1
entity for most of the designators)
• JSC is taking a second look at appendix to
consider some changes (e.g., for series)
Kuhagen (NASIG June 2012) 94
95. Ch. 25: related works
• Common serial work relationship categories:
– Whole-part: in a monographic series, contains
another work (in each or some issues)
– Accompanying: supplement to, is a supplement
– Sequential:
continuation, merger, split, absorption, etc.
Kuhagen (NASIG June 2012) 95
96. Common relationship designators
for serial works
• Appendix J.2 for works:
– Whole-part (J.2.4): “contains (work)”, “in
series (work)”
– Accompanying (J.2.5): “supplement
(work)”, “supplement to (work)”
– Sequential (J.2.6): “absorbed
(work)”, “continues (work)”, “merger of
(work)”, “continued by (work),” etc.
Kuhagen (NASIG June 2012) 96
97. Ch. 26: related expressions
• Common serial expression relationships:
– Translations
– Language editions (remember: using first
resource received to determine preferred title
for the work)
Kuhagen (NASIG June 2012) 97
98. Common relationship designators
for serial expressions
• Appendix J.3 for expressions:
– Derivative (J.3.2): “translation of”, “translated
as”
– No specific designator there now for language
editions
Kuhagen (NASIG June 2012) 98
99. Ch. 27: related manifestations
• Common serial manifestation relationships:
– Different formats
– Reproductions
– Special issues
– Issued with
Kuhagen (NASIG June 2012) 99
100. Common relationship designators
for serial manifestations
• Appendix J.4 for manifestations:
– Equivalent (J.4.2): “also issued as”, “mirror
site”, “reproduced as,” “reprint of
(manifestation)”, etc.
– Whole-part (J.4.4): “special issue
of”, “insert”, etc.
– Accompanying (J.4.5): “issued with”, “filmed
with (manifestation)”, etc.
Kuhagen (NASIG June 2012) 100
101. LC RDA policy for reproductions
• Follow RDA: catalog the reproduction, not the
original (that’s what AACR2 says but LC/U.S.
followed AACR when in a different format)
• Will catalog serial reproduction as serial even
though mode of issuance is single-unit or
multipart monograph
• Not yet discussed by the PCC
Kuhagen (NASIG June 2012) 101
102. Simple reproduction example -- MARC
245 00 $a Journal of ABC.
362 0# $a Volume 1-
264 #1 $a Chicago : $b Film Reproductions,
$c 2012-
300 ## $a microfilm reels …
776 08 $i Reproduction of (manifestation):
$t Journal of ABC. $d Boston : ABC
Publishers, 1984-2002. $h 19 v. ;
24 cm.
Kuhagen (NASIG June 2012) 102
103. Another reproduction example -- MARC
130 0#
$a XYZ bulletin
245 10
$a Bulletin of XYZ.
362 0#
$a Volume 1-volume 13.
264 #1
$a Denver: $b Shipman Publishing,
$c 2011-2012.
300 ## $a 13 volumes …
580 ## $a Reprint of the quarterly journal
published in 52 numbers with title
XYZ bulletin.
775 08 $i Reprint of (manifestation):
$t XYZ bulletin. $d Miami: Kerry
Publishers, 1967-1979. $h 52 no. ;
26 cm.
Kuhagen (NASIG June 2012) 103
104. Ch. 28: related items
• Common serial item relationships:
– Reproductions of specific items (e.g., for local
preservation purposes)
– Bound with (local action)
– Filmed with (local action)
Kuhagen (NASIG June 2012) 104
105. Common relationship designators
for serial items
• Appendix J.5 for items:
– Equivalent (J.5.2): “reproduction of
(item)”, “digital transfer of (item)”, “electronic
reproduction of”, “reprint of (item)”
– Accompanying (J.5.5): “bound with”, “filmed
with (item)”
Kuhagen (NASIG June 2012) 105
106. EXERCISE: Relationships for serials
• Pages 5-6 (surrogates) in Exercise packet and
separate worksheets
• For each resource, fill in relationships for
sections E-F on the worksheets
Kuhagen (NASIG June 2012) 106
107. New MARC fields applying to serials
• Repeatable 264 (replacing 260) to separate
different statements; 2nd indicator signals content
of the field:
0 = Production
1 = Publication
2 = Distribution
3 = Manufacture
4 = Copyright notice date
• CONSER will be issuing guidelines; LC will apply in
RDA records beginning this summer
Kuhagen (NASIG June 2012) 107
108. New MARC fields can apply to serials
• Modification of 340 field and addition of 344-
347 fields for carrier characteristics (300 $b is so
crowded)
– 340: Physical medium
– 344: Sound characteristics
– 345: Projection characteristics
– 346: Video characteristics
– 347: Digital file characteristics
Kuhagen (NASIG June 2012) 108
109. JSC and RDA Toolkit information
• RDA content responsibility of the JSC
• National library or program policy decisions on
“Resources” tab managed by those groups
– Free LCPSs (LC Policy Statements – to become
LC/PCC PSs this summer) – icon signal in RDA
content
• Some content on “Tools” tab
(e.g., mappings, examples, workflows) from
JSC, national libraries, programs
• Other content by ALA Publishing
Kuhagen (NASIG June 2012) 109
110. Updating of RDA content
• Formal proposals for constituency review
– Listing of possible proposals given on JSC web site
(http://www.rda-jsc.org/news.html)
– Proposals for November 2012 meeting due August 8
• Fast Track process to fix typos, add glossary
definitions, revise wording for consistency, revise
examples, etc.
– Discussed/approved by JSC on ongoing basis
Kuhagen (NASIG June 2012) 110
111. RDA Toolkit schedule
• Approximately 8 updates/releases a year
• When scheduled, on 2nd Tuesday of the month
• Called an update if RDA changes result from
formal proposals
– Icon and revision history
• Called a release if RDA changes result from the
Fast Track process
– No icon and revision history
Kuhagen (NASIG June 2012) 111
112. Current releases/updates & RDA
• April 10 update – RDA changes from proposals
affecting serials noted in this presentation
• May 8 release – no changes in RDA content
• June 12 release – RDA changes from Fast Track
process
• No July release
• August 14 release – RDA changes from Fast
Track process
Kuhagen (NASIG June 2012) 112
113. Source information for RDA and Toolkit
changes
• RDA Toolkit development blog:
http://www.rdatoolkit.org/development
• JSC website “New documents” section
(http://www.rda-jsc.org/workingnew.html)
– Proposals ending with “Sec final”
– Documents in the 6JSC/Sec series for Fast Track
changes
Kuhagen (NASIG June 2012) 113
114. LC RDA implementation plans
• Cataloging staff members who participated in
the Oct.-Dec. 2010 U.S. RDA Test returned to
RDA cataloging in November 2011
• Training June 2012-March 2013 for other
cataloging staff -- approximately 60 a month
who then will do only RDA cataloging
• All training to be completed by March 31,
2013: LC’s “Day One”
Kuhagen (NASIG June 2012) 114
115. LC and other national libraries’ plans
• LC’s training plan and training materials
available on Catalogers Learning Workshop (see
next slide) and via links on LC’s site for RDA
implementation: http://www.loc.gov/aba/rda/
• Partner national libraries plan to implement in
2013:
– 1st quarter of 2013: NAL and NLM in the
U.S., British Library, Library and Archives
Canada, National Library of Australia
– Mid-2013: Deutsche Nationalbibliotek
Kuhagen (NASIG June 2012) 115
116. PCC training
• RDA training materials at Catalogers Learning
Workshop:
http://www.loc.gov/catworkshop/RDA%20training%2
0materials/index.html
– NACO training – available now (click on link there
for more information)
– BIBCO training – available fall 2012
– CONSER training – available fall 2012
• Other training materials at site: FRBR (3 modules);
Using the RDA Toolkit; record examples
Kuhagen (NASIG June 2012) 116
117. PCC implementation
• “Day One” for RDA authority records: March
31, 2013
– “… authority records entering the LC/NACO
Authority File must be coded RDA, and all access
points on bibliographic records coded “pcc” must
be RDA”
• No “Day One” for RDA bibliographic records
• See the Day One document at
http://www.loc.gov/aba/pcc/
Kuhagen (NASIG June 2012) 117
118. PCC guidelines, policies, MAPs
• See information/links under “RDA and PCC” at
http://www.loc.gov/aba/pcc/
• Includes CONSER Standard Record guidelines,
enhancing & editing RDA and pre-RDA serial
records – see disclaimer that not all complete
• More to be added/confirmed as PCC groups
finish their assignments
• NASIG Program Session F (June 9, 2:45-3:45)
Kuhagen (NASIG June 2012) 118
119. Questions ??
• About FRBR and FRAD?
• About RDA
• About the RDA Toolkit
• About LC and PCC implementation and
training materials?
• If questions later: judy.kuhagen@gmail.com
Kuhagen (NASIG June 2012) 119
120. Credits
• Slides 9, 27, 28 from training materials
prepared by Barbara Tillett (analogy on slides
27 and 28 from Patrick Le Bœuf)
• Slides 7, 25 from training materials developed
by Judy for participants in the U.S. RDA Test
• RDA logo and RDA text “used by permission of
the Co-Publishers for RDA (American Library
Association, Canadian Library Association, and
CILIP: Chartered Institute of Library and
Information Professionals)”
Kuhagen (NASIG June 2012) 120