1. Module 8: “Top Twelve”
Now we come to reminders of things we want to be sure to take with you from today’s session. We have selected a “top twelve” for you.
Library of Congress RDA Seminar, University of Florence, May 29-June 2, 2011

2. “Top Twelve” things to remember
#1: User needs/user tasks:
-- find, identify, select, obtain
#2: “Take what you see” (representation
principle)
1. User tasks – the ICP (International Cataloguing Principles) first principle is to keep in mind the convenience of the user – that will require cataloger’s judgment to meet the user tasks of find, identify, select, and obtain – you will need to determine if the data beyond the core elements is important to meet those user tasks for your target users.
2.Take what you see (this is the principle of representation in ICP).
RDA Seminar, University of Florence

3. “Top Twelve” things to remember
#3: Element-based description
- easier reuse of well-formed metadata
- elements sets
- RDA Registry (controlled vocabularies)
- more use of pre-existing data (e.g., ONIX)
3. RDA is structured to build an element-based description of well-formed metadata. Those identifying characteristics, or elements, are identified in RDA as element sets and are available for machine-use in the RDA registry. The RDA Registry has both the list of elements as well as controlled vocabularies for some values that we should give when identifying resources. The elements can be re-used or displayed as needed for different contexts, which will make them more usable in the Web environment. It also means we will be able to make better use of data available on the Web or in digital form, such as ONIX data from publishers, that we can take as we see it.
RDA Seminar, University of Florence

4. “Top Twelve” things to remember
#4: “Work, Expression, Manifestation, Item”
#5: “Core” and “Core if” ... Elements – can add
others (related to #1)
#6: Alternatives, optional omissions, optional
additions (related to #1)
4. Group 1 entities from FRBR – these are the aspects of the resource that you want to describe for your users.
5. Core and “Core if” –other elements can be added to this basic set when they are important to your institution.
6. The instructions also include alternatives, optional omissions, and optional additions; you need to make decisions for your users – the preliminary decisions about these for the RDA Test that LC made for our catalogers will be analyzed in the coming months to determine future practices – whether we implement or not. At a minimum we will need to deal with RDA coming in on copy cataloguing, and make some decisions about what if anything to adjust there.
RDA Seminar, University of Florence

5. “Top Twelve” things to remember
#7: Fewer abbreviations (related to #1 and #2)
#8: Relationships, relationships, relationships
(most beyond core elements)
#9: Content, Media, and Carrier types
7. There will be fewer abbreviations so the data is more understandable to users.
8. We will indicate relationships to enable better navigation of the bibliographic universe.
9. RDA replaces the GMDs with more explicit content, media, and carrier types. Hopefully future systems will be able to use this data to display icons or some other visualization clue for the users and use this data for filters or limits on a search and enable grouping such resources for the user.
RDA Seminar, University of Florence

6. “Top Twelve” things to remember
#10: No more “rule of three” – instead, use
cataloger’s judgment
#11: Sources for information expanded
10. The rule of three is gone (except as an alternative) and cataloger’s are encouraged to use their judgment to provide access and data appropriate to their user needs.
11. Basically any source can be used for the identifying data.
RDA Seminar, University of Florence

7. “Top Twelve” things to remember
#12: Identifying characteristics (elements and relationships) as building blocks for future systems
-- talk to your vendor about need for new
systems
12. RDA’s approach of building well-formed metadata as we identify and describe resources, plus the relationships and links mean we have the building blocks for future systems. Now it is time for system developers to use this structure of RDA’s element sets and controlled vocabularies and relationships to build more sophisticated systems for our users and for making cataloging easier.
Thank you all for your attention – any more questions?
RDA Seminar, University of Florence

8. Questions later on any aspect of RDA: LChelp4rda@loc.gov
Questions on today’s presentation: or
Questions later on any aspect of RDA:
RDA Seminar, University of Florence