2. 2
What is RDA?
RDA = Resource Description and Access
• new metadata standard replaces AACR2
• set of practical instructions
• built on the foundation of a theoretical framework/data model
objectives:
• to record better metadata to support better resource
discovery
• to record data that can be used in the web and linked data
environment
3. 3
Plan
not a training session
aim: overview of RDA
understand some of the background and the key
concepts --- to make training sessions easier
1. moving towards RDA implementation
2. key concepts and their visible impact on RDA
a) theoretical framework
b) objectives and principles
c) focus on the user
d) content standard
e) bibliographic information as data
5. 5
AACR2
successful standard
adopted by many countries
in use for many years
but
problems with AACR2
for example:
• written for card catalogues
• inadequate rules to describe new types of resources
• inconsistencies
• library specific
6. 6
Roots of RDA
1997 problems identified:
International Conference on the Principles &
Future Development of AACR, Toronto, Ontario
1998-2004 revisions to AACR2; revise within the existing
structure
2004 AACR3
2005 decision to develop a new standard: Resource
Description and Access
2005-2009 development of content for the new standard
2009 text of RDA completed
7. 7
Moving towards RDA
2010 first release of the RDA Toolkit (RDA plus)
2010 US testing (US RDA Test Coordinating Committee)
2011 some of the libraries who tested RDA decide to
continue producing RDA records
2011-2012 preparations for implementation
- work on recommendations arising from US Test
- community involvement
2012 announcement from the Library of Congress --
target date for implementation: March 31, 2013
8. 8
Moving towards RDA
2012 other national libraries are also planning to
target the 1st quarter of 2013 as their RDA
implementation date:
National Agricultural Library
National Library of Medicine
British Library
Library and Archives Canada
National Library of Australia
Deutsche Nationalbibliothek (mid 2013)
2011- translation projects: German, French, Spanish, Chinese
interest in RDA from non-AACR2 countries
9. 9
Is there a day 1?
Yes and No
1) day 1 is important for a sharing data environment:
PCC: declares day 1 for contributing to NACO authorities
LC: declares day 1 for its own cataloguing operations
2) some institutions never switched back after the test
3) each institution decides on day 1 for bibliographic data
10. 10
March 31, 2013
• all new authority records contributed to LC/NACO authority file
= RDA
• all records coded pcc = all RDA access points
all records coded pcc whether:
• RDA description
or
• AACR2 description
• LC will have completed training all its cataloging staff
and all LC records will be RDA records
11. 11
by March 31, 2013
• rapid rise in number of RDA bibliographic records
• changes in LC/NACO authority file
implications for authority work
implications for copy cataloging
12. 12
implementation --
not a single
instant instant
13. 13
Transition
Different institutions will make the transition at different speeds
OK to be in a hybrid environment:
1) hybrid database or catalogue √
AACR and RDA records in one catalogue or database
2) hybrid record √
AACR2 description and RDA access points
14. 14
Phase 1 of implementation
emphasis on continuity
RDA data in MARC 21
in current catalogues
creating bibliographic and authority records
some new fields
some changed instructions
some new instructions
BUT
>>> thinking about bibliographic information differently
15. 15
Phase 1 = starting down new track
RDA
• continuity and change
• moves us to a new track
• starts us on a promising
track for the future use of
our metadata
• useful to understand some
of the key RDA concepts and
see the long view
17. 17
AACR2 RDA
• continue to record the title
• continue to record the statement of responsibility
• continue to record the date of publication
But …
• new vocabulary
• new way of thinking about how we do these steps
18. 18
Similar, but ...
AACR2
1.2B1. Transcribe the edition statement as found on the item.
Use abbreviations as instructed in appendix B and numerals as
instructed in appendix C.
RDA
2.5.1.4. Transcribe an edition statement as it appears on the
source of information.
No instruction to abbreviate or to convert to arabic
numerals.
19. 19
Similar, but ...
• serious adherence to the principle of representation
“take what you see”
t.p. data recorded
3rd ed. 3rd ed.
Second edition Second edition
20. 20
On the surface …
similar instructions
but different framework
new vocabulary
but also
new concepts
22. 22
RDA’s theoretical framework
• explicit conceptual framework
• aligned with the FRBR and FRAD conceptual models
FRBR Functional Requirements for Bibliographic Records
1998
FRAD Functional Requirements for Authority Data
2009
FRAD is an extension of the FRBR model
• both models developed under the auspices of IFLA
• broad base of international consensus and support
23. 23
The two models
• widely used data modeling technique:
entity relationship model
• entities
• attributes
• relationships
• analyze bibliographic and authority data from the point of view
of how that data is used
24. 24
RDA vocabulary from FRBR + FRAD
• user tasks
• meaning and scope of the 11 bibliographic entities
work person concept
expression family object
manifestation corporate body event
item place
• entities – attributes – relationships
25. 25
Organization and Structure of RDA
RDA table of contents reflects alignment with FRBR
Section 1-4 = Recording attributes
Section 1. Recording attributes of manifestation and item
Section 2. Recording attributes of work and expression
Section 3. Recording attributes of person, family, and corporate
body
Section 4. Recording attributes of concept, object, event, and
place [placeholder]
26. 26
Organization and Structure of RDA
Sections 5-10 = Recording Relationships
Section 5. Recording primary relationships between work,
expression, manifestation, and item
Section 6. Recording relationships to persons, families, and
corporate bodies associated with a resource
Section 7. Recording subject relationships [placeholder]
Section 8. Recording relationships between works, expressions,
manifestations, and items
Section 9. Recording relationships between persons, families,
and corporate bodies
Section 10. Recording relationships between concepts, objects,
events, and places [placeholder]
27. 27
User tasks from FRBR + FRAD
Bibliographic data Authority data
• find • find
• identify • identify
• select • clarify (contextualize)
• obtain • understand (justify)
28. 28
Attributes
• how to record the attributes of entities (characteristics)
for example, entity = a manifestation
attributes we record: title proper
statement of responsibility
edition statement
place of publication
etc.
29. 29
Relationships: links between entities
work created by person
item owned by family
manifestation produced by corporate body
work based on work
manifestation electronic reproduction manifestation
person member of family
family founded corporate body
30. 30
Relationships in RDA
1. record relationship
2. specify exact nature of the relationship
for example
AACR2 name of a person ------- title of book
• type of relationship may be embedded in text of description
• bibliographic record contains name of person and title
RDA name of a person --- type of relationship --- work
• make the relationship explicit and clear
• relationship designators = controlled vocabulary
31. 31
Relationship designators
• specify roles
for example cartographer
performer
broadcaster
former owner
issuing body
• specify the nature of the relationship
for example adaptation of
paraphrased as
electronic reproduction of
32. 32
Relationships in RDA
examples with MARC 21 coding:
245 10 $a British Atlantic, American frontier : $b spaces of power in
early modern British America / $c Stephen J. Hornsby ; with
cartography by Michael J. Hermann.
700 1# $a Herman, Michael J., $e cartographer
245 00 $a Alice in Wonderland, or, What's a nice kid like you doing in a
place like this? /$c Hanna-Barbera Productions.
700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's
adventures in Wonderland.
authority record
500 3# $w r $i Descendant family: $a Adams (Family)
33. 33
Theoretical framework
• alignment with the FRBR and FRAD conceptual models
• bibliographic and authority data
>>> in terms of entities, attributes + relationships
• identify what is important --- how is data used
• systematic and coherent framework
>>> conceptual clarity
>>> logical consistency
>>> reference point for further development
34. 34
Underlying data model
>>> practical set of cataloguing instructions
● built on a theoretical framework
● built on a robust data model
• widely used data modeling technique
• understood by other metadata and data modeling communities
e.g. software engineers, information systems
and database designers
36. 36
RDA Objectives & Principles
• important part of RDA
• shaped many of the instructions that are different from AACR2
• concur with the International Cataloguing Principles (ICP)
37. 37
RDA Objectives & Principles
Objectives RDA 0.4.2 Principles RDA 0.4.3
• responsiveness to user • differentiation
needs
• sufficiency
• cost efficiency
• relationships
• flexibility
• representation
• continuity
• accuracy
• attribution
• common usage or practice
• uniformity
38. 38
Principle of representation
for example RDA 0.4.3.4
principle = representation
The data describing a resource should reflect
the resource’s representation of itself.
result = simplify transcription
“Take what you see”
39. 39
RDA = Take what you see
source = Kemptville, Ontario
AACR2 = Kemptville, Ont.
RDA = Kemptville, Ontario
264 1 $a Kemptville, Ontario
_____________________________________________________
source = Band LXXXVIII (series numbering)
AACR2 = Bd. 88
RDA = Band LXXXVIII
490 $a ... ; $v Band LXXXVIII
40. 40
RDA = Take what you see
source = Third revised edition
AACR2 = 3rd rev. ed.
RDA = Third revised edition
_____________________________________________
source = 2nd enlarged ed., revised
AACR2 = 2nd enl. ed., rev.
RDA = 2nd enlarged ed., revised
41. 41
Different instructions
AACR2 1.0F. Inaccuracies
In an area where transcription from the item is required,
transcribe an inaccuracy or a misspelled word as it appears in
the item. Follow such an inaccuracy either by [sic] or by i.e. and
the correction within square brackets. Supply a missing letter
or letters in square brackets.
RDA 1.7.9 Inaccuracies
When instructed to transcribe an element as it appears on the
source of information, transcribe an inaccuracy or a misspelled
word as it appears on the source, except where instructed
otherwise.
42. 42
Inaccuracy in RDA
1.7.9 continued
Make a note correcting the inaccuracy if it is considered to be
important for identification or access (see 2.20 ).
If the inaccuracy appears in a title, record a corrected form of the
title as a variant title (see 2.3.6 ) if it is considered to be important
for identification or access.
Exception:
2.3.1.4 Inaccuracies. When transcribing the title proper of a serial
or integrating resource, correct obvious typographic errors, and
make a note giving the title as it appears on the source of
information (see 2.20.2.4 ) ...
43. 43
RDA = Take what you see
title page = Melallization of polymers
AACR2 = Melallization [sic] of polymers
or Melallization [i.e. Metallization] of
polymers
RDA = Melallization of polymers
245 14 $a Melallization of polymers
246 1 $i Corrected title: $a Metallization
of polymers
45. 45
RDA Objectives & Principles
Objectives RDA 0.4.2 Principles RDA 0.4.3
• responsiveness to user • differentiation
needs
• sufficiency
• cost efficiency
• relationships
• flexibility
• representation
• continuity
• accuracy
• attribution
• common usage or practice
• uniformity
46. 46
Focus on the user
• record data that is important to the user
why is it important?
helps the user to find
identify
select
obtain
47. 47
Resource discovery = user tasks
Bibliographic data Authority data
• find • find
• identify • identify
• select • clarify
• obtain • understand
Why record the data? To help user achieve these
tasks.
48. 48
Consistent focus on the user
• RDA divided into 10 sections
• each section begins with general guidelines
• functional objectives and principles specific to the section
Functional objectives = relationship between data and user
tasks
the data (recorded or formulated according
to the instructions in that section)
the user tasks
49. 49
Example from Section 1
Section 1= Recording attributes of manifestations & items
1.2 Functional Objectives and Principles
The data describing a manifestation or item should enable the user to:
a) find manifestations and items that correspond to the user’s stated
search criteria
b) identify the resource described …
c) select a resource that is appropriate to the user’s requirements with
respect to the physical characteristics of the carrier and the
formatting and encoding of information stored on the carrier
d) obtain a resource …
50. 50
Basis for Cataloguer Judgment
• instructions encourage cataloguer judgment
--- based on user tasks
for example, from 3.7 Applied material
Record the applied material used in the resource if it is
considered important for identification or selection …
51. 51
Easier for user to identify
• avoid abbreviations
300 $a 398 pages :$b illustrations ; $c 25 cm
AACR2: 300 $a 398 p. :$b ill. ; $c 25 cm.
• avoid square brackets
300 $a 48 unnumbered pages, 256 pages
AACR2: 300 $a [48], 256 p.
• replace Latin abbreviations
300 $a 48, that is, 96 pages
AACR2: 300 $a 48 [i.e. 96] p.
• avoid cryptic information
300 $a xiv, 179 pages (incomplete)
AACR2: 300 $a xiv, 179 + p.
52. 52
Easier for user to find, identify
RDA: no more: rule of three
no more … [et al.] in description
if statement of responsibility names more
than one person >>> record all RDA 2.4.1.5
optional omission: record first named and
summarize the omission
[and six others]
access points for first named or principal core
or all
or cataloger judgment
or institutional policy
53. 53
Easier for user to find, identify
RDA: record all authors; access points for all authors;
define relationships with designators
100 1 $a Berry, John W., $e author.
245 10 $a Cross-cultural psychology : $b research and applications /
$c John W. Berry, Ype H. Poortinga, Seger M. Breugelmans,
Athanasios Chasiotis, David L. Sam.
250 $a Third edition.
264 1 $a Cambridge : $b Cambridge University Press, $c 2011.
300 $a xxii, 626 pages ; $c 25 cm
700 1 $a Poortinga, Ype H., $d 1939- $e author.
700 1 $a Breugelmans, Seger M., $e author.
700 1 $a Chasiotis, Athanasios, $e author.
700 1 $a Sam, David L., $e author.
54. 54
Easier for user to understand
RDA
optional omission (2.4.1.5):
more than three, omit and summarize
core relationship = access point for first-named
omit relationship designator
100 1 $a Berry, John W.
245 10 $a Cross-cultural psychology : $b research and
applications / $c John W. Berry [and four others].
250 $a Third edition.
264 1 $a Cambridge : $b Cambridge University Press, $c 2011.
300 $a xxii, 626 pages ; $c 25 cm
55. 55
Easier for user to find
AACR2 Aesop’s fables. Polyglot.
RDA Aesop’s fables. Greek
Aesop’s fables. Latin
Aesop’s fables. English
Aesop’s fables. German
AACR2 Aesop’s fables. English & German
RDA Aesop’s fables. English
Aesop’s fables. German
57. 57
RDA as a content standard
AACR2: MARC encoding + ISBD display
RDA = what data should the cataloguer record?
• possible to encode using many encoding systems
• can be encoded using MARC
• does not have to be encoded using MARC encoding
• can be used with web friendly XML based encoding schema,
such as Dublin Core, MODS
• possible to display the data in many ways
58. 58
RDA as a content standard
for example, encode the data as required in your data-sharing
environment
RDA says: record person’s date of birth = 1982
Encode?
$d 1982- MARC 21
<subfield code="d">1982- </subfield> MARCXML
<mods:namePart type="date">1982- </mods:namePart>
<dob>1982</dob>
<xs:element name="rdaDateOfBirth“>1982</xs:element>
59. 59
RDA as a content standard
for example, create displays that suit your user group:
RDA says: record person’s date of death = 2003
Display? died 2003
d. 2003
- 2003
date of death: 2003
60. 60
Identifying the entity
either
eye-readable data: name
date of birth and death
Shields, Carol, 1953-2003
and/or
machine actionable data: identifier
0101A6635
http://viaf.org/viaf/4944537/#Shields,_Carol
61. 61
RDA as a content standard
• not locked into library encoding practices
• not locked into library display practices
• get out of the library silo
>>> data visible on the web
>>> data interacting with the
data of other metadata
communities
63. 63
Data Elements
element = A word, character, or group of words and/or
characters representing a distinct unit of
bibliographic information.
appears similar to AACR2 definition
minus “forming part of an area”
effect is quite different from AACR2
each element is ≈ discrete
≈ precisely defined
≈ single attribute / single relationship
64. 64
AACR2
for example
AACR2: information embedded in non-specific places
notes digital file characteristics
physical description file type
MARC 538 encoding format
516 file size
500 resolution
300 regional encoding
transmission speed
65. 65
RDA
RDA: precise elements and element sub-types
digital file characteristics RDA 3.19
file type
encoding format
file size
resolution
regional encoding
transmission speed
66. 66
347 Digital File Characteristics
new MARC field 347
subfield codes
$a - File type (R)
$b - Encoding format (R)
$c - File size (R)
$d - Resolution (R)
$e - Regional encoding (R)
$f - Transmission speed (R)
67. 67
AACR2 Information
AACR2: assume human will decipher
ok to be ambiguous
AACR2: date of publication, distribution, etc.
date of copyright
date of manufacture
MARC 21: 260 $c
260 $g
68. 68
RDA Data Elements
RDA: precise elements – only one kind of data in an element
RDA: 5 different elements: RDA 2.7-2.11
date of production
date of publication
date of distribution
date of manufacture
date of copyright
MARC 21: 264 $c 5 different indicators
69. 69
Controlled vocabulary
• controlled vocabulary recommended for many elements
encoding format DAISY, MP3, Access, XML,
JPEG, TIFF, CAD, PDF,
Blu-ray, VCD
production method blueline, blueprint, engraving,
etching, lithograph, photocopy,
photoengraving, woodcut
base material Bristol board, canvas, cardboard,
ceramic, glass, leather, paper,
parchment, vellum
70. 70
RDA data = precise + usable data
RDA
• each element is distinct and precisely defined
• each element contains only one kind of data
• controlled vocabulary in many elements
each element has the potential to be usable:
to index
to search
to build meaningful displays of data
data in any element can be used: by humans
by computers
71. 71
Many new elements
many new elements but do not have to use them all
core elements
• not a level of description
• core elements are a minimum “a floor, not a ceiling”
• must include any additional elements required to differentiate
the resource or entity from a similar one
• inclusion of other elements --- cataloguer judgment
72. 72
Phase 1: RDA using MARC
Bibliographic description:
• core elements (RDA core, LC/PCC core)
• new MARC fields
• simplified instructions for transcription
• some new instructions when recording data
Authorized access points in bibliographic records:
• LC/NACO authority file
• some new instructions when identifying persons, families,
corporate bodies, works and expressions
Authority records:
• NACO guidelines
73. 73
AACR2: simple book (abbreviated)
020 $a 9780230242685 (hardback)
100 1 $a Stanfield, James Ronald, $d 1945-
245 10 $a John Kenneth Galbraith / $c by James Ronald Stanfield
and Jacqueline Bloom Stanfield.
260 $a Houndmills, Basingstoke, Hampshire : $b Palgrave
Macmillan, $c 2011.
300 $a xi, 251 p. ; $c 23 cm.
490 1 $a Great Thinkers in Economics Series
700 1 $a Stanfield, Jacqueline Bloom, $d 1947-
74. 74
RDA: simple book (abbreviated)
020 $a 9780230242685 (hardback)
100 1 $a Stanfield, James Ronald, $d 1945- $e author.
245 10 $a John Kenneth Galbraith / $c by James Ronald Stanfield
and Jacqueline Bloom Stanfield.
264 1 $a Houndmills, Basingstoke, Hampshire : $b Palgrave
Macmillan, $c 2011.
300 $a xi, 251 pages ; $c 23 cm.
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
490 1 $a Great Thinkers in Economics Series
700 1 $a Stanfield, Jacqueline Bloom, $d 1947- $e author.
75. 75
RDA: simple book (abbreviated)
020 $a 9780230242685 (hardback)
100 1 $a Stanfield, James Ronald, $d 1945- $e author.
245 10 $a John Kenneth Galbraith / $c by James Ronald Stanfield
and Jacqueline Bloom Stanfield.
264 1 $a Houndmills, Basingstoke, Hampshire : $b Palgrave
Macmillan, $c 2011.
300 $a xi, 251 pages ; $c 23 cm.
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
490 1 $a Great Thinkers in Economics Series
700 1 $a Stanfield, Jacqueline Bloom, $d 1947- $e author.
77. 77
RDA: audiocassette (from PCC examples)
100 1 $a Card, Orson Scott, $d 1951- $e author.
240 10 $a Ships of Earth. $s Spoken word
245 14 $a The ships of Earth / ǂc Orson Scott Card.
264 1 $a [Ashland, Oregon] : ǂb Blackstone Audiobooks, ǂc [2008]
264 4 $c ℗2008
300 $a 9 audiocassettes (approximately 13 hr.) : $b analog, Dolby
processed ; $c 10 x 7 cm, 4 mm tape.
336 $a spoken word $2 rdacontent
337 $a audio $2 rdamedia
338 $a audiocassette $2 rdacarrier
511 0 $a Read by Stefan Rudnicki. Directed by Emily Janice Card.
700 1 $a Rudnicki, Stefan, $d 1945- $e narrator.
700 1 $a Card, Emily Janice, $e director.
78. 78
RDA: audiocassette (from PCC examples)
100 1 $a Card, Orson Scott, $d 1951- $e author.
240 10 $a Ships of Earth. $s Spoken word
245 14 $a The ships of Earth / ǂc Orson Scott Card.
264 1 $a [Ashland, Oregon] : ǂb Blackstone Audiobooks, ǂc [2008]
264 4 $c ℗2008
300 $a 9 audiocassettes (approximately 13 hr.) : $b analog, Dolby
processed ; $c 10 x 7 cm, 4 mm tape.
336 $a spoken word $2 rdacontent
337 $a audio $2 rdamedia
338 $a audiocassette $2 rdacarrier
511 0 $a Read by Stefan Rudnicki. Directed by Emily Janice Card.
700 1 $a Rudnicki, Stefan, $d 1945- $e narrator.
700 1 $a Card, Emily Janice, $e director.
79. 79
AACR2: compilation (abbreviated+made-up)
100 1 $a Williams, Tennessee.
240 10 $a Selections. $f 2009
245 10 $a Favorite plays and a short story / $c Tennessee
Williams.
260 0 $a Boston : $b University Press, $c 2009.
300 $a 325 p. : $b ill. ; $c 28 cm
505 0 $a The Glass Menagerie -- A Streetcar Named Desire --
Cat on a Hot Tin Roof -- The Night of the Iguana.
80. 80
RDA: compilation (abbreviated+made-up)
100 1 $a Williams, Tennessee.
240 10 $a Works. $k Selections. $f 2009
245 10 $a Favorite plays and a short story / $c Tennessee
Williams.
264 1 $a Boston : $b University Press, $c 2009.
300 $a 325 pages : $b illustrations ; $c 28 cm
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
505 0 $a The Glass Menagerie -- A Streetcar Named Desire --
Cat on a Hot Tin Roof -- The Night of the Iguana.
700 12 $a Williams, Tennessee. $t Glass menagerie.
81. 81
RDA: compilation (abbreviated+made-up)
100 1 $a Williams, Tennessee.
240 10 $a Works. $k Selections. $f 2009
245 10 $a Favorite plays and a short story / $c Tennessee
Williams.
264 1 $a Boston : $b University Press, $c 2009.
300 $a 325 pages : $b illustrations ; $c 28 cm
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
700 12 $a Williams, Tennessee. $t Glass menagerie.
700 12 $a Williams, Tennessee. $t Streetcar named Desire.
700 12 $a Williams, Tennessee. $t Cat on a hot tin roof.
700 12 $a Williams, Tennessee. $t Night of the Iguana.
82. 82
Key concepts
Key concepts shape RDA:
• theoretical framework
• objectives and principles
• focus on the user
• content standard
• bibliographic information as data
>>> visible impact on RDA and the content of instructions
>>> many changes in RDA trace back to concepts
83. 83
Familiarity with key RDA concepts
• a useful way to grab hold of RDA
• a useful way to approach RDA implementation
84. 84
Flickr credits: creative commons attribution
Monarch life cycle – 14 of 20 by SidPix (Sid Mosdell)
http://www.flickr.com/photos/sidm/4813665260/
Monarch life cycle – 20 of 20 by SidPix (Sid Mosdell)
http://www.flickr.com/photos/sidm/4813666686/
Cross track – iPhone wall paper by CJ Schmit
http://www.flickr.com/photos/cjschmit/4623783487/
The roof continues by Martin Pettitt
http://www.flickr.com/photos/mdpettitt/2521374167/
Oregon silo by TooFarNorth
http://www.flickr.com/photos/toofarnorth/4597980984/
Rock climbing is fun by mariachily
http://www.flickr.com/photos/mariachily/3382799213/
Objectives 0.4.2.1Responsiveness to User NeedsThe data should enable the user to:find resources that correspond to the user's stated search criteriafind all resources that embody a particular work or a particular expression of that workfind all resources associated with a particular person, family, or corporate bodyfind all resources on a given subjectfind works, expressions, manifestations, and items that are related to those retrieved in response to the user's searchfind persons, families, and corporate bodies that correspond to the user's stated search criteriafind persons, families, or corporate bodies that are related to the person, family, or corporate body represented by the data retrieved in response to the user’s searchidentify the resource described (i.e., confirm that the resource described corresponds to the resource sought, or distinguish between two or more resources with the same or similar characteristics)identify the person, family, or corporate body represented by the data (i.e., confirm that the entity described corresponds to the entity sought, or distinguish between two or more entities with the same or similar names, etc.)select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and encoding of information stored on the carrierselect a resource appropriate to the user's requirements with respect to form, intended audience, language, etc. obtain a resource (i.e., acquire a resource through purchase, loan, etc., or access a resource electronically through an online connection to a remote computer)understand the relationship between two or more entitiesunderstand the relationship between the entity described and a name by which that entity is known (e.g., a different language form of the name)understand why a particular name or title has been chosen as the preferred name or title for the entity.0.4.2.2Cost EfficiencyThe data should meet functional requirements for the support of user tasks in a cost-efficient manner.0.4.2.3Flexibility The data should function independently of the format, medium, or system used to store or communicate the data. They should be amenable to use in a variety of environments.0.4.2.4Continuity The data should be amenable to integration into existing databases (particularly those developed using AACR and related standards).Differentiation The data describing a resource should differentiate that resource from other resources.The data describing an entity associated with a resource should differentiate that entity from other entities, and from other identities used by the same entity.0.4.3.2Sufficiency The data describing a resource should be sufficient to meet the needs of the user with respect to selection of an appropriate resource.0.4.3.3Relationships The data describing a resource should indicate significant relationships between the resource described and other resources.The data describing an entity associated with a resource should reflect all significant bibliographic relationships between that entity and other such entities.0.4.3.4Representation The data describing a resource should reflect the resource’s representation of itself.The name or form of name designated as the preferred name for a person, family, or corporate body should be the name or form of name most commonly found in resources associated with that person, family, or corporate body, or a well-accepted name or form of name in the language and script preferred by the agency creating the data. Other names and other forms of the name that are found in resources associated with the person, family, or corporate body or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant names.The title designated as the preferred title for a work should be the title most frequently found in resources embodying the work in its original language, the title as found in reference sources, or the title most frequently found in resources embodying the work. Other titles found in resources embodying the work or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant titles.0.4.3.5Accuracy The data describing a resource should provide supplementary information to correct or clarify ambiguous, unintelligible, or misleading representations made on sources of information forming part of the resource itself.0.4.3.6Attribution The data recording relationships between a resource and a person, family, or corporate body associated with that resource should reflect attributions of responsibility made either in the resource itself or in reference sources, irrespective of whether the attribution of responsibility is accurate.0.4.3.7Common Usage or PracticeData that is not transcribed from the resource itself should reflect common usage in the language and script preferred by the agency creating the data.The part of the name of a person or family used as the first element in recording the preferred name for that person or family should reflect conventions used in the country and language most closely associated with that person or family.0.4.3.8Uniformity The appendices on capitalization, abbreviations, order of elements, punctuation, etc., should serve to promote uniformity in the presentation of data describing a resource or an entity associated with a resource.
Objectives 0.4.2.1Responsiveness to User NeedsThe data should enable the user to:find resources that correspond to the user's stated search criteriafind all resources that embody a particular work or a particular expression of that workfind all resources associated with a particular person, family, or corporate bodyfind all resources on a given subjectfind works, expressions, manifestations, and items that are related to those retrieved in response to the user's searchfind persons, families, and corporate bodies that correspond to the user's stated search criteriafind persons, families, or corporate bodies that are related to the person, family, or corporate body represented by the data retrieved in response to the user’s searchidentify the resource described (i.e., confirm that the resource described corresponds to the resource sought, or distinguish between two or more resources with the same or similar characteristics)identify the person, family, or corporate body represented by the data (i.e., confirm that the entity described corresponds to the entity sought, or distinguish between two or more entities with the same or similar names, etc.)select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and encoding of information stored on the carrierselect a resource appropriate to the user's requirements with respect to form, intended audience, language, etc. obtain a resource (i.e., acquire a resource through purchase, loan, etc., or access a resource electronically through an online connection to a remote computer)understand the relationship between two or more entitiesunderstand the relationship between the entity described and a name by which that entity is known (e.g., a different language form of the name)understand why a particular name or title has been chosen as the preferred name or title for the entity.0.4.2.2Cost EfficiencyThe data should meet functional requirements for the support of user tasks in a cost-efficient manner.0.4.2.3Flexibility The data should function independently of the format, medium, or system used to store or communicate the data. They should be amenable to use in a variety of environments.0.4.2.4Continuity The data should be amenable to integration into existing databases (particularly those developed using AACR and related standards).Differentiation The data describing a resource should differentiate that resource from other resources.The data describing an entity associated with a resource should differentiate that entity from other entities, and from other identities used by the same entity.0.4.3.2Sufficiency The data describing a resource should be sufficient to meet the needs of the user with respect to selection of an appropriate resource.0.4.3.3Relationships The data describing a resource should indicate significant relationships between the resource described and other resources.The data describing an entity associated with a resource should reflect all significant bibliographic relationships between that entity and other such entities.0.4.3.4Representation The data describing a resource should reflect the resource’s representation of itself.The name or form of name designated as the preferred name for a person, family, or corporate body should be the name or form of name most commonly found in resources associated with that person, family, or corporate body, or a well-accepted name or form of name in the language and script preferred by the agency creating the data. Other names and other forms of the name that are found in resources associated with the person, family, or corporate body or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant names.The title designated as the preferred title for a work should be the title most frequently found in resources embodying the work in its original language, the title as found in reference sources, or the title most frequently found in resources embodying the work. Other titles found in resources embodying the work or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant titles.0.4.3.5Accuracy The data describing a resource should provide supplementary information to correct or clarify ambiguous, unintelligible, or misleading representations made on sources of information forming part of the resource itself.0.4.3.6Attribution The data recording relationships between a resource and a person, family, or corporate body associated with that resource should reflect attributions of responsibility made either in the resource itself or in reference sources, irrespective of whether the attribution of responsibility is accurate.0.4.3.7Common Usage or PracticeData that is not transcribed from the resource itself should reflect common usage in the language and script preferred by the agency creating the data.The part of the name of a person or family used as the first element in recording the preferred name for that person or family should reflect conventions used in the country and language most closely associated with that person or family.0.4.3.8Uniformity The appendices on capitalization, abbreviations, order of elements, punctuation, etc., should serve to promote uniformity in the presentation of data describing a resource or an entity associated with a resource.