Rda Module 4: Navigating the RDA Toolkit

Editor's Notes

• #2: We are going to explore the toolkitThis is an introductory look at the tool kit, it is hoped that by the end of this module, trainees will be comfortable :Navigating the three tabs in the toolkit to find the information that they needUsing the search functionNavigating the toolkit using the internal linksKnow about mappings and workflows, but not necessarily how to create one
• #6: We will only log into the individual profile if we have time.***This training module has been organized so that logging in to the individual account is not necessary until trainees reach the section about setting bookmarks and creating workflows and mappings.
• #7: When finding the toolkit through a search engine this is the page that will usually be foundThe RDA toolkit is also in the McGill catalog, we can access it that way too!!From here we can access the toolkit by clicking on the ACCESS button
• #8: We have a good range of functionalities when just logged into the McGill account.We can:Browse RDAAACR2LCSPShared workflows and mappingsWe cannot:Create our own workflows and mappingsSee or create our personal bookmarksSave searches
• #9: Fancy way of saying that the site will recognize the machines at McGill and log us in automatically.This is what it will look like when you arrive at the toolkit when using a computer on the McGill network. This shot computer is logged into the McGill account but not into a individual account.Get everyone to get to this point and be sure that they are all recognized as McGill University library
• #13: Start here….
• #14: New editions of the elements are added seamlesslyThe toolkit is searchable which allows a new way to navigate this type of materialThe toolkit has an area which allows for user generated work tools to be stored: workflows and mappings. These can be linked to RDA content and external sites so that complete instructions for a procedure can be built within the toolkit.
• #15: We are logged in as McGill and are ready to look through the different content within the toolkit.The first tab we are going to look at is the RDA Tab
• #17: This is the first tab that we will explore
• #18: This way we can see all of the segments located within the RDA section of the ToolkitThe RDA table of contents can always be accessed by clicking on the RDA tab.When flipping between tabs your place will not be lost.
• #19: This shows how far into the RDA content you can browse through the table of contentsThis is also a great example of how the Toolkit links to resources within the toolkit The green LCPS icon indicates that there is a library of congress policy statement associated with this elementThis is one of several types of links that are made within the toolkit
• #20: There aren’t
• #21: If you scroll (or use the TOC to arrive at) to 5.7.1.1 Basic instructions on Recording Dimensions and look at the scope you will see the glossary hyperlinkGlossary hyperlinks are brown with a downward pointing triangle at the endThere is also a LCPS link in this screen shot, and the synch TOC button was used
• #22: Users can navigate to the glossary by using the search functions, the TOC, or via the links scattered throughout the RDA Toolkit
• #23: When browsing sometimes is can get confusing to determine where you are in relation to the larger organization of the Toolkit. To demonstrate this, direct trainees to go into the RDA tab and select any element, then scroll down so that the element that you chose is no longer visible.Users might also have navigated to the glossary during the last explanation, the TOC can be synched to the glossary as an example.To synchronize the table of contents with your location use the synch icon under the search boxYour location will be indicated in bold in the TOC
• #24: The pdf that is created is the entire section. For example if you were viewing 17.4, 17-17.12 would be in the pdf.
• #25: When viewing the RDA elements and sections with only the core elements visible the ‘Core’ icon will appear.**What are the core elements?Certain elements in RDA are identified as core elementsCore elements support user tasksAs a minimum, a resource description for a work, expression, manifestation, or item should include all the core elements that are applicable and readily ascertainable.When viewing the RDA Toolkit without the bookmarks or without the added examples it is indicated by the ‘filtered’ icon
• #27: Kermit
• #30: RDA content can be browsed here through they layout of theFRBR modelThis section is RDA content, it is simply organized in a different way Like other sections this area can be browsed using the table of contentsThis is a useful tool to show how RDA correlates with the FRBR and FRAD modelsLike the RDA section it is easy to flip between the sections, they have been broken down to represent pageFunctional Requirements for Bibliographic Records (FRBR) is a conceptual “entity-relationship” model created by IFLA that relates user tasks of retrieval and access in online library catalogues and bibliographic databases.1 The user tasks are:2 * Find * Identify * Select * ObtainIt represents a more holistic approach to retrieval and access as the relationships between the entities provide links to navigate through the hierarchy of relationships.1There are 3 groups of FRBR entitiesGroup 1 entities deal with the output of artistic or intellectual endeavours which are Work, Expression, Manifestation, and ItemGroup 2 entities deal with the person or corporate body responsible for the output of artistic or intellectual endeavours (Group 1 entities)Group 3 entities deal with the subject of output of the artistic or intellectual endeavour include concepts, objects, events, places
• #35: Shown here is the MARC Bibliographic to RDA MappingBecause MARC is what we use at McGill this tool will be useful to cataloguers beginning to work using RDA. The mapping between MARC and RDA can be found easily, it is listed within the Tools tab, under Mappings in the TOC
• #36: There are many elements mapped to this field.A good example of how rich RDA is and how MARC is limiting the display of this collected information.
• #37: Shown here is the location of the RDA to MARC Bibliographic Mapping (within the Tools tab)Also this shot shows how a mapping looks when there is not a one to one correlation
• #38: 490, 800, 810, 811, 830
• #39: The RDA mappings also include RDA to MARC Authorities
• #40: MODS was developed by Library of Congress' Network Development and Standards Office.
• #41: Workflows can be written to include links to all the resources used in the processing of certain materials. Links within the toolkit can be made as well as links to external sources.When logged into a personal account users can create workflows and share them with colleagues or the publicWhen logged into just the McGill account shared workflows can still be used
• #43: The Entity Relationship Diagram (ERD) tool includes :an overview of the relationship of FRBR and FRADdiagrams of Core, Enhanced and Specialized for each of the Attributes Primary, Core and Enhanced for the Relationships for each of the FRBR entities and diagrams of Core,Enhanced and Specialized for the FRAD Attribute Name
• #44: Core RDA elements for describing a work displayed visuallyThis has embedded links that lead users to the RDA elements listed
• #45: Another example of this information displayed visually
• #47: When in AACR2 (or in other resources) you can toggle between tabs you can flip back to the RDA tab to compare content
• #48: AACR2 is linked to throughout the RDA Toolkit and can be accessed through any icon that looks like this.
• #59: 2.8.2.411.13.1.319.2.1.3
• #64: 12 outside of the glossary4 when limited
• #67: Searching in RDA documents one can find all instances of specific AACR2 rules
• #68: This section is not necessary for all training sessions, or for all users of the toolkit.If time allows, this section will cover the additional functionalities that users have access to when they create an individual profile.
• #69: Add the user profile icon to the upper right hand cornerBenefits
• #74: This was the login used for the March 22nd trial training session
• #75: The visual cues associated with being logging into a user profile are the institutional name, the full name of the single user. Also, the my profile , support and log out buttons.
• #76: This is a redo of slide #74The following visual cues are associated with being logged into a user profile: welcome user, institutional name, my profile , support and logout buttons
• #82: Click on Bookmark in the “Managing Personalizations” section of “My Profile” to link to the bookmarked section of RDAThe Bookmark maybe Deleted by clicking “Delete”
• #84: Assign each person a different number within section 17.  17.1, 17.2 etc…Section 17 goes up to 12.
• #87: Where can we find the workflows and mappings?
• #88: This is also available to see in the toolkit under tools
• #93: From this we can see that the workflows can be set up to accommodate a variety of styles.
• #95: Again, this is just an introduction to user generated mappings and workflows. Additional training or practice will be needed to learn to create high quality and useful mappings or workflows.
• #96: This is a screen shot to show what the mapping editor looks like
• #99: All workflows created by an individual are listed in their profile. They are the only user that can change the content of the original document.Access to the individual workflows or mappings can be changed from the user profile.
• #100: Image of the workflow editor