Core Competencies and Education for a Career in Cataloging Interest Group

2019 Midwinter Meeting Notes

  • 1.  2019 Midwinter Meeting Notes

    Posted May 22, 2019 09:20 AM
    Welcome and Overview
    The Interest Group meeting began with Gretchen Hoffman and Bobby Bothmann sharing some of what they had learned earlier in the day while attending the ALA preconference on the RDA 3R Toolkit. While the text was not yet stable and there still was no text for the LC-PCC Policy Statements for the revision, the big revelation was that RDA 3R would not be usable until such time as the "application profiles" are constructed. An application profile is a set of entities, attributes, and relationships labeled as mandatory or mandatory if applicable for the description of a specific type of resource, such as a book, integrating resource, moving image on DVD video, etc. A good example of an application profile are the BSRs found on the BIBCO and CONSER websites.

    We then introduced Danny Joudrey, professor at Simmons University and current co-vice-chair of the interest group, who explained the IFLA-LRM. What follows are my (Bobby Bothmann) notes from Danny's slides (attached).

    Notes for LRM Slides

    Why the LRM? Started with FRBR, then FRAD, followed by FRSAD

    There were conflicts among the three models, such as over "name" which was an attribute in FRBR and an entity in FRDA. Subjects were treated differently. Differences have been harmonized in LRM


    LRM is abstract, still an entity relationship model, still has many of the same things we saw in the original models (FRBR, …)

    LRM simplifies. Much of FRAD is gone in LRM. LRM eliminates administrative focus, refocusing on the user.


    Changes in LRM

    The user tasks have been slightly redefined. Explore has been added. Justify and Contextualize have been removed

    Users are now just normal people--catalogers and librarians have been removed from the scope


    Entities have been changed into 3 hierarchical tiers

    Res is now the top level. The third level contains Person and Collective agent, which are subentities of Agent. All the other entities are subentities of Res in the second level.

    Former group 2 entites are now part of the superclass Agent. Place is now an entity of its own. Nomen is new and is the name or label that applies to a given entity. 

    Attributes and Relationships have also changed. The hierarchy allows for trickling down of meaning. That is, what is true for Agent is also true for the subentities Person and Collective agent. More emphasis on relationships and less concern about attributes. Current RDA has a lot of attributes about the manifestation and expression, which are reduced in LRM in favor of relationships.


    LRM presents a much smaller list of attributes. It doesn't mean you cannot describe them, they are simply not presented. Many attributes have been replaced with relationships. Form of expression is now Category.


    LRM identifies 36 relationships. Retains the high level FRBR relationships. Some relationships have been deprecated others have been redefined. Under FRBR only a work can be created. In LRM the Expression and the Manifestation can now be created as well.

    In FRBR a Work can have a subject either from Group 3 and/or 2. In the LRM a Work has a Res as a subject.


    Relationships have all been defined. For example a Res is associated with a Res. A Res has an appellation (name). Will continue to see whole-part relationships.

    Person has been redefined to be only a person who lived. This has repercussions for fictitious characters, etc. The fictitious character is then a nomen for a real person.

    RDA 3R

    It is aligning with LRM, to move toward a more linked data structure, greater internationalisation, and accommodate practice outside of Anglo/Western concepts.

    What does this all mean? We are moving into a content standard that is no longer rules. I will not tell us what to do. It is a system that will provide options and someone will have to decide what those options shall be, which will be called Application Profile.

    Who will create these Application Profiles? It may be a hot potato that is passed around.


    Structure. There are 13 entries are the focal points (chapters) with 1700+ elements each with its own page .

    There are more work related elements than manifestation elements.



    New navigation, but instruction numbers are gone but the toolkit will generate a random citation number that can be used to retrieve a specific instruction/element.

    Eventually there will be a hierarchy browser.

    There is no more core--everything is optional. Recording methods are optional. Each data element will have to be cited as to source/provenance. Much of this will be set forth and dictated by the application profile.

    Discussion Session 

    A lively discussion followed the presentation. Attendees had concerns about Revised RDA and how it would be applied in practice. There was a discussion about who would create the application profile(s) (LC/PCC? Subject Communities? Individual libraries?), and how much responsibility would be placed on individual libraries to develop policy. This could be a challenge for smaller libraries. Attendees also were concerned about having no set instructions, and how that would affect the creation of standard bibliographic records. Educators shared similar concerns, especially how Revised RDA will affect the teaching and learning of cataloging.  


    Bobby Bothmann
    Professor, Library Services
    Metadata & Emerging Technologies Librarian
    Minnesota State University, Mankato