Hello Everyone! welcome and thanks for joining us Back by popular demand this is essentially a repeat of the webinar we did last October although perhaps we are able to answer more questions about RDA with each year that passes!
I will start by thanking the people who have developed and delivered presentations on RDA and allowed us to incorporate their work into ours; And a big Thank You to Chris Oliver from McGill University in Montreal, whose work we are using (some slides) in this presentation, which is based on one that Alison create for staff at the University of Waterloo.
Along with cataloguers from across Canada, Alison and I have been developing training for cataloguers, In this presentation we will talk about RDA for all library staff because everyone will see the outcome of the changes RDA is already out there because the Library of Congress is using it, and libraries and vendors are using records from LC so they are probably trickling into your catalogue as we speak. So our plan today is to explain what RDA is, talk about some of the differences we’ll notice in catalogue displays describe the improvements we expect to see in our systems for searching and navigation, and then talk a little about what’s next We have planned our presentation so that we have time to answer your questions which you can type into the chat box
The full title is Resource Description and Access -- RDA is a content standard to replace the Anglo-American cataloguing rules (AACR) -- many libraries in Canada, the US, England, Australia, Germany, have implemented it. This is a big deal in cataloguing because some changes are big. RDA is a content standard – meaning it lists the data elements (aka fields) that make up a description, and what goes into those fields
it is important to emphasize --- content --- the standard does not prescribe how to mark up the data elements (by markup I mean in MARC records or in XML, there are many) so it’s flexible RDA’s instructions guide us on making well-formed metadata, meaning data that is structured in a way that computers can easily interpret and use -- which is basically making sure that each element contains only one type of information, for example one type of date. Well-formed data is less ambiguous. This has an effect on what search engines can do with the data. Some of the data we create with our current cataloguing code is in long text strings, in notes -- the actionable stuff is buried. If computers can more easily act on the rich detail in our data, we can use it to create functionality that will help searchers navigate relationships in our catalogues and ideally also what’s available online, in the bibliographic universe Another of RDA’s focus is how works relate to each other, and how creators are related to works, and how the stuff in library collections are related to other stuff. Our legacy cataloguing data is detailed and accurate, but it’s buried in MARC in our integrated library systems and we cannot easily relate it to the rich and varied metadata that it out in the world. Presently there are four ongoing translations of RDA: Chinese, French, German, and Spanish National Library of Ireland (2014) National Library of the Philippines (2013) National Library of Scotland (2014)
RDA is based on a conceptual model called the “functional requirements for bibliographic records” -- an entity-relationship model that clearly depicts relationships between things– such as the relationship between a novel and a parody of that novel The important word in the title is FUNCTIONAL -- with RDA we record the data that is important -- it is important because of how it is used There are core elements, which are the minimum need to achieve the user’s searching goals. With RDA we are still recording titles, dates of publication, editions, like we’ve always done, but now we have a specific job or jobs for the data, FRBR ties each element to something that users do when they search FRBR defines these as “user tasks” and RDA provides cataloguers with instructions on which data elements to include that address these tasks When searching, users want to: find – based on a search string they enter, identify, select, obtain the item, perhaps by clicking on a link in the record or recording a call number/shelf address. so, with RDA we will be creating data that is not only machine-actionable (because it’s well-formed) but also focusing our energies on the elements that directly impact what people do when they search
This metadata will give us the framework to design computer interfaces that will clearly depict those all important relationships!
There are core elements – and then there are optional additional elements, so we have some flexibility in terms of how much detail we want to include in our clusters of data that describe works
The FRBR model gives us a framework for describing how works are related to each other. For example, let’s say l want to read Lawrence Hill’s book called “The Book of Negroes” I’ve heard it’s literary history, named after the the British naval document that listed the names of Black Loyalists who served in the British army in the late 1700s and were transported by ship to Nova Scotia. This is a work I want to read.
I have choices as to the expressions – how the ideas and story lines are communicated.
In terms of textual expressions, I can read an English version published in Canada – the first bookjacket on this slide.
If my library acquired our copy through our American vendor it may be in my catalogue under a different title -- in the US and in Australia publishers insisted the title be changed – and it was issued as Someone Knows My Name.
The French translation published in Quebec, which is Aminata, the name of the protagonist. If I prefer to read in French I might want that expression of the work.
The Norwegian title (bookjacket is on the lower left) is another expression, the title of which derives from the American title -- which caused some concern, people found the title offensive and copies were burned publicly in Denmark to protest.
Now imagine the other expressions that are also available : audiobooks and digitized version that can be downloaded to mobile devices, in various translations – you can read the book in Turkish, in Arabic, in Hebrew, in Portuguese. The Canadian filmmaker Clement Virgo is working on a film adaptation, which is a related work.
We currently have uniform titles to bring the expressions together in our catalogues but we just display long lists because we don’t distinguish between the various formats and languages in a logical way. RDA is one step towards creating well-formed metadata that will help us create displays that clearly depict the relationships; and perhaps also link to relevant information such as the news of protests in Denmark, awards earned, how that film adaptation is progressing, etc.
This new content standard RDA is designed to meet our needs now, to work in our current catalogues RDA data is a big deal for cataloguers because overall the changes are significant and will change the way we work. We will make some small incremental changes, and as we implement the new rules we take into account that RDA data is meant to co-exist with our legacy records – our databases will soon have a messy mix of records catalogued according to different content standards – so they are going to have to live together for the foreseeable future The cataloguing community has high expectations – we expect RDA to enable us to do new things: we expect to be creating bibliographic data that can function in the linked data environment on the web that is growing every day – Alison will talk about this later we expect that our data will be, finally, out there working with other types of metadata, to create new tools and services To improve the systems we use to describe, store and search for data about our collections. Now Alison is going to talk about how RDA will affect displays
We’re going to explore how things might look a little different in your OPAC or discovery layer once we start cataloguing with RDA.
Here is part of an RDA record. I’ve removed things like ISBN, subject headings etc. so that the record isn’t overwhelming, so don’t focus on missing elements. I want you to take a look at this record and use the chat box to tell me what you think is different. I’ll give you a minute to enter comments into chat. Note – I changed this to an e-book for illustration purposes.
Note: cm is an exception; unit of measurement with accepted standard for representation There are fewer abbreviations used in RDA. This doesn’t mean you will never see an abbreviation in an RDA record! Certain elements use the principle of accurate representation of the resource. For these elements we record what is on the resource itself. For example, in the edition statement if it says 3rd ed. on resource we record it as 3rd ed. When not transcribing directly from the resource we do not supply abbreviations. For example, if there is no place of publication we provide information in clear language instead of using s.l. for sino loci. We also spell out words like illustrations and pages. Fewer abbreviations allow for clarity – our users don’t need to figure out things like ill., port., v. s.l., et al. and so on. It does mean that displays are a little wordier and as a cataloguer I will be thankful for macros or drop-down boxes!
RDA introduces a “take what you see” approach to describing a resource. For example we may have a resource with what looks like a typo in the title. In AACR we would insert the latin word sic into the title to indicate an error. Now we transcribe as found but still provide a variant title if we think users may search it differently. In this case it seems pretty clear it is a typo but in other cases it may have been quite intentional. Recording it as is increases accuracy in citations, makes things more predictable for search and also means that as a cataloguer I’m not second-guessing marketing decisions! We can respect the resource in hand by displaying what is there but still meet the needs of the searcher. you may want to check with your systems dept. if you display variant titles
This “take what you see” approach applies to capitalization as well. This allows us to take advantage of machine-generated data from publishers, such as table of contents notes, or as found in the bulk-files of MARC records which often accompany purchases of large e-book collections. When creating individual records cataloguers have the choice of using sentence case and will probably do that. However, for bulk loads we can choose to accept titles as is, allowing us to get the files into the database without as much time-consuming editing of things that do not affect access. Of course, it will mean some variability in display. There is also a trust factor here– trusting that the source data is correct. That will need to be tested from vendor to vendor.
In AACR2 once there were more than 3 authors cataloguers only listed the first author followed by the latin term et al., meaning and others. In RDA naming everyone in the statement of responsibility is the default, with an option to use [and 4 others]. I have an anecdote from the reference desk that speaks to the usefulness of this data. Once I had a faculty member trying to cite a resource with more than 3 authors because the editor of the journal would not accept et al. in the citation. No catalogues or indexes listed all of the authors and he no longer had a copy of the resource. We had to interlibrary loan the item to see the title page!
Display of format will also change with RDA. AACR2 has a term called the general material designation which sits beside the title. For example, all sound recordings regardless of type would have the same GMD: sound recording. With RDA the GMD has been replaced by 3 elements: content type, media type and carrier type. Taken together we can decide what icons or other devices we can use to more specifically identify the type of resource, for example music CD or portable music file. I’ve shown an example with icons but you could choose to map to phrases instead. Images from: http://all-free-download.com/free-icon/music-cd.html
Here is an example of the 3 new elements, which aren’t really meant to be displayed as is to the user. They help us differentiate between the different types of resources. For example between books that are physical vs. online, that are textual vs. spoken word. In MARC coding we have some fixed fields that help us to this but these fields did not exist in our cataloguing rules; with RDA we now have guidance for this type of information whether we are using MARC or some other type of format.
These elements are repeatable, allowing you to say more about the resource. For example, here is a website that has text, maps and images. In the past this would all of have been represented by [electronic resource]. Currently, we can already code this information using the fixed fields in MARC21 but it has never been part of the cataloguing rules. Now we need to figure out how we want to use and display the information!
I think my favourite aspect of RDA is the expansion of guidelines and elements for identifying persons, families and corporate bodies. These elements are separately coded so that each piece of information could be accessed. Also they can be coded even if they aren’t being used as part of the access point. In AACR2, most of the focus was on the form of the authorized heading and the references. For example, we can add Alice Munro’s place of birth, associated country, her occupation and what language she writes in. Right now we mainly use the authorized access point which is made up of the name and part of the date of birth. But what about in the future?
Here are some mocked up examples of what we could do in our catalogue instead of just displaying the name. Users encounter many names in our database, what if we could give them a little bit more to help identify the person using information from the authority records? If this is too cluttered, how about a “who is this?” or information link?
To explain the potential for improvements to navigation we should take a quick look at the conceptual model ... FRBR
There are 3 main groups in FRBR that are used to describe the things we know well: titles, authors and subjects
Group one is the stuff - all of the books, ebooks, documentaries, etc. that we collect for our user communities
Group two is the people, corporate bodies and families who make the stuff – writers, illustrators, founders, etc., plus In RDA the scope of creators is expanded to include families
Group three consists of the subjects, what all that stuff is really about
Creating data about these groups and then creating links to depict relationships between the groups – will help us improve navigation by clustering entities in meaningful ways it will also lead us to create data about entities once and then reuse that data whenever needed rather than re-create it when we acquire another copy in a different format or language for our collections We do this now with authority data but will do it more with RDA The next slide shows an example of how FRBR describes things we (libraries) collect as group 1 entitles – works – expressions – manifestations -- items
FRBR is a theoretical framework which give us different language/terminology for the things that libraries collect and describe, work with everyday. These are W E M I -- I’ll go through them now:
Works are often referred to as books --- I want to read that book. What if the book was written in German? When said by students, there’s a book they have to read for class, it’s got a specific story and author, and they don’t mind if it’s paperback or large print so long as it’s the book. That’s a work = a distinct intellectual or artistic creation, it’s really in the author’s head, the idea/story. It’s not live until it gets to the next level and expressed in some way.
IT is important to note here, that this description of the work is a shareable description, by everyone with an interest in an authoritative source of this information. There will be an authority data cluster/record of sorts which we will either be downloading to our local databases or pointing to. A “work level” description is helpful then because it can include information that is relevant to any user of the “work” regardless of whether it’s large print or published in the UK or a pdf copy online, they just need to read the real thing and not a parody of it which is a related thing.
Next we have the various expressions available in the universe, which are available to our users – expressions are intellectual or artistic realizations of a work in the form of text, or spoken word, sound, images, or any combination of these forms. Describing objects at the expression level will people choose on a practical level based on the format they need, and also based the language in cases where a work has been translated.
The manifestation level is the physical embodiment of an expression of a work, this is what we catalogue currently – for example all of the units printed and published by a publisher in one run.
Finally, we will describe at the item level = single instance of a manifestation, your library’s copy – what if anything is unique about it and probably a barcode
Every object has aspects of it that fall into one of the group one entities. In this example I’ve flipped WEMI the other way around so we can start with the item level, This an item in Ryerson’s collection; It’s one copy of the manifestation produced in Vancouver by Beach Holme Publishing - they printed a run of copies – this is the manifestation of the English expression – I think it’s the only one, unless there’s a new audiobook out there The work is the stuff that Michael Crummey thought up, the characters and the story and the order of the stories in this case. The work record will be created and if it’s like a wiki then knowledgeable/interested persons can contribute information to it, which we will all point to when we collect expressions and manifestations of this work. Rather than what we do now which is repeat the work information in every record for every object related to it.
Here is an abstract illustration showing, how With current linking functionality in marc records in catalogues, we can co-locate works a little bit - circles that are overlapping are related somehow however for the most part our systems return long lists of results when a search is performed partially because the underlying data is not machine-actionable -- it can be read and indexed, but MARC linking fields do not depict relationships very well
using FRBR as a model, we can imagine how displays that, making use of the information created with RDA, will clearly depict the relationships between works, expressions and manifestations the ultimate goal is helping human users navigate and discover relationships RDA promises to also make the cataloguing work more streamlined -- we can create and share records for works and expressions so we’ll re-use the WORK information (as we do now with authority data) and focus on connecting the dots – linking the data for different manifestations and items
Here is a screenshot from OCLC’s Work Pages site, Work Pages is an experimental project that applies principles of the FRBR model – by pulling out data from MARC records in Worldcat and aggregating the existing bibliographic information, they demonstrate how records can be clustered clustered into works using programming algorithms This prototype is based on a January 2011 snapshot of WorldCat the result is descriptions that are richer and more complete than the descriptions in individual bibliographic records. compared to the long hitlists created by our integrated library systems currently, this offers searchers a visual and clear overview of the work, the formats and translations available, thereby helping users to find, identify, select and obtain An example of using the work we do to create value-added ways of accessing and using bibliographic data for human consumption a couple of changes to specific fields that will affect how searchers navigate catalogues ...
As we heard earlier, RDA does not restrict the number of authors that are recorded when there are more than 3 -- RDA gives us a choice to list them all or record the first name and summarize the number of added authors in plain English. This improves the information in our catalogues since we can provide access points for all creators responsible for the work, regardless of where their names appear in a long list of names. And if or when we acquire more works by the 6th or 7th author, we can collocate those works under the author’s name.
As Alison said with RDA will can include additional relevant information about creators, so as to give searchers more to go on than just birth and death dates. The expansion of guidelines and elements for identifying persons, families and corporate bodies means we will include details with will make it easier for searchers to navigate through long lists of similar names.
RDA metadata includes designators – role designators – which are handy when it comes to multi-talented persons Imagine searching for a persons name and getting something like this, instead of the long title lists our systems currently display
The concept of a family as an entity that create or otherwise be associated with a work is introduced in RDA Up until now Families have been treated and established only as subject headings RDA defines a family as “two or more persons related by birth, marriage, adoption, civil union, or similar legal status, or who otherwise present themselves as a family” (RDA 8.1.2) some of the elements that can help users could find useful in addition to the name, are § Dates and places associated with the family § Prominent member of the family § Hereditary title § Family history So we will provide access points for families as creators, founders, etc. and users will be able to search on family names. Famiies can also be related to a resource This is an Important elements for archives, museums, special collections, genealogy newsletters, family reunion publications and the like. You may recognize the budding metadata librarian in this family photo with lovely while kneesocks on.
here is an example of how we might display data for a family, including some of the new elements prescribed – place and history, this example was created by Alison for her cataloguing training module Although there a quite a few new elements and the underlying MARC record has a lot of detail, not all of it needs to be displayed to users. If it’s well formed and parsed out into discreet chunks, we’ll be able to choose what to display and how.
Another big change that users will notice when searching collections that include various expressions of the Bible With the current rules, when a resource contains expressions in more than 3 languages we provide one access point with language “polyglot” So currently we see: Bible. O.T. Polyglot In RDA you can give access point to all of the expressions, which makes it possible to index and search for them Notice also that we will also no longer use OT for old testament
Trina has given you a little glimpse into the future while talking about the potential of FRBR for navigation and earlier in the intro to RDA she talked about structured metadata, the importance of having discrete and well defined data elements. I’m going to build on those very briefly. If you are struggling to grasp what we mean about discrete and well defined data, I will give you a non-library example that you should find familiar. If you type something like 10-16-2013 into Excel it recognizes the format and automatically changes it to a date. This is because you have used a standard, well-defined format. You can go one step further and format a cell or row of cells yourself and say to Excel these pieces of data are all dates. Excel then knows the rules for what it can do with dates. So you have one piece of information in a cell and you have told the machine the type of information it is and because of that type the machine knows what kinds of things can be done with it, for example how to sort, how to calculate number of days etc.
RDA is one of the developments that is prompting the library community to think about how library data can interact with data beyond the catalogue out on the web. How can our data be discoverable in web search engines? How can we contribute unique library data to other communities? And how can we take advantage of data out on the web to augment our own bibliographic descriptions for our users? How do we make connections for our users? We have bibliographic data in a library-centric format, MARC, that is housed in MARC databases that aren’t accessible to web searches. One way of being web accessible is to produce data in XML format. For example, records in the Primo discovery layer are stored in XML. This allowed Vanderbilt University library to create a site map of their library catalogue so that it is searchable in Google. Their unique resources, such as Global Music Archive then showed up in Google results. Based on recommendations coming out of the RDA test in the United States, the Bibliographic Framework Transition Initiative (also known as BIBFRAME) has been established by the Library of Congress to investigate a post-MARC future for library metadata.
A step beyond just XML itself is to provide library data in a format that supports linked data. This is the framework that BIBFRAME is exploring. I’m a linked data newbie, not an expert but I’m going to try to convey to you the power of well-defined elements combined with formats that allow machines to act on that data, to find the relationships between pieces of data and know some logic it can apply to that data based on the category it belongs to. Before I start I want to say thank-you to Pascal Calarco here at Waterloo and Corey Harper at NYU for giving me feedback on this section. Here are some links that you can explore later. I will talk about the first 2 links.
Linked data means marking up your data in some way so that it defines attributes of resources and specifies relationships that the machine can act on, for example that a certain resource is a web page and the subject of that web page is a woman which belongs to the class “person” who’s name can be displayed as Margaret Atwood. Here we are looking at the human readable view of this record for Margaret Atwood from VIAF. VIAF is the Virtual International Authority File. It is hosted by OCLC and is a joint project with several national libraries. It has brought together information from various authority files, but not just in MARC format. The information is also available in Resource Description Framework (RDF) which supports linked data. The defined elements let a machine know that this page is about Margaret Atwood and Margaret Atwood is a person. It has supplied different ways of displaying the author’s name, for example in different scripts, and also supplied alternative names for the author. It tells the machine that the person described in this resource is the same Margaret Atwood as in the Wikipedia resource and in the World Cat Identities resource. A machine can just use VIAF to pull information about Margaret Atwood or it can send a request to the Wikipedia page to find out more.
Wikipedia exists as linked data through DBPedia. Here are some of the machine-actionable properties in DBPedia, I’m just showing you a very small segment of the page. Notice that it includes the VIAF identifier [A]*. It also includes information on Margaret Atwood’s homepage [A], a link to a picture of the author [A] and tells the machine that the subject of this DBPedia page is the same as the subject of the New York Times linked data page [A] on Margaret Atwood. What is important is that the data is there but it is also defined. Margaret Atwood is a person and she is influenced [A] by the subjects of these other dbpedia pages who are also persons. Margaret Atwood has a homepage and here is the address for that homepage. This other URL is a depiction of this person Margaret Atwood and so on. The best thing about DBPedia is that many linked data collections link to it, so it acts like a hub to other data. By knowing the identifier for VIAF you can pull in the library related information but also move onto other data sources for more information about Margaret Atwood. Notice that dbpedia has defined some of their own properties, but they are also taking advantage of properties that have already been defined like homepage from foaf, or Fried of a Friend, and same as from OWL, web ontology language. *[A] = animation
RDA has contributed some properties to the web too! A shout out to Corey for finding this example from the BNF showing the use of RDA elements in an RDF record. Above you have the human readable view of the information and below is the underlying machine readable data. They have used the RDA place of publication to supplement the Dublin Core properties because in unqualified Dublin Core publisher can include both place of publication and name of publisher; the RDA elements are more granular. They have also made use of the FRBR relationships in RDA to explain that this 1994 Paris edition of La reine Margo is a manifestation of a particular work. These RDA properties have been defined on the web in the Open Metadata Registry by the Dublin Core Metadata Initiative/RDA Task Group.
Basically, what we want to do, and what we think RDA will help us do, is go beyond the borders of our catalogues. (read and expand on screen)
What does all of this mean? RDA is very new and as a community we are just starting to envision the non-MARC future, but we expect that RDA is positioning library metadata for that future.
RDA for Public Services
Education Institute Webinar
Presented by Trina Grover & Alison Hitchens
October 16, 2013
(Repeat of the EI Institute presentation of Oct. 2012)
To all of those people who are letting us re-use their
presentations in preparation for RDA implementation.
In this case, thanks to Chris Oliver (McGill University) for
use of slides from various presentations.
This presentation is based on a presentation given to
uWaterloo public services staff in April 2012
What is RDA?
How will RDA affect display?
How will RDA affect searching & navigation?
work in current
be compatible with
co-exist well into
enabling us to
take advantage of new
create data that can function
in linked data environment
make library data visible in the
make library data work with
other types of metadata
HOW WILL RDA AFFECT DISPLAY
Photo source: Supercake
Don’t introduce abbreviations– accurate representation
On title page:
• Don’t use abbreviations - responsiveness to user need
Publisher: [place of publication not identified] : Fishy Press, 2011
Extent: x, 143 pages : illustrations, portraits ; 22 cm
TAKE WHAT YOU SEE!
“Take what you see” - accurate representation of the
Title: The wolrd [sic] of
Variant title: The world
Title: The wolrd of
Variant title: Title should read:
The world of television.
TAKE WHAT YOU SEE!
• make use of machine-generated data
• Important for bulk-loading of records and for re-use of
• Does result in variability in display
Title: BIG BOOK OF INTARSIA
WOODWORKING : 37 Projects and Expert
Techniques for Segmentation and Intarsia
OPTION TO LIST ALL OF THE AUTHORS!
Bill Traylor : drawings from the collections of the High Museum
of Art and the Montgomery Museum of Fine Arts / essays by
Margaret Lynne Ausfeld … [et al.].
Bill Traylor : drawings from the collections of the High Museum of
Art and the Montgomery Museum of Fine Arts / essays by
Margaret Lynne Ausfeld, Susan Mitchell Crawley, Leslie H.
Paisley, Fred Barron, Jeffrey Wolf.
FORMAT AND TYPE OF CONTENT
The sound of music [sound recording]
The sound of music
The sound of music
CREATE ICONS MORE ACCURATELY
content type: text
media type: unmediated
carrier type: volume
content type: text
media type: computer
carrier type: online
content type: spoken word
media type: audio
carrier type: audio disc
Online Audio book:
content type: spoken word
media type: computer
carrier type: online resource
SAY MORE ABOUT THE RESOURCE
In the past this would all be represented by:
content type: text
content type: cartographic image
content type: still image
media type: computer
carrier type: online resource
With RDA: we need to figure out the display!
ELEMENTS RECORDED TO IDENTIFY A
Date of birth: 19310710
Name: Munro, Alice
Place of birth: Wingham, Ont.
Associated country: Canada
Place of residence: Clinton,
Fuller form of name: Alice Ann
Variant name: Laidlaw, Alice Ann
Alice Ann Munro (née Laidlaw) is
a Canadian short-story writer
& three-time winner of
Canada’s Governor General
Award for English-language
fiction, recipient of the 2013
Nobel Prize in Literature & the
2009 Man Booker
International Prize for her
lifetime body of work…
POSSIBILITIES FOR DISPLAY
Munro, Alice, 1931- (short-story writer)
Munro, Alice, 1931-
Canadian short story-writer born in 1931
Munro, Alice, 1931-
Also known as Alice Ann Munro and Alice Laidlaw
Munro, Alice, 1931-
Who is this?
Munro, Alice, 1931-
HOW WILL RDA AFFECT
SEARCHING & NAVIGATION?
Photo source: Cedric Husler
FUNCTIONAL REQUIREMENTS FOR
BIBLIOGRAPHIC RECORDS (FRBR)
FRBR Group 1
things that libraries collect
FRBR Group 2
entities who do the
intellectual / artistic work
to make things
FRBR Group 3
need to read the novel for
an English exam -- I want
access to the WORK
want an audio version for
commuting -- I need to
find a particular
prefer a paperback copy
when traveling -- I want a
need to find the copy I
borrowed, it is overdue --
I need a particular ITEM
Image source: people-clipart.com
- 1 OBJECT
an item in Ryerson’s
one example of the Beach
an embodiment of the
a realization of the work
by M. Crummey
TRULY FRBR-IZED DISPLAY OF DATA
translations of text
adaptations as a motion
Source: Oliver (2011: slide 34)
A project of OCLC Research
Tremblay, Michel, 1942-
Selected works: Le Vrai Monde (1983)
Un objet de beauté (1997)
Tremblay, Michel, 1954-
Associated group: HEC Montréal
Tremblay, Michel, 1955-
Affiliation: Medical School of Laval University
Tremblay, Michel, 1964-
Associated place: Saskatchewan
Affiliation: Saskatchewan Agriculture and Food
adapted from D. Paradis (2009)
LOOKING TOWARD BETTER DISPLAY
& NAVIGATION OF ROLES
is the author of 25 resources
is the director of 37 resources
is an actor in 5 resources
is the subject of 20 resources
WE ARE FAMILY!
Photo credit: Derek Hitchens.
Used with permission.
Name: Eaton Family
Place of residence: Toronto, Ont.
Prominent member: Eaton, Timothy, 1834-1907
History: Timothy Eaton was born in March 1834 in
Ballymena, Northern Ireland. At the age of 20 he moved
to Ontario. He married Margaret Beattie in 1862 and had
5 children. He opened a dry goods store in 1869 in
Toronto which was the cornerstone for the large
Canadian retail chain Eaton's. John Craig Eaton inherited
the business in 1907 ... The business went bankrupt in
SEARCH FOR MULTI-LINGUAL MATERIALS
Title: Antigo Testamento Poliglota : Hebraico,
Grego, Português, Inglês.
Bible. Old Testament. Hebrew
Bible. Old Testament. Greek
Bible. Old Testament. Portuguese
Bible. Old Testament. English
Photo source: Fabienne Wassermann
FOR FUTURE SEARCH & NAVIGATION
STRUCTURED DATA LINKED DATA
Virtual International Authority File (VIAF)
You may also want to explore:
BIBLIOTHÈQUE NATIONALE DE FRANCE
DATA IN RDF
Human readable view
BEYOND OUR BORDERS
Capture enhanced biographical information
Link to other works by the author not held in the library’s
Contribute information about an author to the web
Capture descriptive information about the content of the
work (e.g. in Wikipedia, in a national bibliography, publisher’s
Link out to resources that are based on the work (e.g.
adaptations, movies, plays etc.)
Contribute bibliographic data and relationships to the web
Make our library resources discoverable on the web
Photo source: Cea
for the future
Ryerson University Library
Cataloguing & Metadata Librarian
University of Waterloo Library
American Library Association, Canadian Library Association, and CILIP: Chartered Institute of
Library and Information Professionals. RDA Toolkit. http://access.rdatoolkit.org/
Grover, Trina. “Cataloguing on the edge: emerging standards for bibliographic data,”
PowerPoint prepared for Atlantic Provinces Library Association, May 17, 2011. Access at
Hitchens, Alison. “Resource Description and Access (RDA) for Public Services Staff,”
PowerPoint prepared for ISD Training Day, University of Waterloo Library, April 26, 2012.
Library of Congress. “Module 4: Persons, Families and Corporate Bodies: Elements and
authorized access points.” PowerPoint module prepared for the Georgia Public Library Service
Cataloging Summit, August 9-10, 2011. Access at
Oliver, Chris. “What is RDA and why do I need to know?” PowerPoint prepared for CLA
Montreal Chapter, March 9th
, 2011. Access at
OTHER RESOURCES - RDA
Library of Congress. Acquisitions and Bibliographic Access Directorate. Resource
Description and Access (RDA): Information and Resources in Preparation for RDA.
Library of Congress. Bibliographic Framework Transition Initiative
Oliver, Chris. Introducing RDA: a guide to the basics. Chicago: American Library
RDA Canadian Knowledge Exchange wiki. http://rdaincanada.wikispaces.com/
Welsh, Anne; Batley, Sue. Practical cataloguing: AACR, RDA and MARC21. New
York: Neal-Schuman Publishers, 2012.
OTHER RESOURCES – LINKED DATA
Coyle, Karen. RDA vocabularies for a twenty-first century data environment.
Library Technology Reports v. 46, no. 2. Chicago, Ill.: ALA TechSource, 2010.
Coyle, Karen. Linked data tools: connecting on the web. Library Technology
Reports v. 48, no. 4. Chicago, Ill.: ALA TechSource, 2012.
Coyle, Karen. Understanding the Semantic Web: bibliographic data and metadata.
Library Technology Reports v. 46, no. 1. Chicago, Ill.: ALA TechSource, 2010.
Harper, Corey. “Linked Library Data: Tuning Library Metadata for the Semantic
Web.” ALCTS webcast, March 16, 2011
Miller, Eric. “Bibliographic Framework Initiative Update MARC Linked Data
Model.” Presented at Library of Congress, Washington DC July 16, 2012
CREATIVE COMMONS LICENSE FOR
This work is licensed under the Creative Commons
Attribution-NonCommercial-ShareAlike 2.5 Canada
To view a copy of this license, visit
send a letter to Creative Commons, 444 Castro Street, Suite
900, Mountain View, California, 94041, USA.