Call Girls in Dwarka Mor Delhi Contact Us 9654467111
FRBR, FRAD and RDA I don't speak cataloging why should I care
1. FRBR, FRAD and RDA :
I don’t speak cataloging, why should I care?
Presented by Deann Trebbe
Technical Services Librarian
Grand Canyon University Library
at the Arizona Library Association Annual Conference
30 November, 2011
Tucson, Arizona
1
Disclaimer:
I am not an expert on this subject – far from it – but I am what I would call a next-gen old-
school cataloger. Old school because I was trained in the traditional methods, next-gen
because I was then thrust into the world of electronic documents. I attended Library
School at The Catholic University of America in the late 80’s, early 90’s so my cataloging
education began as I straddled the gap between the card catalogs of old and the OPACs of
the next generation. I did an internship at the Library of Congress where for 8 hours a
week I would sit in front of a monochrome computer monitor entering MARC records
from a stack of catalog cards.
As the Library of Congress goes – so go I, as a cataloger – and so with the national
libraries decision to implement RDA no sooner than Jan. 2013, I began the seeking the
information I would need to make the jump at the same time. Here is a compilation of
what I have been able to glean so far….
2. What does it all mean?
2
True confessions – I am a recovering United States Marine Musician. Truth be known –
I’m not really in recovery at all, I still think like a Marine, act like a Marine and talk like a
Marine. And Marines – much like librarians – tend to speak in acronyms. Occasionally at
our library staff meetings hilarity occurs (in my mind anyway) when the reference and
curriculum librarians use acronyms that are common knowledge to our library. For
example, when the curriculum librarian mentions AWS the rest of the staff translate that to
Academic Web Services in their minds. Having spent the bulk of my formative adult years
in the Marine Corps, I hear Amphibious Warfare School. On the other hand when I start
mentioning acronyms like FRBR or RDA I generally get blank stares in return. So I
thought we should start off this morning by exploring some of the acronyms and what they
mean before we launch into the discussion of why this is important to start thinking about
how the library and it’s users will be affected by them.
3. FRBR = Functional Requirements for
Bibliographic Records
FRAD = Functional Requirements for
Authority Records
RDA = Resource Description and Access
… and lurking around the corner
3
Let’s start with some definitions and then we will explore a bit more in-depth.
FRBR = Functional Requirements for Bibliographic Records
FRAD = Functional Requirements for Authority Records
RDA = Resource Description and Access
… and lurking around the corner
5. What FRBR is not:
A set of rules
An international standard
A system design for online catalogs
5
Let’s start with FRBR and what it isn’t:
It is not a set of rules
It is not an international standard
It is not a system design for online catalogs
It can not be implemented because it is conceptual, it doesn’t cover every possible way that
something might appear. It says most of the time it looks like this.
(Taylor 2007, 4)
6. What FRBR is ….
A conceptual model – based on the entity-attribute-
relationship model of analysis
Entity = Thing (key object of interest to the user)
Attribute = Characteristic
RELATIONSHIP = Interaction
6
What FRBR is: It is what it is ….
So, what is FRBR?
FRBR is a conceptual model for the bibliographic universe. The bibliographic what?....
The International Cataloging Principles glossary defines Bibliographic universe as “The
realm related to the collections of libraries, archives, museums, and other information
communities. *
OK – so what does that mean – sounds kind of Star War-ish.
*(Source: IFLA Meetings of Experts on an International Cataloguing Code [i.e. the
collective meetings from 2003-2007])”
FRBR is an evolving conceptual model describing the bibliographic universe that we
organize and control through cataloging codes. It is designed to help users easily navigate
catalogs and find the material they want, in the form they want it. In addition to the things
libraries and other institutions might collect. It also includes all people, corporate bodies
or families that might interact with those collections in any way. Including, but not
exclusively, authors, owners, producers, etc. It is intended to connect everyone to
everything. It also includes all concepts that might be needed to describe these entities.
7. Late 1980’s many in the cataloging world … recognized that fundamental changes were
happening in the environment that might require a rethinking of the way we conceive of
and organize information.
A 1990 conference in Stockholm, sponsored by the International Federation of Library
Associations and Institutions, better known as IFLA, commissioned a study of the
functions of bibliographic records. The agreed upon core components were to be based
not on the convenience of the cataloger – or on perceived pressure to reduce costs, but on
the needs of users of the records. (Maxwell, 2008, p.2-3)
The result is the FRBR model.
[FRBR] … will go a long way toward helping untangle the explosion of information that is
characteristic of the late 20th and early 21st centuries. (Maxwell, 2008)
FRBR considers that each work has a unique entry point and from that you can then
describe that work in its various formats through their relationships and attributes. FRBR
and FRAD both are big on relationships
Some FRBR terms you need to know
Entity = Thing (key objects of interest to user’s of databases)
Attibute = characteristic
relationship = interaction
Either entities or relationships can have attributes
FRBR describes user tasks that serve as criteria to determine which attributes and
relationships are important in bibliographic description
8. FRBR Entities
Group 1 = AACR2 Bibliographic Description
WEMI
•Work
•Expression
•Manifestation
•Item
Group 2 = AACR2 Access points
Person and or corporate body
Group 3 = AACR2 Subjects
•Concept
•Object
•Event
•Place
… In other words: Title, author, subject
8
The first group comprises the products of intellectual or artistic endeavour that are
named or described in bib records: work, expression, manifestation, and item.
The second group comprises those entities responsible for the intellectual or artistic
content, the physical production and dissemination, or the custodianship of such
products: person and corporate body.
The third group comprises an additional set of entities that serve as the subjects of
intellectual or artistic endeavour: concept, object, event, and place.
(LeGrow, 2010, Taylor 2007, 4-8)
J. Bowen writes in FRBR: Coming soon to your Library in the July 2005 issue of Library
Resources and Technical services “Most FRBR entities and attributes are already present
in library catalog records, and the influence of FRBR can also be seen in existing library
activities. FRBR is thus not something totally foreign, but a fresh, more rigorous way of
thinking about what libraries already do that provides a basis for designing new ways to
improve users' access to library resources.”
Bowen, J. FRBR: Coming Soon to Your Library?. Library Resources & Technical Services v. 49 no. 3
(July 2005) p. 175-88
9. 9
This slide shows the relationships of the Group 1 entities to each other.
10. Oliver, 2011 10
Here are some examples of the links between entities.
11. FRBR maps the attributes and
relationships to user tasks
-- find entities that correspond to the user’s stated
search criteria
-- identify an entity
-- select an entity that is appropriate to the user’s needs
-- acquire or obtain access to the entity described
FRBR Users
-- End users of information retrieval systems
-- Information workers assisting users
-- Information workers maintaining databases
(Taylor 2007, 15)11
FRBR is all about the user and is based around 4 user tasks
-- find entities that correspond to the user’s stated
search criteria
-- identify an entity
-- select an entity that is appropriate to the user’s needs
-- acquire or obtain access to the entity described
FRBR Users
-- End users of information retrieval systems
-- Information workers assisting users
-- Information workers maintaining databases
12. Oliver, 2011 12
Let’s put it all together now. From the user’s standpoint.
13. Oliver, 2011 13
From the library staff’s standpoint.
14. FRBR example
14
RDA is on the way! (Le Grow)
The FRBR model can be used to present options to
users in a more clear and user-friendly manner.
Would it not be easier to see one basic overview record for “Jane Eyre” and choices for
versions and availability rather than a long list of records of different editions of Jane Eyre
with not much information on the initial hit list page to differentiate them?
U.S. edition (Random House)
British edition (Hodder & Stoughton)
These are manifestations of the regular print expression
Large print editon (Thorndike Press)
Large print editon (Chivers Press)
These are manifestations of the large print expression
Book on CD (Macmillan Audio)
Book on CD (Blackstone Audiobooks)
These are manifestations of the sound recording expression
15. 15
Here is an example of what this might look like in an online catalog. VTLS’s Virtua
system
16. What is FRAD?
Functional Requirements for Authority Data
Like FRBR it is a conceptual Model
◦ Provide a clearly defined structured frame of reference
for relating the data that are recorded in authority
records to the needs of the users of those records
◦ Assist in an assessment of the potential for international
sharing and use of authority data both within the library
sector and beyond
◦ Framework for Group 2 entities in FRBR
FRBR defines person as “An individual, presumably human,
living or dead.
16
Functional Requirements for Authority Data
Like FRBR it is a conceptual Model
FRAD’s purpose is to
(1) Provide a clearly defined structured frame of reference for relating the data that are
recorded in authority records to the needs of the users of those records
(2) Assist in an assessment of the potential for international sharing and use of authority
data both within the library sector and beyond
Like FRBR, FRAD models describe the relationships and connections in our bibliographic
universe that in
turn can be used to design systems that will enable users to navigate through this universe
to things they need or may like to know about.
FRAD is the framework for Group 2 entities in FRBR.
17. RDA: Describe an entity associated
with a resource (a person, family,
corporate body, concept, etc.)
find
identify
clarify
understand
Based on the user tasks defined in IFLA Working Group on Functional
Requirements and Numbering of Authority Records (FRANAR),
Functional Requirements for Authority Data: A Conceptual Model
(RDA Toolkit, Introduction) 17
The data created using FRAD to describe an entity associated with a resource (a person,
family, corporate body, concept, etc.) are designed to assist users performing the following
tasks: *
find—i.e., to find information on that entity and on resources associated with the entity
identify—i.e., to confirm that the entity described corresponds to the entity sought, or to
distinguish between two or more entities with similar names, etc.
clarify—i.e., to clarify the relationship between two or more such entities, or to clarify the
relationship between the entity described and a name by which that entity is known
understand—i.e., to understand why a particular name or title, or form of name or title, has
been chosen as the preferred name or title for the entity.
18. FRAD: Designed for 2 groups of users:
1. Authority record creators who create and maintain
authority files
2. End-users who interact with authority data, directly or
indirectly through controlled access points in bibliographic
records
◦ Find
◦ Indentify
◦ Contextualize
◦ Justify
(Patten, 2007, p. 22) 18
Like FRBR, the FRAD model also defines user tasks and maps the entities, attributes and
relationships to those user tasks. The IFLA working group has defined two groups of
users:
(1) Authority record creators who create and maintain authority files (Catalogers!)
(2) Users who use authority information either through direct access to authority files or
indirectly through the controlled access points(authorized forms references, etc.) in
catalogs, national bibliographies, other similar databases, etc. (Everybody else!)
19. What makes FRAD better than
what we already have?
A short history borrowed from Ed Jones…
19
What makes FRAD better than what we already have? (From the – if it ain’t broke, don’t
fix it camp)
A short history borrowed from Ed Jones…
Yes – that is his real name
20. Authority records in a card catalog
The system guided the user to the resource
The system anticipated the user’s missteps
The user couldn’t make a typo
The user got exercise
The system was carbon-neutral
Jones, Ed. FRAD : A Personal View, ALA
Annaheim, 2008)
20
There were some real benefits to the card catalog.
[read slide]
On the other hand, while users didn’t have to know the cataloging rules, they did need to
know the filing rules—there was no keyword searching
How has the card catalog worked online?
21. Online, the card catalog doesn’t work
so well
Jones, Ed. FRAD : A Personal View, ALA
Annaheim, 2008) 21
Umm…
This is the result of the same search strategy online
Actually, I’ve given the user the benefit of several doubts here: He didn’t look under
“Department” and he somehow avoided making a typo
The problem is he looked under the full heading in English, and the system assumed he
would look only under the first element—the name of the university—like in a card
catalog
So he’s plopped down in limbo
We’ve developed some work-arounds in our OPACs, but I wanted to show that our
authority records are still optimized for the card catalog
22. Bibliographic entities, names, and
controlled access points
Džo Šmo (person)
◦ Džo Šmo (name)
Šmo, Džo (controlled access point)
Džo Šmo (controlled access point)
◦ Josef Schmo (name)
Schmo, Josef (controlled access point)
Josef Schmo (controlled access point)
◦ Joseph “Jojo” Chmeau (name)
Chmeau, Joseph (controlled access point)
Chmeau, Jojo (controlled access point)
Joseph “Jojo” Chmeau (controlled access point)
Jones, Ed. FRAD : A Personal View, ALA
Annaheim, 2008) 22
Ed used this slide to jump into his next section (he goes into undifferentiated names next –
let’s not go there) – I threw it up on the screen because I found it amusing – but it does
serve a point – it shows the FRAD structure. Unless of course you would rather I explain
it this way (next slide)
We’re used to just seeing the controlled access points
Here is the person Joe Schmoe
And here are 3 names
There’s the one in whatever language and script he wrote in, and there are the two used on
the German and French translations. According to Ed, in France, he was very popular and
affectionately known as “Jojo”
23. I’m going to ignore this – it’s
scary …
Jones, Ed. FRAD : A Personal View, ALA
23
Annaheim, 2008)
This is from a really nasty section called “Authority Records in the Library Sector” of the
FRAD manual
I’m going to ignore this – it’s scary
(Back up one slide)
24. Conclusion
As the FRBR conceptual model has
encouraged us to look at bibliographic
records in new ways, so the FRAD model
encourages us to look at authority data in
new ways
Like libraries, these conceptual models
are growing organisms
Jones, Ed. FRAD : A Personal View, ALA
Annaheim, 2008)
24
Don’t get excited – this is only the conclusion for FRAD. Ed says: This is my conclusion,
because people expect conclusions. I agree with Ed.
25. RDA
Where is my RDA suit?
Why do you need it?!
(With apologies to Frozone)
25
Where is my RDA suit?
Why do you need it?!
Why do we need a new standard? For that matter do we need standards? Ask any of our
students and they will tell you that you can find anything you want through Google.
Google is in effect a great big online Union catalog – do we want them setting the
standard? I don’t think so. Here is my take on cataloging standards and why we need
them – and yes – there will be a defense of catalogers included. As a matter of fact – let’s
start there.
26. Jesse Shera's Two Laws of
Cataloguing:
Law #1 No cataloguer
will accept the work
of any other
cataloguer.
Law #2 No cataloguer
will accept his/her
own work six months
after the cataloguing.
University of Illinois, Graduate School of
Library Science. Dec. 1977.
LeGrow, RDA is on the Way
26
I laughed out loud when I first saw this slide – but as I was working out this presentation it
occurred to me that there is a lot of truth in both statements – but there is a reason as well.
The information world is spinning at a tremendous rate and along with it the standards are
changing at a tremendous rate of speed just trying to keep up.
In the next sequence of slides I will attempt to illustrate for you what this has translated to
in my mind as I have labored to draw all of this together in a coherent fashion. It’s all
related.
27. This is a cataloger’s brain ….
27
This is a catalogers brain – slighty cracked – but sunny and fresh
28. This is a cataloger’s brain on
AACR2
28
This is a cataloger’s brain on AACR2
Flat file structure – a tad crusty around the edges
29. This is a cataloger’s brain on
RDA
29
This is a cataloger’s brain on RDA – scrambled, but if you look hard enough there is a
pattern to it – and note how the egg white and the yolk have melded into a tasy morsal, and
how the pepper adds definition, making it more palatable to the user – it’s all about
relationships!
30. Jesse Shera's Two Laws of
Cataloguing:
Law #1 No cataloguer
will accept the work
of any other
cataloguer.
Law #2 No cataloguer
will accept his/her
own work six months
after the cataloguing.
University of Illinois, Graduate School of
Library Science. Dec. 1977.
LeGrow, RDA is on the Way
30
According to Richard Murray in an article titled “The Whimsy of Cataloging” - The
stereotype of the cataloger is, for many, the hermit hiding in the bowels of the library
shackled to an OCLC terminal all day, counting pages of plates and measuring the heights
of books. On the rare occasion he or she is let out of the dungeon, it’s to be the one at
meetings who speaks in unintelligible MARC-ese about “non-filing characters” and
“second indicator blank” and “space colon space.” The cataloger’s role in the library is to
enforce rules that nobody understands and to make things as difficult as possible for
everyone involved. Right?
I confess, I do nothing to try to belay that stereotype (it’s fun to mess with the reference
librarian’s minds).
Feb 2002, LIScareer.com
Career Strategies for Librarians
31. Library Journal, October 15, 2002
MARC Must Die By Roy Tennant, Manager,
eScholarship Web & Services Design, California Digital Library.
31
When MARC was created, the Beatles were a hot new group and those of us alive at the
time wore really embarrassing clothes and hairstyles. Computers were so large, complex,
and expensive that it was ludicrous to think that you would one day have one in your
home, let alone hold one in the palm of your hand. Although age by itself is not necessarily
a sign of technological obsolescence (how much has the wooden pencil improved in the
last 40 years?), when it comes to computer standards it is generally not a good thing.
The very nature of the MARC (machine-readable cataloging) record is, to some degree, an
anachronism. It was developed in an age when memory, storage, and processing power
were all rare and expensive commodities. Now they are ubiquitous and cheap.
Kelley is a bit more respectful of MARC and less likely to have Henrietta Avram twirling
in her grave. She says MARC was a brilliant, visionary solution in its day, but it was
conceived in different times when the limits of what technology could do were much more
confining. MARC was designed for an environment where data storage was very, very
expensive and data was read linearly from tapes.
32. There ‘s No Catalog Like No Catalog –
LITA ALA Annual 2008
The library catalog is the greatest repository
of the most “anal retentive, obsessive-
compulsive” activity” … ever seen.
Anal-retentive, obsessive-compulsive is good
for airplane mechanics, carpenters, lawyers,
and doctors – but catalogers?
Why do cataloger’s have these standards?
to save our libraries and our users time and
money
(Weinheimer 2010, 188-189) 33
There are some in the Library world that advocate dumping the catalog altogether. At a
session titled – There’s no catalog like no catalog at ALA annual in Anaheim in 2008,
One panelist said that the library catalog is the greatest repository of the most “anal
retentive, obsessive-compulsive” activity” that he has ever seen
James Weinheimer goes on to say that the
Response from audience was embarrassed laughter (although none of the catalogers I was
there with showed the slightest bit of amusement) but led the author to believe that there
was some sort of general agreement that anal-retentiveness in cataloging was a bad thing.
He goes on to make the case that though he sympathizes with the viewpoint, blind
adherence to standards is not always such a bad thing, he cites airplane mechanics and
home builders as 2 examples. And continues that while medicine and law are two more
examples where compliance with standards is a good thing, the same can’t be said of
catalogers – can it?
Legal and health professionals rely on research found through bibliographies and catalogs,
and as a result they rely on those who prepare these items to make sure that they are up-to-
date and accurate. Errors in information retrieval for a physician or lawyer can put their
clients at risk.
33. Why do catalogers have these standards? Job security? Secret society? – According to
Weinheimer (and Barbara Tillet and the JSC) The reason we have these standards is to
save our libraries and our users time and money
(Weinheimer 2010, 188-205)
Pop quiz:
6 p. L., [17]-274, [1] p. incl. front., illus. 22 cm.
274 p. : ill. ; 22 cm.
274 pages : illustrations ; 22 cm.
How many cataloger’s does it take to change a
lightbulb?
(Weinheimer 2010, 189-190) 34
Pop quiz: what does this mean
|a 6 p. L., [17]-274, [1] p. |b incl. front., illuse. |c 22 cm.
What is the point? This is an example of highly complex pagination and illustration data
from the physical description field of the MARC record. In the early days of cataloging
people would include blank pages, the beginnings and endings of pg. Sequences and so on.
AACR2 simply cites the final page of each sequence of pages.
Weinheimer asks the question – why as a cataloger does he care how the pagination is
recorded and his answer is – he doesn’t care about the minute details of the rules – as long
as we are all playing by the same rules. He goes on to point out that when he goes to
catalog a new item – he will check the bibliographic details of existing items in the catalog
to make sure he isn’t re-inventing the wheel when he only needs to add a copy to the
holdings.
34. Weinheimer’s conclusion:
Library cataloging can provide one thing,
and one thing alone, that automatic
means cannot, at least not yet: and that
is quality. Quality means that some kinds
of standards are followed, and that
someone using a product that follows
those standards, … can safely rely on it.”
(Weinheimer, 2010, pg. 203)
35
Weinheimers conclusion: “When it comes to metadata libraries cannot provide more,
faster, or cheaper metadata in comparison to automatic production because computers can
provide such information in quantities and at speeds that humans cannot hope to challenge.
Library cataloging can provide one thing, and one thing alone, that automatic means
cannot, at least not yet: and that is quality. Quality means that some kinds of standards are
followed, and that someone using a product that follows those standards, whatever that
product happens to be – traveling safely in an airplane, or eating Chicken that is free of
disease, or drinking water that is clean -- can safely rely on it.”
35. 36
I’m going to pick on my own catalog here – it’s a work in progress – to point out the
importance of reliable description and access in this case authority control – between this
slide and the next it makes it pretty clear that basing the authors name on how it appears in
the text is not good enough.
A search on Mark Twain shows that there are 412 records that match that criteria in the
keyword search. Of those 412 records 291 records are for the author Mark Twain. None
of these records link to Samuel Longhorn Clemons.
36. 37
A search on Samuel Clemens brings up 10 records with the Author Mark Twain and 3
records under Samuel Clemens. Where did the other 281 records go and why didn’t these
3 show up under a search for Mark Twain?
Weinheimer further concludes that these traditional library tasks of description and access
may be accomplished using completely different methods than those we use today.
Enter FRBR, FRAD and RDA!
37. If you can find it
in a library,
thank a cataloger!
Cataloging codes describe resources in a predictable
consistent way
The codes build a database that shows our users the
organization that we provide to make it easier to find
what they are looking for, and to show them related
resources in our collections and beyond.
This service to our users is our reason for existence
as libraries and builds on a long tradition of
organizing information
(Tillett, 2007)
38
So - If you can find it in a library thank a cataloger!
In an article titled "High-tech heretic : why computers don't belong in the classroom
and other reflections by a computer contrarian" by Clifford Stoll he says
"Computerized search engines are no substitute for a well-cataloged library. Library
catalogers -- perhaps the least thanked of a seldom thanked profession -- add value to
already valuable information. Like indexers, they classify, categorize. And like indexers,
theirs is a job that's perceived as easily automated. It ain't so. The cataloger interprets.
Looks for meaning. Provides context, cross-references, weaves diverse threads into easily
seached end terms."-- From "High-tech heretic : why computers don't belong in the classroom and other
reflections by a computer contrarian" by Clifford Stoll. Page 191 Doubleday 1999. ISBN 0385489757
Cataloging codes provide instructions to catalogers so they can describe resources
in a predictable consistent way
The codes build a database that shows our users the organization that we provide to
make it easier to find what they are looking for, and to show them related resources
in our collections and beyond.
This service to our users is our reason for existence as libraries and builds on a long
tradition of organizing information
38. The Catalog
Then –
Emphasis on Books and
other printed materials
In-between -
Microforms, Audio tapes, LP’s video tape,
CDs, DVDs, etc.
Now -
Computer technology
Electronic documents
Streaming audio & video
MP3 & MP4 file formats
Future –
Who knows ….
To infinity … and beyond! 39
The Catalog
-- development of computer technology and electronic document production presents a
significantly different challenge than libraries had only fifty years ago
-- information resources and the libraries that held them still rooted in the era of books and
periodicals
-- the card catalog was the entry point to the library's physical holdings.
early cataloging rules, dating back to the catalog of the British Museum in 1841, evolved
primarily to handle textual, published resources and rules were developed for linear
presentation, either in printed book catalogs or in alphabetically arranged card catalogs
Headings, in alphabetical order, were once the only access points into the catalog.
The effect of computers and networks of information resources on the mission of libraries
is still being debated, but the very existence of libraries in the future rides on their ability
to respond to today's – and tomorrow's – technology.
39. In 2007 Arlene Taylor wrote that she believes that the solution to the lack of order found in
our current catalogs, with the effect of making it difficult for users to sort out what is
available in the way of versions of a work and other resources related to that work =
Combination of 3 things
Accept principles espoused by FRBR
Construct rules for creating cataloging and other metadata based on this model (RDA)
Design systems that will display metadata based on this model
Here are some examples of systems based on the FRBR model
WorldCat
40
* OCLC’s WorldCat – notice the search facets at the side
40. 41
VTLS’s Virtua system – This is our catalog from GCU and notice some of our search
facets – we have had requests from our ground students to be able to search by the physical
form alone.
41. 42
VTLS’s Virtua system - here is another view of a VTLS SaaSP* catalog
*Software as a Service
44. 45
This one is my favorite as a FRBRized example:
OLAC’s (Online Audio-visual catalogers) FRBR-inspired prototype audio-visual
“discovery interface” http://blazing-sunset-24.heroku.com
45. 46
This slide shows how using FRBR, libraries can inform the users of versions of that
resource on in multiple languages or editions, related resources, works by same creator,
same subject, etc.
And still provides surrogate to lead users to resources not yet available online, fulfilling
the old role of that catalog as well as the new
OLAC’s (Online Audio-visual catalogers) FRBR-inspired prototype audio-visual
“discovery interface” http://blazing-sunset-24.heroku.com
46. The Role of the Library as an
extension of the mind Vinod Chachra,
Ph.D. http://www.vtls.com/media/en-
US/audio/Library_extension_of_mind.mp3
Also available through:
Download Vinod Chachra-The Role of the Library as an
Extension of ...
www.mp3gangster.com/mp3/idc3c49e
3 technologies that represent a million fold multiplication
1. Communications technology
2. Nuclear energy
3. Computers
Computers + communications technology
(Chachra, 2006)
47
Technological advancements can be measured by the multiplier by which human being become
more productive through the use of certain objects
• Technological advancements which have huge impacts are called revolutions
• There where 2 major influences on the Agricultural revolution – 2 factors,
• (1) the invention of the plow and
• (2) the use of chemical fertilizers (100 fold multiplier)
• Industrial revolution - Steam engine (1000 fold multiplier)
• There are 3 technologies that represent a million fold multiplication
• communications technology – wire, wireless etc
• Nuclear energy – don’t yet understand full capabilities
• Computers
The evolution of technologies took a major turn with the creation of the Internet. computers +
communications technology = Million multiplication of a million multiplier.
Library systems developers have worked hard to create a machine-readable library catalog that
provided functionality beyond that of the analog card catalog (i.e., MARC), for instance by
allowing keyword searching of all data in the catalog record. However, the struggle to
accommodate technological change with data created using the old rules is clearly not optimal,
and hinders the ability of libraries to create innovative services.
47. Libraries – designed to remove barriers
Spatial barriers
Temporal barriers
Financial barriers
Intellectual barriers
New barriers
• Discipline independence in a multi disciplinary
world
• language in a global world
• Is literacy necessary in a multi-media world?
(Chachra, 2006)
48
Libraries – originally designed to remove barriers
• Spatial barriers – meeting places
• Temporal barriers – don’t need to live during time of author to take advantage of their
knowledge
• Financial barriers – equality of access
• (new rule) Intellectual barriers
New barriers
• Discipline independence in a multi disciplinary world – no matter how much we
learn about one discipline
there will always be some discipline we know nothing about
• language in a global world – knowledge not limited to any single language –
should not be
necessary for us to learn another language in order to cope with the information
• Is literacy necessary in a multi-media world – still need a medium of exchange –
need to look
for solutions and systems that become literacy independent (shouldn’t have to learn exotic
language in to have access to information)
48. • Differences between computers and people
(John Gale):
• People learn through inference
• Human memory fades – computers never forget
• Human memory is limited – not so for computers
• Humans can visualize – computers pretend to
visualize
• Humans learn through inference and association
leveraging what they learn
• Computers are deterministic – people are
probabilistic
(Chachra, 2006)
49
Contrast development of computers with people – develop in opposite ways, the opportunity of
combining the best of these two things.
Symbiotic relationship between computers and people. We are more and more dependant.
John Gale sums it up this way:
• Differences between computers and people (John Gale):
• People learn through inference (accessive learning) (which doesn’t happen
in computers yet) and association (imbedded in links)
• Human memory fades – computers never forget
• Human memory is limited – not so for computers (supposedly)
• Humans can visualize – computers pretend to visualize (though that is
changing … HAL)
• Humans learn through inference and association leveraging what they learn
– computers are starting to do this but not as quickly
• Computers are deterministic – people are probabilistic
• Human memory is like Data
• Software can be considered an encoding language
• In what way is software similar or different from human DNA
49. Systems must interconnect and data must expose itself –
need to know the content of repositories or databases
before you start using it
New System Design Considerations
Different languages have different scripts and different
encoding schemes
Indexing and searching tools (like Google) have been
written using the Latin alphabet
Tools and Rules are still the answer
Create high quality data based on how we want the data to
be visualized
(Chachra, 2006)
)
50
The Challenge is to create computer systems that take the best advantage of capabilities of
Humans and combine them with best capabilities of computers to bring about systems
which allow computers to become an extension of the human mind
Simplify processes so extensive training is not necessary (This is something that VTLS has
been working at diligently in their system design)
Systems must interconnect and data must expose itself – need to know the content of
repositories or databases before you start using it
- Different languages have different scripts and different encoding schemes
- Indexing and searching tools (like Google) have been written using the Latin
Alphabet
- Creates a problem for non-Latin languages because they don’t work
- Employing it for different languages is very difficult
50. - for ex. Thai has no spaces between words – how do you search it? – most
search engines depend on word searches – have to create artificial spaces
Exposing data
How do we organize the worlds organization and how do we visualize depth and content
of data
Google can be described as one big virtual Union Catalog – best model for organizing the
world’s information – not really –
why? No standardization – search of FRAD first time on iPhone brought up Fraud. As
Vinod pointed out earlier computers do learn – when I was writing this and tried the search
on my work computer I got FRAD, FRBR, FRBR blog (along with a YouTube video of 7
minutes of totally inane junvenile commentary called FRAD goes to school, which I
believe to be another cry for standards!)
Humans don’t want entire dataset – smaller manageable content ( I experienced this to an
extent while putting together this presentation – I started out with 515 slides and more
information that I haven’t even had time to look at.)
One answer to this problem is visualization by segmentation (facets?) exposure – shows
what is in the collection without having to create a complicated search (Chamo – get some
screen shots from our catalog)
The answer to the information glot is still Tools and Rules (give user a lot of tools, create
software that enforces the rules)
Then we the catalogers need to create high quality data based on how we want the data to
be visualized
51. That being said …..Standing still with
AACR2 is not an option if libraries are
to remain viable.
If not AACR then what?
51
We’re at a crucial time for the development of new information systems, more global in
nature, more Internet oriented, that can make cataloging easier and make the results of
cataloging much more flexible and useful to our users. The Challenge is to create
computer systems that take the best advantage of capabilities of Humans and combine
them with best capabilities of computers to bring about systems which allow computers to
become an extension of the human mind
52. RDA
Resource
Description &
Access
1
Resource Description and Access, is designed to help us transition to the technological
capabilities of the Internet, today and into the future by having us identify the entities and
relationships at the element level that machines can use better than they have been able to
in the past in our MARC records.
RDA was originally named AACR3, but after further thought, in order to achieve many of
its goals the title Anglo-American Cataloging Rules was abandoned and a more global
view was taken, which led to the title Resource Description and Access
From the start it was meant to build on the Anglo American cataloging traditions, the
conceptual models of FRBR and FRAD and the International Cataloging Principles (Tillet
2007, 88) The concepts in RDA are not new concepts – they are simply a new view of
traditional cataloging. A new way of looking at the bibliographic universe, using
vocabulary that we hope system designers and future generation of librarians will
understand. (Tillett, 2007, 88)
53. What RDA will NOT do…
RDA will have NO influence on presently used
classification schemes
RDA will not change the creation of records at the
manifestation level
Not a display standard (as is AACR2)
◦ Does have appendix D for ISBD and appendix E for
AACR2 style for access points
Not an encoding standard
◦ Use whatever schema you prefer (MARC 21, Dublin
Core, etc.)
53
Let’s start again with what it is not:
-- RDA will have NO influence on presently used classification schemes. If your library
used Dewey yesterday – it will still use Dewey tommorrow. The same for LC, NML or
any other classification scheme your library may be using.
-- RDA will not change the creation of records at the manifestation level but the structure
of the new code will be affected by the FRBR user tasks
RDA is not an encoding system or a presentation standard for displays. It is schema-
neutral. In other words, it doesn’t tell you how to dress up your data or how your data
should communicate – it simply tells you what data is should be recorded to be effective
54. What are the intended benefits of
RDA for libraries and the
communities they serve?
Rules that are designed to be more flexible and
more usable across information communities
Rules that are a better fit with emerging
technologies, especially sharing data with the
publishing community
Rules that can support an improved discovery
experience
RDA is designed to take advantage of the efficiencies and flexibility in data capture,
storage, retrieval, and display made possible with new database technologies, but to be
compatible as well with the legacy technologies still used in many resource discovery
applications.
OCLC describes the intended benefits
Rules that are designed to be more flexible and more usable across information
communities
Rules that are a better fit with emerging technologies, especially sharing data with the
publishing community
Rules that can support an improved discovery experience
I thought we did away with Rules ….
55. RDA provides a set of guidelines and
instructions on formulating data to
support resource discovery. (RDA Toolkit,
Introduction)
FRBR: FRAD:
Find Find
Identify Identify
Select Contextualize
Obtain Justify
• ICP’s highest principle =
“convenience of the user”
55
It’s more like a guideline.
RDA provides a set of guidelines and instructions on formulating data to support resource
discovery.
FRBR provides the conceptual foundation for RDA
RDA includes the FRBR terminology Example: the names of bibliographic
entities: “work”, “expression”, “manifestation”, and “item”)
Responding to those user needs coincides with the main principle stated in the Statement
of International Cataloguing Principles: convenience of the user.
RDA is a set of practical instructions built on the foundation of a theoretical
framework/model
data that responds to user needs
accurate data
precise data
usable data
visible data
a standard with an expanded scope
56. RDA based on IFLA’s
international models and
principles
Functional Requirements for
Bibliographic Records (FRBR; 1998)
Functional Requirements for Authority
Data (FRAD; 2009)
Statement of International Cataloguing
Principles (ICP; 2009)
RDA Essentials (Kuhagen, Nov. 2010)
56
RDA is based on two international conceptual models, FRBR and FRAD, developed by
working groups of the International Federation of Library Associations and Institutions
with worldwide input and review. A third model for subject data (FRSAD) has just been
published; subject data chapters will be added to RDA in the future.
Intended to be a set of instructions for the content of descriptive metadata
Bibliographic record
Authority record
Other data structures
Standard for the web environment
57. Why are the models important?
Broad international support for the explanatory power
of the models
common international language and conceptual
understanding of the bibliographic universe
as the foundation for a standard:
• easier to apply in international context
• easier for our data to interoperate with other data
generated on the basis of a FRBR/FRAD
understanding of the bibliographic universe
[Oliver, 2011]
57
According to Chris Oliver, there is Broad international support for the explanatory power
of the models and the models provide a common international language and conceptual
understanding of the bibliographic universe as the foundation for a standard:
easier to apply in international context
easier for our data to interoperate with other data generated on the basis of a FRBR/FRAD
understanding of the bibliographic universe
Focus on local user needs
Choice of agency preparing the description:
Language of additions to access points
Language of supplied data
Script and transliteration
Calendar
Numeric system
58. RDA in Europe: making it happen! (8 Aug 2010, Royal Library,
Copenhagen)
Countries represented
Austria
Belgium
Canada
Croatia
Cyprus
Czech Republic
Germany
Iceland
Ireland
Italy
Netherlands
Norway
Palestine
Poland
Spain
Sweden
Switzerland
Tunisia
United Kingdom
USA
58
The next 2 slides give you an idea of the kind of international support that exists for RDA.
International interest in the
subject of cataloguing
59
This slide is from Lynne LeGrow’s presentation RDA is on the Way.
59. Wider scope
of resources
Response to what’s being acquired in libraries
◦ More elements for non-printed text resources
◦ More elements for non-text resources
◦ More elements for unpublished resources
Compatible with specialist manuals (DACS,
CCO, DCRM(B) etc.)
RDA Essentials (Kuhagen, Nov. 2010)
60
RDA also covers the wider scope of resources being acquired in libraries today. RDA for
general libraries is compatible with specialist manuals for various categories of resources;
the JSC (the Joint Steering Committee for Development of RDA) consulted with those
specialist communities during the development of RDA.
Expanded scope
not just for libraries anymore!
-- It connects libraries with other cultural heritage communities
e.g. additions and changes for archives
-- instructions designed to describe a wide variety of resources & the possibility for other
communities to adopt/adapt
- release from MARC 21 record format also helps build connections to other communities
- awareness of practices and standards in other metadata encoding communities
60. Importance of relationships
Categories:
◦ Persons/families/corporate bodies to
resources
◦ Resources to other resources
◦ Person/families/corporate bodies to other
persons/families/corporate bodies
RDA Essentials (Kuhagen, Nov. 2010)
61
Providing relationships is important to meeting the needs of users to tell them what else
connected to one resource in some way also exists and is available. RDA supports the
clustering of bibliographic records to show relationships between works and their creators
to make us more aware of the work's different editions, translations, or physical formats.
There are many types of relationships. Those relationships can be explained by the use of
relationship designators found in three of the RDA appendices.
Examples: relationship terms
artist abstract of (work)
etcher choreography for
sponsoring body (work)
composer concordance to (work)
translator screenplay (work)
editor of compilation sequel
interviewee finding aid
photographer (expression)
cartographer libretto (expression)
director; producer mirror site
former owner reproduced as
performer descendants
enacting jurisdiction founder
employer
62
61. RDA: A Response to change
Changes in technology
◦ Impact on descriptive/access data
book catalogs
card catalogs
OPACs
next generation
Move from classes of materials to
elements and values (more controlled
vocabularies)
Move from individual library to
international audience
RDA Essentials (Kuhagen, Nov. 2010)
63
RDA is designed for the digital environment. As with other cataloging codes before it,
RDA reflects both the technology of the time and the types of materials that we are
organizing, describing, and making available to our users. RDA provides guidelines on
cataloguing digital resources and will improve searching and browsing for users
One of the most significant changes from AACR2 is the move in RDA from AACR2’s
class of materials concepts to identifying elements needed to describe things in order to be
more useful on the Web – we will be moving beyond the library-centric MARC Format to
new ways to share linked data over the Web.
RDA recognizes that the value of cataloging data is moving from just an individual library
to an international audience.
62. Ch-ch-ch-ch-ch-changes…
What’s Different – what’s the same
Oh where, Oh where have my
LCRI’s gone?
LC’s decisions in Library of Congress Policy
Statements (LCPSs) available in the RDA Toolkit
and as pdfs at
http://www.loc.gov/catdir/cpso/RDAtest/rda_lcps.h
tml
64
Ch-ch-ch-ch-ch-changes…
A whole lot of changin’ goin’ on here
Lets start with LCRI’s – they are now called Library of Congress Policy Statements
More new terms comin’ up
63. AACR2 to RDA vocabulary
GMD media type +
carrier type +
content type
preferred sources
Chief source
Heading, Main entry,
Added entry, Authorized Access point
heading
See references Authorized access point
Uniform title Variant access point
Elements Preferred access point
FRBR attributes
65
The GMD, often an inconsistent presentation of different categories of information, has
been replaced by three elements: media type, carrier type, and content type. We’ll look at
them later in this section.
also note that the change is not only in the term but also that the sources for information
have been expanded from a single source to multiple sources.
Also – we seem to have a pattern emerging in the new vocabulary. It’s all about access!
RDA Essentials (Kuhagen, Nov. 2010)
64. ICP representation principle
Transcribed information = “Take what
you see” and “accept what you get”
General guideline at RDA 1.7.1 addresses transcription of what is on
the resource:
◦ Capitalization: follow appendix A or accept found form
◦ Punctuation, abbreviations, inaccuracies, symbols, initials,
numbering: generally follow what is on source
Hairboutique.com
66
The International Cataloging Principals principle of representation underlies the change
from AACR2 generally not to alter what is on the resource when transcribing information.
“Take what you see” has becomes our motto. RDA Essentials (Kuhagen, Nov. 2010)
Most catalogers don’t like this idea.
I was thinking what if Marie and Debra Barone were catalogers (Loosely based on episode
Humm Vac (#5.18) (2001))
Debra Barone: A clean catalog is not the most important thing in the world.
Marie Barone: You know who says that? A messy person.
RDA Essentials (Kuhagen, Nov. 2010)
65. Punctuation and Capitalization
AACR2 dictated that certain marks of
punctuation (such as ellipsis) should be
replaced with other marks of punctuation.
RDA specifies that punctuation should be
transcribed exactly as it appears
AACR2 rules of capitalization no longer
apply
RDA specifies that capitalization should be
transcribed exactly as it appears
67
Could this lead to …..
Capitalization choices
Accepting found capitalization:
245 10 $a Cairo : $b THE CITY VICTORIOUS /
$c Max Rodenbeck.
250 ## $a FIRST VINTAGE DEPARTURES EDITION.
Changing found capitalization:
245 10 $a Cairo : $b the city victorious /
$c Max Rodenbeck.
250 ## $a First Vintage Departures edition.
RDA Essentials (Kuhagen, Nov. 2010)
68
THIS?!!!!
Shown here are two versions of four transcribed elements: the first with capitalization as
found on the resource, the second with capitalization adjusted according to the guidelines
in appendix A. The use or not of uppercase letters does not affect searching and retrieval;
many Web applications use uppercase letters.
Also note that not adjusting words such as “first” to a numeral and “edition” to an
abbreviation are examples of transcribing what you see.
66. Correcting found errors?
Principle of representation (RDA 2.3.1.4):
◦ Don’t correct errors in titles proper of
monographs = no more “[sic]” or “[i.e., ___ ]” –
give note (246 field in MARC) to explain
◦ Do correct errors in titles proper of serials and
integrating resources to have a stable title
◦ Don’t correct errors in other transcribed
elements; give note if considered important
RDA Essentials (Kuhagen, Nov. 2010)
69
The “take what you see” principle applies to errors in transcribed elements.
With RDA we will use square brackets only for information not found in the item,
regardless of source within the item.
With RDA "[sic]" or bracketed additional letters will no longer be used after typos. Create
246 with corrected title spellings.
We will continue to correct errors in titles proper of serials and integrating resources to
have a stable title.
Use cataloger judgment to give a note and/or an access point if important.
67. An odd bit of punctuation …
When an element ends with an abbreviation followed by
a full stop or ends with the mark of omission and the
punctuation following that element either is or begins
with a full stop, include the full stop that constitutes or
begins the prescribed punctuation.
AACR2 = 250 $a 3rd ed.
RDA = 250 $a 3rd ed..
Note: This example assumes that the edition statement appeared on
the prescribed source as “3rd ed.”
AACR2 1.0C1 says 250 $a 3rd ed.
RDA = 250 $a 3rd ed..
Note: this is not a change initiated by RDA; appendix D reflects a change in ISBD as of
the consolidated edition.
68. Statement of Responsibility
245 00 / $c Sean Markey ... [et al.].
245 10 / $c Sean Markey, John T. Pierce,
Kelly Vodden, and Mark Roseland.
Option:
[and three others].
245 10 / $c edited by Ronald W. Waynant ; foreword by the late
Dr. Leon Goldman.
245 10 / $c by the Reverend R.M. Dickey ; edited by Art
Petersen.
Statement of responsibility taken from title page verso
24510 / $c by Edward J. Gregr and Ryan Coatta.
(Look Mom! – no brackets!)
Schiff, 2010 71
In RDA, The ‘Rule of Three’ has been made optional.
(The more access the better!) (Le Grow)
In AACR2 1.1F7. Include titles and abbreviations of titles of nobility, address, honour,
and distinction, initials of societies, qualifications, date(s) of founding, mottoes, etc., in
statements of responsibility IF and then it goes on to give a list of what can be used
Otherwise, omit all such data from statements of responsibility. Do not use the mark of
omission.
RDA says transcribe what you see
No more brackets in the statement of responsibility as long as it is somewhere on the item!
70. Try to supply a probable date whenever possible because not doing so starts a chain
reaction of identifying other dates and it’s easier to supply a probable date of publication.
If you REALLY cannot supply a probable date and you’re cataloging a single-part
monograph, then give the explanation “[date of publication not identified]”.
The last element to be discussed that is encoded in the MARC 260 field is the Copyright
date. In RDA it is not a type of Date of publication; it is a separate element. To identify it
in the 260 $c, precede it with the appropriate symbol.
Identifying a person
Definition (RDA 8.1.2) = “An individual or
an identity established by an individual
(either alone or in collaboration with one or
more other individuals)”
RDA 9.0: Includes fictitious entities
(change from AACR2)
◦ Miss Piggy, Snoopy, etc. now in scope if
presented as having responsibility in some way
for a work, expression, manifestation, or item --
not just as subjects
RDA Essentials (Kuhagen, Nov. 2010)
74
And finally – I want to talk a little more about new changes in RDA – that is – Authority
Data. We talked about some of this when we went over FRAD – so I promise to be brief.
In RDA a person can be an individual or an entity established by one individual alone or
an identity established in collaboration with one or more other individuals.
I am going to touch briefly on some new things in
The scope statement at RDA 9.0 includes fictitious entities as persons, a change from
AACR2. So, they can now be represented by authorized access points as creators or
whatever role they play if they are presented on the resource as being responsible in some
way.
71. 1+ creators: always one in
MARC 1XX
RDA:
100 $a Brown, Susan.
245 $a Physics / $c by Susan Brown, Melanie
Carlson, Stephen Lindell, Kevin Ott,
and Janet Wilson.
AACR2: no 1XX field if more than three entities.
75
In AACR2 if there were more than 3 or if the first named individual was an editor there
would be no 1XX field – straight to 7XX
With AACR2 if the work has more than 3 authors, or if the work has 3 authors
AND has a collective title, then we use
TITLE MAIN ENTRY.
With RDA the first author gets the main entry (regardless of how many)
72. Relationships are important
When tracing names in 700 tags we will be using
relator terms. (input in a subfield e)
These relator terms will be spelled out and not
input as abbreviations as they are now.
Examples:
700 1 $aSmith, Chester.$esinger
700 1 $aDouglas, Keith.$econductor
700 1 $aManning, Ruth.$eco-author
76
Note that these are no longer abbreviated – they are spelled out. (LeGrow)
Relationship of person, family, or corporate body to resource being described
Relationship between resources
Relationship between person, etc., and another person, etc.
Can identify type of relationship via designators -- terms in RDA appendices or in other
vocabularies
Examples: relationship terms
artist abstract of (work)
etcher choreography for
sponsoring body (work)
composer concordance to (work)
screenplay (work)
translator
sequel
editor of compilation finding aid
interviewee (expression)
photographer libretto (expression)
cartographer mirror site
director; producer reproduced as
former owner
performer descendants
enacting jurisdiction founder
employer
77
73. Scope of “family”
Now considered creators, contributors, etc.
◦ Important for archives, museums, and special
collections -- may supplement RDA with
specialist manuals (e.g., Describing archives : a
content standard (DACS))
◦ Also possible for general library materials:
genealogy newsletters, family reunion
publications, etc.
RDA Essentials (Kuhagen, Nov. 2010)
78
And speaking of relations … Considering families as creators and contributors, not just
subjects, is part of expanding the application of RDA beyond libraries to other information
communities such as archives and museums.
74. Subject headings
are being
updated
Inverted headings are gradually being
changed to direct order
Example: Body, human is now Human
body
Antiquated terms are being updated to
modern jargon
Example: Cookery will change to Cooking
LeGrow, Lynne (2010). RDA is on the way!
79
655 Genre headings are used
more
Unlike 650 subject headings
which tell the user what the
material is ‘about’, genre
headings tell the user what the
material ‘is’.
Examples: 655 7 $aMystery fiction.$2gsafd
655 7 $aEssays.$2lcsh
655 7 $aFilmed operas.$2lcsh
LeGrow, Lynne (2010). RDA is on the way!
80
75. Changes in MARC 21
Can encode RDA content in any schema
but many libraries will be using MARC 21
when testing or first implementing RDA
RDA/MARC Working Group made
proposals for changes to MARC 21
RDA Essentials (Kuhagen, Nov. 2010)
81
Remember that RDA content can be encoded in any schema. For the transition to RDA,
many libraries will continue to encode their RDA content in MARC.
A joint RDA/MARC group wrote discussion papers and made proposals for some changes
to the MARC formats to accommodate some, but not all, new RDA elements.
76. Controlled values, the purpose of 3xx
fields : or what have you done with my
GMD
82
The GMD is being replaced by three new 3XX field which are controlled values for
naming the types of content (like sound, text, still images, and so on), types of carriers
(like a film reel, a computer disc, a volume), and other elements in RDA that have
controlled lists of values- they are already being registered on the Web and can be used to
present displays and show pathways to related resources.
I would be lying if I said that this comes as welcome news to a lot of people. Though to be
fair – outside of the cataloging world I don’t know how many people are actually disturbed
by this. Still there will be considerations for the users as well as catalogers and system
designers.
(Tillett, 2011)
77. Examples of the GMD
(and friends)
The sweet hereafter [videorecording] / Alliance Communications presents an
Ego Film Arts production ; a film by Atom Egoyan ; screenplay by Atom Egoyan
; produced by Camelia Frieberg and Atom Egoyan ; directed by Atom Egoyan.
Rip Van Winkle [electronic resource] : a legend of the Catskills / a
comparative arrangement with the Kerr version, by C. Burke. 1850.
Get Rich Click! : The Ultimate Guide to Making Money on the Internet [Book
on CD] By Cahill, Patrick Published: 2013
Private : #1 Suspect : #1 Suspect [Large Type] By Patterson, James/ Paetro,
Maxine Published: 2012
The fiery cross / Compact Disc, by Diana Gabaldon.
The Most fabulous classical Christmas album ever! [sound recording].
10 secrets for success and inner peace by Dyer, Wayne W.... Issued on Playaway,
a dedicated audio media player. ...
83
For those of you who do not speak cataloging the GMD is the General Material Designator
and here are some examples of what they look like in the catalog
78. Content type (RDA 6.9; MARC 336)
Scope = “fundamental form of
communication in which the content is
expressed and the human sense through
which it is intended to be perceived”
◦ “cartographic image,” “performed music,” “still
image,” “text,” etc.
For images, also whether in two or three
dimensions and presence or absence of
movement (e.g., “two-dimensional moving
image”)
RDA Essentials (Kuhagen, Nov. 2010)
84
Content type tells the user how the content of the work is expressed: what form of
communication and which human sense is used. Strangely enough it is found in the
expression record.
RDA 6.9. Content type (MARC tag 336) is a categorization reflecting the fundamental
form of communication in which the content is expressed and the human sense through
which it is intended to be perceived. For content expressed in the form of an image or
images, content type also reflects the number of spatial dimensions in which the content is
intended to be perceived and the perceived presence or absence of movement. Values:
cartographic dataset; cartographic image; cartographic moving image; cartographic
tactile image; cartographic tactile three-dimensional form; cartographic three-
dimensional form; computer dataset; computer program; notated movement; notated
music; performed music; sounds; spoken word; still image; tactile image; tactile notated
music; tactile text; tactile three-dimensional form; text; three-dimensional form; three-
dimensional moving image; other; unspecified. Each value also has a MARC code
established for it that can be used in 336 $b.
79. Media type (RDA 3.2; MARC 337)
Scope = “a categorization reflecting the
general type of intermediation device
required to view, play, run, etc., the
content of a resource”
◦ “audio,” “projected,” “microform,” “video,” etc.
Broad categories; specific types in
Carrier type (RDA 3.3)
RDA Essentials (Kuhagen, Nov. 2010)
85
Media type is a broad categorization of what type of device, if any, is needed to be able to
see, hear, etc., the content of the resource.
RDA 3.2. Media type (MARC tag 337) is a categorization reflecting the general type of
intermediation device required to view, play, run, etc., the content of a resource. Values in
RDA: audio; computer; microform; microscopic; projected; stereographic; unmediated;
video; other; unspecified. Each value also has a MARC code established for it that can be
used in 337 $b.
80. Carrier type (RDA 3.3; MARC 338)
Scope = “a categorization reflecting the
format of the storage medium and housing
of a carrier in combination with the type of
intermediation device required to view,
play, run, etc., the content of a resource”
◦ “audio disc,” “computer disc,” “microfiche,”
“slide,” “volume,” etc.
Don’t confuse with term used in Extent
(MARC 300 $a): some terms in common
RDA Essentials (Kuhagen, Nov. 2010)
86
Carrier type gives more specific information than the Media type term does about the format,
housing, and type of device needed if any.
The most important thing to remember about Carrier type is that it is a separate element from the
element Extent; Carrier type is given in MARC field 338; Extent is given in MARC 300 subfield
$a. The reason it is easy to confuse them is that some of the terms you’ll see in 300 $a are the
same as terms you’ll see in the 338 field.
RDA 3.3. Carrier type (MARC tag 338) is a categorization reflecting the format of the storage
medium and housing of a carrier in combination with the type of intermediation device required to
view, play, run, etc., the content of a resource. Each value also has a MARC code established for it
that can be used in 338 $b.
Audio carriers: audio cartridge; audio cylinder; audio disc; audio roll; audiocassette; audiotape
reel; sound-track reel
Computer carriers: computer card; computer chip cartridge; computer disc; computer disc
cartridge; computer tape cartridge; computer tape cassette; computer tape reel; online resource
Microform carriers: aperture card; microfiche; microfiche cassette; microfilm cartridge; microfilm
cassette; microfilm reel; microfilm roll; microfilm slip; microopaque
Microscopic carriers: microscope slide
Projected image carriers: film cartridge; film cassette; film reel; film roll; filmslip; filmstrip;
filmstrip cartridge; overhead transparency; slide
Stereographic carriers: stereograph card; stereograph disc
Unmediated carriers: card; flipchart; object; roll; sheet; volume
Video carriers: video cartridge; videocassette; videodisc; videotape reel
Other values established: other; unspecified
81. MARC for content, media, carrier
In each field (336-338):
◦ $a: term
◦ $b: code [give $a and/or $b]
◦ $2: “rdacontent” or “rdamedia” or “rdacarrier” as
appropriate
◦ $3: materials specified - give if appropriate
◦ Ex. 336 $b txt $2 rdacontent $3 liner notes
RDA Essentials (Kuhagen, Nov. 2010)
87
In each of the three fields for these elements, the term is recorded in subfield $a; that same
information can be given instead in coded form in subfield $b or both subfields $a and $b
can be given.
In subfield $2 will be one of the terms as shown; it names the vocabulary used - these are
the terms in MARC identifying the RDA vocabularies. Subfield $3 is used as needed to
identify parts of the resource.
82. 336-338 examples
Book:
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
Music CD:
336 $a performed music $2 rdacontent
337 $a audio $2 rdamedia
338 $a audio disc $2 rdacarrier
Score:
336 $a notated music $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
88
The following slides are examples of how these fields will be formatted.
Let’s take a quick look at one example showing the three fields that will be present in a
template for a book:
- the content type in the 336 field is “text”
- the media type in the 337 field is “unmediated” because a book does not need a
device for the content to be read
- the carrier type is “volume”
Remember that the terms in subfield $a are from controlled vocabularies.
83. 336-338 examples
Map:
336 $a cartographic image $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a sheet $2 rdacarrier
DVD:
336 $a two-dimensional moving image $2
rdacontent
337 $a video $2 rdamedia
338 $a video disc $2 rdacarrier
Online PDF:
336 $a text $2 rdacontent
337 $a computer $2 rdamedia
338 $a online resource $2 rdacarrier
89
336-338 examples
Website (with maps, text, and photographs):
336 $a text $2 rdacontent
336 $a cartographic image $2 rdacontent
336 $a still image $2 rdacontent
337 $a computer $2 rdamedia
338 $a online resource $2 rdacarrier
Or subfield $a may be repeated in 336 field:
336 $a text $a cartographic image
$a still image $2 rdacontent
90
84. 336-338 examples
Website (with maps, text, and photographs):
336 $a text $2 rdacontent
336 $a cartographic image $2 rdacontent
336 $a still image $2 rdacontent
337 $a computer $2 rdamedia
338 $a online resource $2 rdacarrier
Or subfield $a may be repeated in 336 field:
336 $a text $a cartographic image
$a still image $2 rdacontent
90
Some live examples from WorldCat
92
86. Sterling and Francine Clark Art Institute
95
Sterling and Francine Clark Art Institute
96
87. Sterling and Francine Clark Art Institute
97
Sterling and Francine Clark Art Institute
98
88. I don’t know if you noticed, but …
Life in the
cloud!
99
There was a lot of linked data in the last couple of slides I showed you
So, let’s talk about Linked Library Data and the Semantic Web.
If you will kindly refer back to my disclaimer – it is even truer here. I am not an expert!
But, I am game if you are - so here goes…
89. Dunsire, Gordon (2011). Linked data and
the implications for library cataloging.
100
1. The first stage was automation. Here, all the metadata from the card have been stored in
a computer file. The metadata are separated out into different attributes (or fields or cells)
in a regular way; all records have the same set (or sub-set) of attributes. This structure is
implicit in the metadata on the card, where the attributes are indicated by various
punctuation devices (such as brackets), but not always identified specifically. This type of
file is known as a flat-file record, as all the metadata are stored in a monolithic two-
dimensional , or flat, structure.
2. The flat-file is not an efficient way of storing metadata if there is a lot of repetition of
content between records. One area of repetition in library metadata can be found in the
names of persons and organizations; a lot of authors write more than one book, and many
documents can be produced by organizations in the course of their business. Repetition is
minimized by storing a single record, itself also flat-file, containing metadata for the
person or organization. The record is linked to the related bibliographic record using a
numerical identifier,. In library terminology, the bibliographic description and name
authority records are linked via an authority control number
3. The same approach works for subject descriptors taken from controlled vocabularies. A
single subject authority record is linked to many bibliographic descriptions. Note that the
control numbers are transparent to humans; instead, he authority headings (name or subject
term) are displayed on the fly using the link.
4. This type of file structure is known as a relational database. The method of storing
descriptive metadata separately from authority headings which act as access points for the
description began to be implemented in the 1970s, and is used by the majority of
automated library catalogues today. But a new approach is being developed based on the
Functional Requirements for Bibliographic Records (FRBR) model published in 1998.
90. Dunsire, Gordon (2011). Linked data and
the implications for library cataloging.
101
1. In this example, the Work component of the FRBR record does not contain any
metadata content, just the structure in the form of attribute names, and transparent links to
the content of the authority files.
2. RDA: resource description and access is the successor to the Anglo-American
Cataloguing Rules for determining bibliographic record structure and content. It is fully
compatible with FRBR. One of its features is widespread use of controlled terms for
metadata content. We can apply the same approach as for authority files, and store the
controlled terms in their own file, linked to the relevant component of the FRBR record.
Content type is one of the RDA attributes using a controlled vocabulary.
3. The same for carrier type.
4. The provenance attribute in the Item component record refers to the author and is an
implicit duplication of some of the content of the author attribute, which is authority-
controlled. We can minimize this duplication by refining the provenance attribute into the
more specific donor attribute and isolating the author reference as the content of that
attribute. The donor attribute is then linked to the same name authority record as the author
attribute.
5. This just leaves the manifestation title within the FRBR record. But we could link the
attribute to a publisher or bookseller file of titles …
6. And end up with a FRBR record which contains only attribute names and links.
The record is reduced to its bare-bones structure, and effectively is extinct.
91. Dunsire, Gordon (2011). Linked data and
the implications for library cataloging.
102
Where has the bibliographic record gone? Its content has been completely disaggregated to
multiple records stored elsewhere in the local system or in remote systems. Library of
Congress Subject Headings are already available in a format suitable for this approach,
known as linked data. The Virtual International Authority File for names is also available
as linked data. Linked data is the basis of the Semantic Web.
The bibliographic record is implicit. The attribute names and links are used to assemble an
explicit record on demand. The metadata content is efficiently stored and maintained (any
change to authority content is immediately reflected in the assembled record). Catalogues
do not have to store any of the metadata locally just in-case a user needs it; the metadata
record is presented just-in-time.
The current pre-FRBR environment involves huge amounts of duplicated effort with
multiple copies of records being maintained separately at the local level. But we all
have backlogs of new bibliographic resources to describe.
92. Dunsire, Gordon (2011). Linked data and
the implications for library cataloging.
104
A quick word about Library namespaces – this will make better sense in a few more slides
(hopefully)
Dunsire, Gordon (2011). Linked data and
the implications for library cataloging.
105
This should help as well.
93. Linked data: The play’s
the thing
Ed Jones, National University (San Diego)
ALA Annual Conference (New Orleans)
So now I am going back to Ed Jones, you remember him from the section on FRAD, to
give us a whirlwind tour of how RDA plays with the Semantic Web. Ed was asked to talk
about how RDA plays with the SW at ALA annual in New Orleans.
This is an excellent presentation and unfortunately I don’t have time to go through the
whole of it now. There is a link to it in my bibliography. I am going to scale it down a lot.
–but, hopefully you will get the idea.
The playground
[Linked open data cloud diagram, by Richard Cyganiak and Anja Jentzsch,
http://lod-cloud.net/]
So here’s the playground
Dbpedia is popular, as is ACM Who do we play with?
94. Who we play with
Ourselves, mostly
[Describe]
The Germans are well-represented
Lobid = North Rhine Westphalia Library Services Center (German)
PSH = Polymathic Structured Subject Headings (Czech)
P20 = 20th Century Press Archives (German)
But if we’re going to look at how we play, we’re going to need some playground rules
…
95. Ranganathan’s first law of linked data:
Data is for use
[or, for the true die-hard, Data are for use]
Playground rules
So I have 1 playground rule and 2 corollaries
This seems pretty straightforward, but then so did Books are for use, and we’re still trying
to come to grips with that one
and there are useful corollaries to this law …
97. “If you build it, they will come”
1. There is (or will be [maybe, hopefully])
a lot of linkable data out there
2. Others will want some of our data and
make links
3. We will want some of theirs and make
links
Corollary 2 to Ranganathan’s first
law
I think (1) is fairly certain
(2) And (3) have yet to be proved
Making your data linkable is fairly straightforward once the translation has been done
But while the metadata can be converted on an industrial scale, linking between individual
records in different sets often requires manual intervention
99. Playing nice:
Tim Berners-Lee’s rules for linked
data
1. Use URIs as names for things.
2. Use HTTP URIs so that people can look
up those names.
3. When someone looks up a URI, provide
useful information, using the standards
(RDF*, SPARQL).
4. Include links to other URIs so that they
can discover more things.
Tim Berners-Lee has his own playground rules
[describe]
Pretty straightforward
RDA isn’t out on the playground yet, so it’s hard to judge how it will play, but some of
its playmates are (at least tentatively)
100. How we play: Group 3
LC makes available a number of its vocabularies and element sets, including LCSH
They’re available as RDF/XML, N-triples (N-Triples is a line-based, plain text format for
encoding an RDF graph.), and JSONProvided (JavaScript Object Notation, is a
lightweight text-based open standard designed for human-readable data interchange.) “as
is” (swap-meet rules)
XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML
Information Set and XML Base
