The document discusses recording methods and transcription guidelines for RDA cataloging. It defines the four RDA recording methods: unstructured description, structured description, identifier, and IRI. Examples of each are provided. The document also discusses manifestation statements and provides guidelines for basic and normalized transcription of manifestation statements.
This document discusses proposed changes to the RDA Toolkit guidance on data provenance. It introduces the concept of "metadata works" to represent metadata statements and description sets and their relationships to other entities and sources. It provides more granular guidance on recording sources of metadata and proposes using a vocabulary encoding scheme to record source elements. The changes aim to better align RDA with the Library Reference Model and support linked data and local applications.
This document discusses authority control and creating access points according to RDA. It begins with learning outcomes and an overview. Key terminology is defined, such as RDA entities, elements, appellations, access points, and relationships. The basics of creating access points are covered, including their basis in RDA entities and additions to them. Practical examples are provided of recording access points and their elements in metadata description sets.
New Concepts: Representative Expressions and Manifestation StatementsALAeLearningSolutions
This document discusses the concepts of representative expressions and manifestation statements in RDA. It explains that RDA 2020 introduces the concept of representative expression, which is an attribute of a work used to record essential characteristics from a canonical expression of that work. It provides examples of how representative expressions would be recorded in RDF triples and MARC records. The document also outlines the various representative expression elements that can be used to describe different types of works.
This document discusses aggregates and diachronic works. It defines an aggregate as a manifestation that embodies an aggregating work and one or more expressions. It describes different types of aggregates like aggregate collections and parallel aggregates. It also defines a diachronic work as a work that is planned to be embodied over time. Diachronic works include serials and other resources issued over time. The document outlines how aggregates and diachronic works are modeled in RDA and IFLA LRM, and provides guidance on cataloging these types of resources.
This document summarizes a workshop on application profiles held on August 12, 2019. It discusses the purpose and components of application profiles, including choosing which RDA elements and instructions to include, how to document profiles, and issues around developing and managing profiles for different communities and institutions. The workshop covered drivers of choice in RDA, characteristics of application profiles, ways to specify elements and parameters in a profile, and options for documenting profiles, with the goal of helping participants understand and implement application profiles.
The document discusses the development of the concept of "nomen" in RDA and its related standards. It traces how nomen originated in earlier models like FRBR, FRAD, and FRSAD as a way to designate entities and was consolidated in LRM. LRM defines nomen as an association between an entity and its designation, with attributes like category, language, and script. This lays the conceptual groundwork for nomen in RDA, where it is defined as a designation that refers to an RDA entity.
This document discusses timespan as a new entity in the Library Reference Model (LRM) which forms the basis for the 2020 revision of RDA. Some key points:
- In LRM, timespan is modeled separately from other entities like work and expression, with its own attributes and relationships.
- A timespan has a beginning, end, and duration. Common examples given are years, eras, or specific dates/times.
- Current cataloging already uses timespan concepts like date strings, but the new model provides a standardized framework.
- Elements like preferred name, authorized access point, category, beginning and end can be used to fully describe a timespan metadata description set.
New Concepts: Representative Expressions and Manifestation Statements (Februa...ALAeLearningSolutions
The document discusses new concepts in RDA related to representative expressions and manifestation statements. It introduces the concept of representative expressions, which are attributes deemed essential for characterizing a work, taken from a representative expression of that work. This allows attributes of expressions like language and intended audience to be recorded at the work level. It outlines the new representative expression elements in RDA for different types of works and shows how representative expressions are represented in RDA metadata description sets using RDF triples.
This document discusses proposed changes to the RDA Toolkit guidance on data provenance. It introduces the concept of "metadata works" to represent metadata statements and description sets and their relationships to other entities and sources. It provides more granular guidance on recording sources of metadata and proposes using a vocabulary encoding scheme to record source elements. The changes aim to better align RDA with the Library Reference Model and support linked data and local applications.
This document discusses authority control and creating access points according to RDA. It begins with learning outcomes and an overview. Key terminology is defined, such as RDA entities, elements, appellations, access points, and relationships. The basics of creating access points are covered, including their basis in RDA entities and additions to them. Practical examples are provided of recording access points and their elements in metadata description sets.
New Concepts: Representative Expressions and Manifestation StatementsALAeLearningSolutions
This document discusses the concepts of representative expressions and manifestation statements in RDA. It explains that RDA 2020 introduces the concept of representative expression, which is an attribute of a work used to record essential characteristics from a canonical expression of that work. It provides examples of how representative expressions would be recorded in RDF triples and MARC records. The document also outlines the various representative expression elements that can be used to describe different types of works.
This document discusses aggregates and diachronic works. It defines an aggregate as a manifestation that embodies an aggregating work and one or more expressions. It describes different types of aggregates like aggregate collections and parallel aggregates. It also defines a diachronic work as a work that is planned to be embodied over time. Diachronic works include serials and other resources issued over time. The document outlines how aggregates and diachronic works are modeled in RDA and IFLA LRM, and provides guidance on cataloging these types of resources.
This document summarizes a workshop on application profiles held on August 12, 2019. It discusses the purpose and components of application profiles, including choosing which RDA elements and instructions to include, how to document profiles, and issues around developing and managing profiles for different communities and institutions. The workshop covered drivers of choice in RDA, characteristics of application profiles, ways to specify elements and parameters in a profile, and options for documenting profiles, with the goal of helping participants understand and implement application profiles.
The document discusses the development of the concept of "nomen" in RDA and its related standards. It traces how nomen originated in earlier models like FRBR, FRAD, and FRSAD as a way to designate entities and was consolidated in LRM. LRM defines nomen as an association between an entity and its designation, with attributes like category, language, and script. This lays the conceptual groundwork for nomen in RDA, where it is defined as a designation that refers to an RDA entity.
This document discusses timespan as a new entity in the Library Reference Model (LRM) which forms the basis for the 2020 revision of RDA. Some key points:
- In LRM, timespan is modeled separately from other entities like work and expression, with its own attributes and relationships.
- A timespan has a beginning, end, and duration. Common examples given are years, eras, or specific dates/times.
- Current cataloging already uses timespan concepts like date strings, but the new model provides a standardized framework.
- Elements like preferred name, authorized access point, category, beginning and end can be used to fully describe a timespan metadata description set.
New Concepts: Representative Expressions and Manifestation Statements (Februa...ALAeLearningSolutions
The document discusses new concepts in RDA related to representative expressions and manifestation statements. It introduces the concept of representative expressions, which are attributes deemed essential for characterizing a work, taken from a representative expression of that work. This allows attributes of expressions like language and intended audience to be recorded at the work level. It outlines the new representative expression elements in RDA for different types of works and shows how representative expressions are represented in RDA metadata description sets using RDF triples.
1. The document discusses relationship elements in RDA, which have grown in number but are treated more consistently.
2. It covers topics like the entities and relationships from FRBR, FRAD, and FRSAD; the effect of the LRM on relationships; and exploring special cases like nomen as relationships and relationships in coherent and minimum descriptions.
3. The document examines the transition from designators to discrete relationship elements, and how some attributes became relationships due to new entities like timespan and place.
This document discusses timespan as an entity in RDA and LRM. Some key points:
- In LRM, timespan is modeled as a separate entity with relationships to other entities, rather than as an attribute. A timespan has a beginning, end, and duration.
- Current cataloging already uses timespans extensively through fields like dates and controlled access points representing time periods.
- In RDA, a timespan is described by a metadata description set which records identifying information like name, preferred name, or authorized access point for the timespan. This models how timespans are currently described in bibliographic records and authority records.
The document discusses relationship elements in RDA. It provides an overview of relationship elements, covering topics like the entities and relationships identified in FRBR, FRAD, and FRSAD. It also discusses the Library Reference Model and how it affected relationships in RDA. The document explores relationship elements in more depth, examining the domains and ranges of relationships and different recording methods for relationships in RDA.
The document discusses the development of the concept of "nomen" in RDA and its precursor models. It traces how nomen emerged in FRBR, FRAD, and FRSAD to refer to names, identifiers, and controlled access points. In LRM, nomen was defined as an association between an entity and its designation. RDA adopted nomen as a designation that refers to an RDA entity. The document outlines the descriptive elements for nomen in RDA, including category, context of use, intended audience, language, script, and others. It provides examples of using these elements in RDF triples to describe nomens.
Tools of our Trade (RDA, MARC21) 2010-03-15Ann Chapman
UKOLN is supported by various organizations. The document discusses tools for resource description like AACR2/RDA and MARC standards. It provides an overview of the development of RDA as the new cataloging standard to replace AACR2, including the goals, structure and timeline of RDA. The relationship between RDA and MARC 21 is also covered.
RDA is the new cataloging standard that replaces AACR2. It is based on FRBR and focuses on user tasks like finding, identifying, selecting, and obtaining resources. RDA uses FRBR entities and relationships to organize descriptive information and focuses on online resources. It differs from AACR2 in areas like elements, vocabularies, transcription, and levels of description. While RDA supports metadata sharing and digital environments, concerns include costs of implementation and difficulty adapting the new standard. The future of RDA remains unclear as it is still being developed.
RDA is a new cataloging standard that aims to make resource description and access more intuitive for users. It is based on FRBR and FRAD models established by IFLA that define bibliographic entities and their attributes and relationships. RDA seeks to accommodate all types of resources, align with the semantic web, and simplify the cataloging process by focusing on recording attributes as they appear. It was implemented in 2013 and emphasizes direct transcription over abbreviations to create more user-friendly records. RDA aims to improve users' ability to find, identify, select, and acquire resources through catalog searches.
RDA (Resource Description and Access) is a new standard for describing library resources, designed to replace AACR2. Library staff, including public services, systems personnel, and catalogers, may have heard mention of RDA but not know much about it or how it will change their daily work. You may have many questions. What is RDA? We'll give a very little bit of history and theoretical background. What is this going to mean for catalogers, ILS managers, and users in the near term? What are the future implications, or, why are we doing this? What are the juicy bits of controversy in cataloger-land? And finally, Do we HAVE to? We'll talk for a while, have some activities that get you thinking, and find out your thoughts on RDA.
Presented at "Captains & Crew Collaborating," the 8th annual paraprofessional conference at J.Y. Joyner Library, East Carolina University.
RDA is a new cataloging standard designed to replace AACR2 and provide guidelines for describing digital resources. It is based on FRBR and FRAD which are models that organize information by user tasks and relationships between entities like works, expressions, manifestations and items. RDA aims to be more intuitive for users by providing more detailed descriptions of resources and is being tested by various libraries and organizations before its full implementation. However, some questions remain regarding its costs and benefits compared to AACR2.
The Why, What, How and When of RDA: the current state of playAnn Chapman
Presentation given as part of the CILIP Executive Briefing on RDA on 23 March 2010 at CILIP HQ, London, and on 30 March 2010 at the Bloomsbury Hotel, London.
Resource Description and Access (RDA), the cataloging standard developed to replace AACR2, will be released in June 2010, and a period of testing and evaluation of the new rules will begin. Join Emily Nimsakont, the NLC’s Cataloging Librarian, to learn the basics of RDA. Topics of discussion will include the goals and basic concepts of RDA, ways in which the new rules will differ from the current rules, and changes to MARC format related to RDA.
The tools of our trade: AACR2/RDA and MARCAnn Chapman
Guest lecture at London Metropolitan University on 13th March 2009. The lecture covered the history behind RDA, the international collaborative process by which it is being developed, an overview of the text and a look at the RDA approach to cataloguing; this was followed by an overview of the history and development process for the MARC format.
The document discusses teaching RDA after the 3R project which restructured and redesigned the RDA Toolkit. It provides recommendations for teachers and students on how to approach teaching post-3R RDA, including focusing on new concepts like LRM entities, understanding navigational changes in the toolkit, and using exercises to describe bibliographic entities and create records. Sample lesson plans are proposed for introductory and advanced academic students as well as practitioners.
The workshop focuses on constructing authorized access points for records under RDA, utilizing the LC/PCC Policy Statements (LCC/PCC PS). This is NOT a NACO workshop. Authorized access points for personal names, corporate bodies, conferences, and works and expressions (titles) will be covered, as will relationship designators for personal names and corporate bodies. Subject headings will not be covered.
This document provides an introduction and overview of Resource Description and Access (RDA), the new cataloging standard that replaces Anglo-American Cataloguing Rules (AACR). RDA is designed for the digital age and is based on Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD). RDA provides more flexibility and is compatible with current metadata standards and encoding formats like MARC. While RDA has some advantages, there are also ongoing considerations and discussions around its implementation.
RDA is a new metadata standard that replaces AACR2. RDA is built on FRBR and FRAD conceptual models which analyze bibliographic data in terms of entities, attributes, and relationships. RDA focuses on the user and aims to provide data that helps users find, identify, select, and obtain resources. Key differences from AACR2 include taking data as it appears, recording relationships explicitly, and avoiding abbreviations to make data easier for users to understand.
New Concepts: Fictitious and Non-human Personages (February 2020)ALAeLearningSolutions
This document discusses the treatment of fictitious and non-human personages in RDA and the Library Reference Model (LRM). It explains that in the LRM, only humans or collectives of humans can be agents, so non-human personages cannot be agents. However, RDA allows non-human personages to be related to works using relationships like "related entity." The document also discusses how pseudonyms work, with examples of treating fictional characters like Geronimo Stilton as pseudonyms. It concludes by discussing ongoing work to provide more guidance on cataloging non-human personages.
This document provides an overview of Resource Description and Access (RDA), the new cataloging standard that will be implemented by the Library of Congress in March 2013 and by the Mansfield Library in April 2013. It discusses why RDA is being adopted now, what RDA is and how it is designed for the digital world and user needs, and how RDA will affect cataloging practice at a core level through accepting existing records and making minor corrections. It also outlines how to identify RDA records and new elements being added, such as relationship terms, content type, media type and carrier type. New practices under RDA like use of "[corrected text]" and abbreviations are also mentioned. Resources for learning more about RDA implementation
This is a short (1.5 hour) presentation for support staff about RDA and the do's and don'ts of editing bibliographic records in MARC format. Covers background material on RDA, identifying RDA records vs AACR2 records, changes to records and cataloging practices due to RDA (fields, vocabularies, terms, etc.), hybrid AACR2/RDA records, and the basic rules of editing (both general and for specific fields).
Cataloging with RDA - Western New York Library Resources CouncilEmily Nimsakont
RDA is the new cataloging code that will replace AACR2. It is based on FRBR and FRAD conceptual models which are entity-relationship models that focus on user tasks. RDA differs significantly from AACR2 in its structure, terminology, transcription practices, and categorization of resources using media, carrier, and content types instead of GMDs. Testing of RDA by national libraries began in 2010 with full implementation planned after the testing period. Libraries need to prepare for RDA by learning the new terminology and monitoring developments during the testing process.
UKOLN is supported by various organizations. The document discusses cataloging standards and formats including AACR2, RDA, MARC, FRBR and ISBD. It provides an overview of the history and development of these standards, their relationship to each other, and goals for RDA to address limitations of AACR2 and be compatible with other standards.
The document discusses Resource Description and Access (RDA), a new cataloging standard that aims to improve findability, identification, and interoperability of library resources. RDA is based on FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data) models. It defines cataloging entities and relationships using Semantic Web technologies like URIs, RDF, and SKOS to make metadata more reusable and linkable on the global scale. The document outlines how RDA entities, elements, and vocabularies are being registered in the NSDL Metadata Registry to enable their representation and sharing using Semantic Web formats.
1. The document discusses relationship elements in RDA, which have grown in number but are treated more consistently.
2. It covers topics like the entities and relationships from FRBR, FRAD, and FRSAD; the effect of the LRM on relationships; and exploring special cases like nomen as relationships and relationships in coherent and minimum descriptions.
3. The document examines the transition from designators to discrete relationship elements, and how some attributes became relationships due to new entities like timespan and place.
This document discusses timespan as an entity in RDA and LRM. Some key points:
- In LRM, timespan is modeled as a separate entity with relationships to other entities, rather than as an attribute. A timespan has a beginning, end, and duration.
- Current cataloging already uses timespans extensively through fields like dates and controlled access points representing time periods.
- In RDA, a timespan is described by a metadata description set which records identifying information like name, preferred name, or authorized access point for the timespan. This models how timespans are currently described in bibliographic records and authority records.
The document discusses relationship elements in RDA. It provides an overview of relationship elements, covering topics like the entities and relationships identified in FRBR, FRAD, and FRSAD. It also discusses the Library Reference Model and how it affected relationships in RDA. The document explores relationship elements in more depth, examining the domains and ranges of relationships and different recording methods for relationships in RDA.
The document discusses the development of the concept of "nomen" in RDA and its precursor models. It traces how nomen emerged in FRBR, FRAD, and FRSAD to refer to names, identifiers, and controlled access points. In LRM, nomen was defined as an association between an entity and its designation. RDA adopted nomen as a designation that refers to an RDA entity. The document outlines the descriptive elements for nomen in RDA, including category, context of use, intended audience, language, script, and others. It provides examples of using these elements in RDF triples to describe nomens.
Tools of our Trade (RDA, MARC21) 2010-03-15Ann Chapman
UKOLN is supported by various organizations. The document discusses tools for resource description like AACR2/RDA and MARC standards. It provides an overview of the development of RDA as the new cataloging standard to replace AACR2, including the goals, structure and timeline of RDA. The relationship between RDA and MARC 21 is also covered.
RDA is the new cataloging standard that replaces AACR2. It is based on FRBR and focuses on user tasks like finding, identifying, selecting, and obtaining resources. RDA uses FRBR entities and relationships to organize descriptive information and focuses on online resources. It differs from AACR2 in areas like elements, vocabularies, transcription, and levels of description. While RDA supports metadata sharing and digital environments, concerns include costs of implementation and difficulty adapting the new standard. The future of RDA remains unclear as it is still being developed.
RDA is a new cataloging standard that aims to make resource description and access more intuitive for users. It is based on FRBR and FRAD models established by IFLA that define bibliographic entities and their attributes and relationships. RDA seeks to accommodate all types of resources, align with the semantic web, and simplify the cataloging process by focusing on recording attributes as they appear. It was implemented in 2013 and emphasizes direct transcription over abbreviations to create more user-friendly records. RDA aims to improve users' ability to find, identify, select, and acquire resources through catalog searches.
RDA (Resource Description and Access) is a new standard for describing library resources, designed to replace AACR2. Library staff, including public services, systems personnel, and catalogers, may have heard mention of RDA but not know much about it or how it will change their daily work. You may have many questions. What is RDA? We'll give a very little bit of history and theoretical background. What is this going to mean for catalogers, ILS managers, and users in the near term? What are the future implications, or, why are we doing this? What are the juicy bits of controversy in cataloger-land? And finally, Do we HAVE to? We'll talk for a while, have some activities that get you thinking, and find out your thoughts on RDA.
Presented at "Captains & Crew Collaborating," the 8th annual paraprofessional conference at J.Y. Joyner Library, East Carolina University.
RDA is a new cataloging standard designed to replace AACR2 and provide guidelines for describing digital resources. It is based on FRBR and FRAD which are models that organize information by user tasks and relationships between entities like works, expressions, manifestations and items. RDA aims to be more intuitive for users by providing more detailed descriptions of resources and is being tested by various libraries and organizations before its full implementation. However, some questions remain regarding its costs and benefits compared to AACR2.
The Why, What, How and When of RDA: the current state of playAnn Chapman
Presentation given as part of the CILIP Executive Briefing on RDA on 23 March 2010 at CILIP HQ, London, and on 30 March 2010 at the Bloomsbury Hotel, London.
Resource Description and Access (RDA), the cataloging standard developed to replace AACR2, will be released in June 2010, and a period of testing and evaluation of the new rules will begin. Join Emily Nimsakont, the NLC’s Cataloging Librarian, to learn the basics of RDA. Topics of discussion will include the goals and basic concepts of RDA, ways in which the new rules will differ from the current rules, and changes to MARC format related to RDA.
The tools of our trade: AACR2/RDA and MARCAnn Chapman
Guest lecture at London Metropolitan University on 13th March 2009. The lecture covered the history behind RDA, the international collaborative process by which it is being developed, an overview of the text and a look at the RDA approach to cataloguing; this was followed by an overview of the history and development process for the MARC format.
The document discusses teaching RDA after the 3R project which restructured and redesigned the RDA Toolkit. It provides recommendations for teachers and students on how to approach teaching post-3R RDA, including focusing on new concepts like LRM entities, understanding navigational changes in the toolkit, and using exercises to describe bibliographic entities and create records. Sample lesson plans are proposed for introductory and advanced academic students as well as practitioners.
The workshop focuses on constructing authorized access points for records under RDA, utilizing the LC/PCC Policy Statements (LCC/PCC PS). This is NOT a NACO workshop. Authorized access points for personal names, corporate bodies, conferences, and works and expressions (titles) will be covered, as will relationship designators for personal names and corporate bodies. Subject headings will not be covered.
This document provides an introduction and overview of Resource Description and Access (RDA), the new cataloging standard that replaces Anglo-American Cataloguing Rules (AACR). RDA is designed for the digital age and is based on Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD). RDA provides more flexibility and is compatible with current metadata standards and encoding formats like MARC. While RDA has some advantages, there are also ongoing considerations and discussions around its implementation.
RDA is a new metadata standard that replaces AACR2. RDA is built on FRBR and FRAD conceptual models which analyze bibliographic data in terms of entities, attributes, and relationships. RDA focuses on the user and aims to provide data that helps users find, identify, select, and obtain resources. Key differences from AACR2 include taking data as it appears, recording relationships explicitly, and avoiding abbreviations to make data easier for users to understand.
New Concepts: Fictitious and Non-human Personages (February 2020)ALAeLearningSolutions
This document discusses the treatment of fictitious and non-human personages in RDA and the Library Reference Model (LRM). It explains that in the LRM, only humans or collectives of humans can be agents, so non-human personages cannot be agents. However, RDA allows non-human personages to be related to works using relationships like "related entity." The document also discusses how pseudonyms work, with examples of treating fictional characters like Geronimo Stilton as pseudonyms. It concludes by discussing ongoing work to provide more guidance on cataloging non-human personages.
This document provides an overview of Resource Description and Access (RDA), the new cataloging standard that will be implemented by the Library of Congress in March 2013 and by the Mansfield Library in April 2013. It discusses why RDA is being adopted now, what RDA is and how it is designed for the digital world and user needs, and how RDA will affect cataloging practice at a core level through accepting existing records and making minor corrections. It also outlines how to identify RDA records and new elements being added, such as relationship terms, content type, media type and carrier type. New practices under RDA like use of "[corrected text]" and abbreviations are also mentioned. Resources for learning more about RDA implementation
This is a short (1.5 hour) presentation for support staff about RDA and the do's and don'ts of editing bibliographic records in MARC format. Covers background material on RDA, identifying RDA records vs AACR2 records, changes to records and cataloging practices due to RDA (fields, vocabularies, terms, etc.), hybrid AACR2/RDA records, and the basic rules of editing (both general and for specific fields).
Cataloging with RDA - Western New York Library Resources CouncilEmily Nimsakont
RDA is the new cataloging code that will replace AACR2. It is based on FRBR and FRAD conceptual models which are entity-relationship models that focus on user tasks. RDA differs significantly from AACR2 in its structure, terminology, transcription practices, and categorization of resources using media, carrier, and content types instead of GMDs. Testing of RDA by national libraries began in 2010 with full implementation planned after the testing period. Libraries need to prepare for RDA by learning the new terminology and monitoring developments during the testing process.
UKOLN is supported by various organizations. The document discusses cataloging standards and formats including AACR2, RDA, MARC, FRBR and ISBD. It provides an overview of the history and development of these standards, their relationship to each other, and goals for RDA to address limitations of AACR2 and be compatible with other standards.
The document discusses Resource Description and Access (RDA), a new cataloging standard that aims to improve findability, identification, and interoperability of library resources. RDA is based on FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data) models. It defines cataloging entities and relationships using Semantic Web technologies like URIs, RDF, and SKOS to make metadata more reusable and linkable on the global scale. The document outlines how RDA entities, elements, and vocabularies are being registered in the NSDL Metadata Registry to enable their representation and sharing using Semantic Web formats.
RDA (Resource Description and Access) is a new cataloging standard that will replace AACR2. It is based on FRBR and defines descriptive elements for resources while separating content from carrier information. RDA aims to be easier to use, applicable online, provide effective description of all media types, and be compatible with other standards like Dublin Core. It will have a logical structure based on entity-relationship modeling and be developed through an open process involving libraries worldwide. RDA is scheduled for full implementation in 2010 and will impact cataloging systems and metadata schemas like MARC 21.
RDA is the new cataloging code that will replace AACR2. It is based on FRBR and FRAD conceptual models and designed to be more flexible and accommodate online resource description. RDA differs from AACR2 in its structure, terminology, categorization of resources, and transcription rules. Testing of RDA began in 2010 by national libraries and partners. Resources are available to help libraries prepare for the transition to RDA.
Chris Oliver: RDA: Designed for Current and Future EnvironmentsALATechSource
RDA is a new metadata standard that replaces AACR2 and provides guidelines for recording bibliographic data to support resource discovery. It is designed to work in current catalogues and databases, as well as take advantage of new technologies through a flexible framework aligned with FRBR and FRAD models. RDA defines discrete data elements that provide precise, machine-actionable data to describe resources and their relationships.
This document summarizes a webinar on deploying Resource Description and Access (RDA) cataloging and expressing it as linked data. The webinar speaker, Alan Danskin from the British Library, discussed RDA as a cataloging standard that provides guidelines for describing resources to support discovery. He explained how RDA works with linked data by using entities, relationships, and attributes expressed as URIs. Challenges in applying RDA as linked data include the complexity of the FRBR model and publishing RDA vocabularies as linked open data. Application profiles help apply RDA by defining the metadata elements, policies, and guidelines for a specific domain or community.
The document discusses metadata schemas and standards for digital library projects in China. It describes several existing metadata schemes including the General Format for Digitalized Chinese Full-text (GFDCF), the CPDLP Metadata Profiles, and the Chinese Metadata Specifications (CMS). It also discusses applying ontologies to build a unified metadata framework, including ontologies of Chinese information resources and bibliographic relations. This would help address issues of lack of unified semantics, mappings between schemas, and diversification in the Chinese metadata landscape.
Future directions for RDA / Gordon DunsireCILIP MDG
The document discusses future directions for the Resource Description and Access (RDA) standard. It outlines strategies for expanding RDA communities internationally and in cultural heritage domains. It also describes plans to consolidate FRBR models, develop related standards, and reorganize the RDA Toolkit. Additionally, it discusses developing a new RDA reference data infrastructure to support multiple services and applying the Linked Data approach. The impact of the new FRBR-LRM conceptual model on RDA is also addressed.
Presented January 18, 2010 to the ALCTS Committee on Cataloging: Description and Access (CC:DA) as an introduction to RDF data, and application profiles. Presenters were Jon Phipps, Karen Coyle and Diane Hillmann.
The new RDA: resource description in libraries and beyond / Gordon DunsireCILIP MDG
This document discusses the new RDA (Resource Description and Access), which provides data elements, guidelines and instructions for creating metadata for library and cultural heritage resources. Key points:
- The RDA Toolkit provides user-focused elements, guidelines and instructions. The RDA Registry provides infrastructure for well-formed, linked RDA data applications.
- There are now 13 entities and over 1700 elements in RDA. Elements are now the main unit of focus and have standard structure/layout.
- Recording methods have been extended to all elements and now make the linked data method explicit. Instructions are now more optional to accommodate local practice.
- Effective description requires choosing appropriate entities and elements based on an application profile
The document summarizes the structure and content of the new cataloging standard Resource Description and Access (RDA). It discusses how RDA was influenced by other standards like FRBR and FRAD and aims to support both current and future database structures. The document outlines that RDA has two main parts - recording attributes and recording relationships. It describes the 10 sections of RDA which cover attributes of different entities and relationships between entities. The document provides details on the sections regarding recording attributes of manifestations, works, persons, and placeholders for other entities. It also explains how RDA will record relationships using access points, identifiers, and relationship designators.
The students in an LS 566 Metadata class were asked to index a collection of six images from the 1992 University of Alabama Crimson Tide football season. The class chose a modified Dublin Core metadata schema containing 15 elements to describe the images. Students worked in groups to define the elements and map them to the images. They used Omeka software to extract image text and connect files to element fields. The indexing process took longer than expected due to a tornado that damaged the university.
This document provides a summary of a presentation about the transition from AACR to RDA (Resource Description and Access).
1) AACR has served libraries well for decades but is no longer suitable for the digital world. RDA is being developed as the new cataloguing standard to address this issue and ensure catalog data is usable online.
2) RDA is based on FRBR (Functional Requirements for Bibliographic Records) and other conceptual models which define bibliographic entities, attributes, and relationships to improve user tasks like finding and identifying resources.
3) Early implementations of RDA show benefits like more organized displays that are easier for users to navigate compared to traditional catalogs without FRBR principles
The document discusses different types of metadata schemas used for digital collections, including Dublin Core (DC), Qualified Dublin Core (QDC), MARC, MARCXML, MODS, VRA Core, CDWA Lite, GEM, LOM, TEI, and EAD. It provides information on the purpose, content standards, limitations, and best uses of each schema. The document is intended as a workshop on metadata for digital collections.
This document provides an overview of describing web resources using the Resource Description Framework (RDF). It discusses the basic concepts of RDF including resources, properties, statements, and the XML syntax used to represent them. It also covers RDF Schema which adds vocabulary for describing properties and classes of RDF resources, and provides a critical view of some aspects of RDF such as its use of binary predicates and treatment of properties.
Cartographic resources cataloging with RDA: An introductionALATechSource
This document provides an overview of changes to cataloging cartographic resources using RDA. It reviews new RDA terminology and concepts, such as core elements. It discusses specific changes to fields like 245, 255, and 300. These include recording scale using representative fractions and expanding abbreviations. The document also introduces new RDA fields like 264 and explains how to handle statements of responsibility and supply information.
Similar to Special Topics: Recording Methods and Transcription Guidelines (July 2019) (20)
Other Duties as Assigned: Training Your Staff for Evolving Responsibilities (...ALAeLearningSolutions
Kim Crowder is a consultant who provides training on reorganizing and reimagining staff teams. In this presentation, she outlines her approach to defining organizational needs, examining skill gaps, identifying existing talents, and making gradual shifts to transform the team. Her methodology includes collaborating with staff to create a shared vision, identifying strengths and opportunities, providing training, and maintaining high morale during the process of change. The goal is to develop a team with complimentary skills that can achieve organizational goals.
Building Great Programs for Seniors: Presenter Outline (July 2020)ALAeLearningSolutions
The document provides many ideas for programming and services for senior citizens at libraries. It discusses ideas like technology training classes, book clubs focused on different decades, craft programs, health and wellness activities, history and genealogy programs, and more. The ideas are aimed at making programming accessible and engaging for older adults. Friends groups and volunteers are mentioned as ways to help fund and support senior programming. Partnerships with other organizations serving seniors are also recommended. The document contains a wealth of specific program topic ideas spanning areas like history, arts, health, technology, and more.
This document provides ideas for senior programming at libraries. It includes topics like health and fitness, crafts, history, entertainment and more. Suggestions are made for both in-person and online virtual events. The document emphasizes making events accessible, repeating popular ones, partnering with other organizations, and gathering input from seniors on their interests. Overall it aims to engage and support the senior community with lifelong learning and social opportunities at local libraries.
Building Great Programs for Patrons in their 20s and 30s (July 2020)ALAeLearningSolutions
This document provides guidance on building library programs that cater to patrons in their 20s and 30s. It discusses defining the target demographic, learning about the local community, establishing goals, strategic timing of programs, and inclusive programming. Suggested program themes include nostalgia, DIY/crafts, education, off-site events, and addressing unique needs. The importance of marketing, budgets, and measuring outcomes is also covered. The goal is for all patrons to view the library as relevant to their lives.
Increase Your Circulation with Visual Merchandising: Bookstore Display Princi...ALAeLearningSolutions
This document provides tips for libraries to increase circulation through effective visual merchandising. It recommends libraries start by studying customer traffic patterns and space usage to identify areas for improvement. Proper display techniques are important, such as facing books outwards, keeping straight lines, and maintaining balance and symmetry. Displays should be used to promote specific topics, collections, or events. Effectiveness can be measured through circulation, customer feedback, and door counts. Challenges include limited staffing, funds and space, but creativity can help overcome these. Cohesive branding and systematizing responsibilities can aid implementation.
This document provides an overview of relationships in RDA, including definitions of key terms, characteristics of relationships, relationship elements, and recording methods. It discusses what a relationship is, how relationships are expressed in RDA through relationship elements, and how each relationship element has a domain and range. It also briefly outlines the different types of recording methods available in RDA and how unstructured descriptions can be used. Finally, it provides information on accessing exercises and application profiles related to relationships through the RDA Toolkit.
Balancing Library Management with Day-to-Day Responsibilities: OutlineALAeLearningSolutions
The document summarizes a webinar on juggling day-to-day responsibilities for library managers. It covers checking in with participants, prioritizing responsibilities, decision making, time management, and communication. The webinar suggests developing a personal mission statement to prioritize tasks, accepting that decisions involve risk and learning from mistakes, managing time by saying no and focusing on one task at a time, and communicating clearly, listening actively, and being transparent while managing expectations. The webinar provides tips and resources to help library managers balance different responsibilities.
Balancing Library Management with Day-to-Day Responsibilities: Notes & Refere...ALAeLearningSolutions
This document provides resources for webinars, self-reflection tools, mental health resources, and training opportunities for library workers. It includes links to webinar recordings on topics like self-care during COVID-19 and compassionate leadership. Lists of free resources are also included, such as mindfulness groups on Facebook and time management software. References for books on management, joy at work, and doing nothing are listed as potential paid resources.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
This document provides guidance for librarians on creating effective online storytimes. It begins by discussing the differences between in-person and online storytimes, noting that online storytimes lack visual interaction and environmental control. The document emphasizes fostering connection over content. It provides tips for planning online storytimes, such as choosing interactive materials, deciding between live or recorded formats, and ensuring accessibility. Technical setup recommendations are offered. Presentation tips include speaking slowly, making eye contact with the camera, allowing time for responses, and using repetition. Worries like technical issues and public speaking nerves are addressed. Resources for online programming, copyright guidance, and professional development are listed.
Liven Up Baby and Toddler Storytimes with Sign Language (June 2020)ALAeLearningSolutions
This document discusses how to incorporate American Sign Language (ASL) into baby and toddler storytimes. It explains that using signs can aid language development, empower children to communicate before speaking, and make storytimes more inclusive. The presenter recommends choosing a limited number of signs to use consistently, practicing the signs, and providing context and follow-up materials to parents. Hands-on ideas for using signs in stories, songs, and routines are provided. Resources for learning signs like books, videos, and websites are also shared.
American Libraries Live—Libraries and COVID-19: Reimagining Programming durin...ALAeLearningSolutions
This document summarizes an online discussion between Amy Alessio, a library programming expert, and Sydney Krawiec, a youth services librarian. The discussion focused on how libraries can reimagine programming during the COVID-19 pandemic, including starting alternative programming, promoting new virtual offerings, and planning for a transition back to in-person events. Questions from the audience addressed challenges with programming during this time and strategies for moving programming online.
Effective Library Signage: Tips, Tricks, & Best Practices (May 2020)ALAeLearningSolutions
The document provides tips and best practices for effective library signage based on a library's experience conducting signage audits and assessments. It discusses the importance of signage, types of signs, conducting audits, replacing signs, and maintaining effectiveness. Key recommendations include using consistent templates, clear and simple messages, realistic images, ADA compliance, flexible policies, and continuous assessment.
How to Respond to a Security Incident in Your Library (May 2020)ALAeLearningSolutions
The document provides guidance on responding to security incidents at libraries. It discusses developing plans and policies for staff and patron safety, as well as facility safety. Common security-related incidents that libraries may face are outlined, such as unruly patrons, domestic violence situations, homeless individuals, and medical emergencies. The document emphasizes preparing for incidents through training, having contact with law enforcement, and focusing on de-escalation and solutions rather than just rules when responding to issues.
This document provides guidance on best practices for using images on the web and social media. It discusses the differences between raster and vector images, recommends file formats like JPG, PNG and GIF for different uses, and stresses the importance of optimizing image file sizes for faster loading. The document also offers tips on image naming, alt text, resizing and quality checks. It provides links to free stock image sites and services for compressing image files. The overall message is that images should be high quality, optimized for size and format, and properly named and described to enhance user experience on websites and social media.
Kathy MacMillan presented on creating outstanding online storytimes. She discussed the differences between in-person and online storytimes and how the goals remain the same but the delivery changes. Some key points included choosing interactive materials that work visually online, planning presentations around 10-20 minutes with repetition and explicit instructions, and focusing on fostering connection over perfection. Technical considerations like live vs recorded, registration, and accessibility were also covered.
This document outlines a discussion on providing virtual services for libraries during COVID-19. It discusses evaluating a library's digital resources and services, understanding patron needs when buildings are closed, and ways to share resources virtually. It also addresses staff needs for working remotely, such as tools and skills, as well as balancing practical short-term solutions with future-proofing the library. The document includes introductions from presenters David and Jason and concludes with a Q&A section.
Navigating Chaotic Waters: Adjusting to New Working Circumstances during a Pa...ALAeLearningSolutions
This document shares various resources for navigating work during the pandemic, including websites, apps, guides and webinars focused on mindfulness, well-being, physical activity, meditation, journaling, and reopening plans and guidance from library organizations. Links are provided to live animal cameras, workout apps, mindfulness guides, podcasts, and articles about managing stress and transitioning back to in-person work.
Navigating Chaotic Waters: Adjusting to New Working Circumstances during a Pa...ALAeLearningSolutions
This webinar discusses navigating work during the COVID-19 pandemic. The presenter outlines different types of stress like acute, episodic acute, and chronic stress. They discuss adjusting to telecommuting and working from home, including setting work-life boundaries and self-care strategies. Suggestions are provided for managers to support staff well-being and avoid layoffs during budget cuts. The presentation emphasizes staying connected as a community for hope and advocacy.
A Free 200-Page eBook ~ Brain and Mind Exercise.pptxOH TEIK BIN
(A Free eBook comprising 3 Sets of Presentation of a selection of Puzzles, Brain Teasers and Thinking Problems to exercise both the mind and the Right and Left Brain. To help keep the mind and brain fit and healthy. Good for both the young and old alike.
Answers are given for all the puzzles and problems.)
With Metta,
Bro. Oh Teik Bin 🙏🤓🤔🥰
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...TechSoup
Whether you're new to SEO or looking to refine your existing strategies, this webinar will provide you with actionable insights and practical tips to elevate your nonprofit's online presence.
Brand Guideline of Bashundhara A4 Paper - 2024khabri85
It outlines the basic identity elements such as symbol, logotype, colors, and typefaces. It provides examples of applying the identity to materials like letterhead, business cards, reports, folders, and websites.
THE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...indexPub
The recent surge in pro-Palestine student activism has prompted significant responses from universities, ranging from negotiations and divestment commitments to increased transparency about investments in companies supporting the war on Gaza. This activism has led to the cessation of student encampments but also highlighted the substantial sacrifices made by students, including academic disruptions and personal risks. The primary drivers of these protests are poor university administration, lack of transparency, and inadequate communication between officials and students. This study examines the profound emotional, psychological, and professional impacts on students engaged in pro-Palestine protests, focusing on Generation Z's (Gen-Z) activism dynamics. This paper explores the significant sacrifices made by these students and even the professors supporting the pro-Palestine movement, with a focus on recent global movements. Through an in-depth analysis of printed and electronic media, the study examines the impacts of these sacrifices on the academic and personal lives of those involved. The paper highlights examples from various universities, demonstrating student activism's long-term and short-term effects, including disciplinary actions, social backlash, and career implications. The researchers also explore the broader implications of student sacrifices. The findings reveal that these sacrifices are driven by a profound commitment to justice and human rights, and are influenced by the increasing availability of information, peer interactions, and personal convictions. The study also discusses the broader implications of this activism, comparing it to historical precedents and assessing its potential to influence policy and public opinion. The emotional and psychological toll on student activists is significant, but their sense of purpose and community support mitigates some of these challenges. However, the researchers call for acknowledging the broader Impact of these sacrifices on the future global movement of FreePalestine.
Creative Restart 2024: Mike Martin - Finding a way around “no”Taste
Ideas that are good for business and good for the world that we live in, are what I’m passionate about.
Some ideas take a year to make, some take 8 years. I want to share two projects that best illustrate this and why it is never good to stop at “no”.
How to Setup Default Value for a Field in Odoo 17Celine George
In Odoo, we can set a default value for a field during the creation of a record for a model. We have many methods in odoo for setting a default value to the field.
Special Topics: Recording Methods and Transcription Guidelines (July 2019)
1. RDA Special Topic Series
RDA Recording Methods and
Transcription Guidelines
July 16, 20191
2. RDA Special Topic Series July 16, 20192
Learning Objectives
Define four RDA recording methods
Understand the role of each recording method in
current and future cataloging practices
Apply unstructured description to creating
manifestation statements
Distinguish between basic and normalized
transcription
3. RDA Special Topic Series July 16, 20193
Agenda
Origins of the recording methods
Definitions and examples
Recording statements in RDA elements pages
Manifestation Statements
Basic transcriptions
Normalized transcriptions
Manifestation statement elements
Elements for recording structured statements
4. RDA Special Topic Series 22 October 20184
Recording Methods
(4-fold path)
• Four ways to capture data
• Included in every element
chapter
With an indication of
applicability
• Can use more than one,
if applicable and desired
For example, transcribing
the publisher and
providing an access
point for the publisher
5. RDA Special Topic Series July 16, 20195
Origins of the Recording
Methods
8. RDA Special Topic Series July 16, 20198
Current RDA Examples of Recording
Methods
Unstructured Description of related manifestation:
Also issued electronically via World Wide Web in PDF format
Structured Description of related manifestation:
Also issued as: Large print edition. — Thorndike, Maine : Center Point
Publishing, [2005]
Identifier for the related manifestation:
Issued with: ISBN 978-0-7575-4388-3
Examples taken from RDA 27.1.1.3
Chapter 17 Example:
http://larvatusprodeo.net
10. RDA Special Topic Series July 16, 201910
Unstructured Description
A recording method that is a human-readable string
that is an uncontrolled full or partial description of
an entity or an uncontrolled term describing an
aspect of an entity.
Includes a note, a transcription, a name or title as it
appears in a source of information, and an
uncontrolled term. – RDA Glossary
11. RDA Special Topic Series July 16, 201911
Unstructured Description
Text string – Nomen
Transcribed data: what you see is what you get
Current practice in descriptive cataloging
Useful for: non-standard metadata from non-
professional sources lacking provenance (authority)
Access: only keyword searching and indexing (least
useful method)
Only supports user task of Identify
Source: Linda Barnhardt, “RDA Data Recording Methods, Transcription,
and Manifestation Statements”
12. RDA Special Topic Series July 16, 201912
Examples
J.R.R Tolkien
The Hobbit, or, There and Back Again
G. Allen & Unwin
London
By J.R.R. Tolkien
A tale of the adventure of a company of dwarves in search of dragon-
guarded gold. A reluctant partner in this perilous quest is Bilbo Baggins, a
comfort-loving, unambitious hobbit, who surprises even himself by his
resourcefulness and skill as a burglar.
13. RDA Special Topic Series July 16, 201913
Structured Description
“A string that is a full or partial description of an
entity based on a syntax or string encoding scheme
or a controlled term describing an aspect of an
entity. Includes an access point or a controlled term
taken from a vocabulary encoding scheme.” – RDA
Glossary
14. RDA Special Topic Series July 16, 201914
Structured Description
Text string – Nomen
Data recorded in standard, structured formats for
human users
We do this now: utilize data from authority files,
vocabulary encoding schemes [VES], knowledge
organization systems
Includes authorized and variant access points, other
controlled terms
Access: Collocation and Indexing
User tasks: Find, Identify, Explore
Source: Linda Barnhardt, “RDA Data Recording Methods, Transcription,
and Manifestation Statements”
15. RDA Special Topic Series July 16, 201915
Examples
Dickens, Charles, 1812-1870, [authorized access point for person]
Dickens, Charles, 1812-1870. Bleak house. [authorized access point for
work (name of work)]
performed music [term from RDA content type VES]
unmediated [term from RDA media type VES]
Sonatina, op. 52, no. 1 / Lennox Berkeley (10:36) -- Segovia : op. 29 /
Albert Roussel (2:19) [Contents note in ISBD syntax]
polychrome [term from RDA colour content VES]
16. RDA Special Topic Series July 16, 201916
Identifier
A recording method that is a machine-readable
string that is assigned to an entity in order to
differentiate the entity from other entities within a
local domain, or a notation for a term from a
controlled vocabulary that is assigned to an aspect of
the entity.
Includes an identifier or notation taken from a
vocabulary encoding scheme. – RDA Glossary
17. RDA Special Topic Series July 16, 201917
Identifier
Text string – Nomen
Coded labels intended for machine identification
We include and use identifiers for searching for
bibliographic data
Unique within a local scheme
Includes: authority control numbers, standard identifier
schemes, terminology notations
Access: indexing and relational database applications
Source: Linda Barnhardt, “RDA Data Recording Methods, Transcription,
and Manifestation Statements”
18. RDA Special Topic Series July 16, 201918
Examples
978-0-307-70157-2 (ISBN)
0028-0038 (ISSN)
457 348-2 (publisher’s number)
02454311421550 (UPC)
2002-27097 (LCCN)
95218067 (VIAF)
19. RDA Special Topic Series July 16, 201919
IRI – Internationalized Resource
Identifier
A recording method that is a string that is assigned
to an entity in machine-readable form in order to
differentiate the entity from other entities, or to an
aspect of an entity, within the global domain of the
semantic web and open linked data. – RDA Glossary
20. RDA Special Topic Series July 16, 201920
IRI
IRI is a “thing,” not a string – “Real-world object”
Unique within a global domain: the Semantic Web of
linked data
Data for “smart” machine applications
Not easily interpretable by humans
Access: Semantic Web and linked open data
New type of recording method
Source: Linda Barnhardt, “RDA Data Recording Methods, Transcription,
and Manifestation Statements”
21. RDA Special Topic Series July 16, 201921
Examples
RDA Vocabulary Encoding Scheme Carrier Type Term for
audiotape reel.
http://rdaregistry.info/termList/RDACarrierType/1008
Tolkien, J. R. R. (John Ronald Reuel), 1892-1973. (LCNAF)
IRI: http://id.loc.gov/authorities/names/n79005673
Tolkien, J. R. R. (John Ronald Reuel), 1892-1973. (VIAF)
IRI: http://viaf.org/viaf/95218067
22. RDA Special Topic Series July 16, 201922
Four Recording Methods
Not all methods are applicable to all elements
Example: an unstructured description is not applicable for an
authorized access point for person, which is a structured
description.
Structured-descriptions can be formulated by combining
unstructured descriptions.
23. RDA Special Topic Series23
Example
Tolkien, J. R. R. (John Ronald Reuel), 1892-1973.
Structured description, assembled from components/sources above
J. R. R. Tolkien Unstructured description, taken from associated
resource
John Ronald Reuel Unstructured description, taken from reference
source
1892-1973 Structured description for a timespan using
syntax encoding scheme for date/time
24. RDA Special Topic Series July 16, 201924
Recording Methods in RDA Beta
29. RDA Special Topic Series 22 October 201829
Recording Methods - Review
Data Source Recording Method Example
Manifestation – transcription Unstructured Montreal
Authority file – authorized
access point
Structured Montréal (Québec)
Getty Thesaurus of
Geographic Names Identifier
Identifier 7013051
LC/NACO Authority File
Control Number
Identifier n 80132975
DBPedia URI IRI http://dbpedia.org/resource/Mo
ntreal
GeoNames URI IRI http://sws.geonames.org/60772
43/
31. RDA Special Topic Series July 16, 201931
Definition
A statement appearing in a manifestation and
deemed to be significant for users to understand
how the manifestation represents itself.
32. RDA Special Topic Series July 16, 201932
Manifestation Statements
A manifestation may carry information that describes the
manifestation itself.
This information is recorded to follow the principle of
representation.
A manifestation statement supports the user
task identify.
33. RDA Special Topic Series July 16, 201933
Transcription Methods:
Basic Transcription
Preserve the capitalization, punctuation, numerals, and
diacritics as they appear on the manifestation.
Omit symbols or other images intended to be interpreted
as text that are not available in the character set used by
the agent who creates the transcription.
34. RDA Special Topic Series July 16, 201934
Basic Transcription Guidelines
Transcribe the components of a manifestation statement in the
order in which they appear on the manifestation.
Use “” to delimit the separate components of a statement.
Use the mark of omission “…” to indicate the omission of text
within a statement.
Optionally, also use the mark of omission to indicate the
omission of text at the beginning and end of a statement.
Collapse “white space”, including multiple spaces, new line,
indentation, tabs and block alignments, etc., to a single space.
De-duplicate contiguous marks of omission.
De-duplicate contiguous delimiters.
De-duplicate strings in a manifestation statement.
35. RDA Special Topic Series July 16, 201935
Normalized Transcription
Guidelines deal with transcribing elements following
more traditional cataloging practice
Language and script
Diacritics
Capitalization
Punctuation
Spacing of initials and acronyms
Abbreviations and symbols
Numbers
Very similar to current RDA 1.7.1
36. RDA Special Topic Series36
Manifestation Statement: Basic Transcription
Source:
EOIN MCNAMEE
CITY OF TIME
Illustrated by Jon Goodell
WENDY LAMB BOOKS
Transcription:
Basic transcription: capitalization,
punctuation, numerals and diacritics
are preserved as they appear on the
manifestation
37. RDA Special Topic Series37
Manifestation Statement: Normalized
Transcription
Source:
Eoin McNamee
City of time
Illustrated by Jon Goodell
Wendy Lamb Books
Transcription:
Normalized transcription:
capitalization, punctuation, numerals
and diacritics are transcribed
following RDA guidelines
39. RDA Special Topic Series39
Elements for Recording Manifestation Statements
manifestation copyright statement
manifestation designation of sequence statement
manifestation dissertation statement
manifestation distribution statement
manifestation edition statement
manifestation frequency statement
manifestation identifier statement
manifestation manufacture statement
manifestation production statement
manifestation publication statement
manifestation regional encoding statement
manifestation series statement
manifestation title and responsibility statement
40. RDA Special Topic Series40
Elements for Recording Structured Statements
Manifestation> copyright statement
Manifestation> designation of sequence statement
Manifestation> distribution statement
Manifestation> edition statement
Manifestation> identifier for manifestation
Manifestation> manufacture statement
Manifestation> production statement
Manifestation> publication statement
Manifestation> regional encoding
Manifestation> series statement
Manifestation> title proper, other title information,
statement of responsibility relating to title proper
41. RDA Special Topic Series July 16, 201941
What’s the Difference?
Manifestation statement elements are always
unstructured descriptions
Some of the other manifestation elements can be
expressed in more that one recording method
Example: Montreal in previous slide as place of publication
Montreal (unstructured description)
Montréal (Québec) (authorized access point, structured description)
7013051 (Identifier)
http://dbpedia.org/resource/Montreal (IRI)
42. RDA Special Topic Series July 16, 201942
Uses of Manifestation Statements
Quick way to make backlogged materials available:
Scan preferred source, OCR; accessible with keyword
searching
Most keyword algorithms ignore case and punctuation, so
choice of transcription will not affect retrieval.
Quick way to make digitized materials available
Description of rare materials—more closely matches
what’s on the item (using basic transcription)
The new RDA Toolkit element chapters will consistently present four different ways of capturing data, called “recording methods”. If you have been to previous RDA presentations about this topic in the past several years, you may know the earlier term we were using: the four-fold path.
Each chapter will indicate which methods are available for that element; for each method that is not valid, the phrase “This recording method is not applicable to this element” will appear. If more than one method is applicable, it will be up to cataloguer judgment and/or the policy of the cataloguing agency about which to use, and whether or not to use more than one method. For example, a cataloguer could both transcribe a publisher and also provide an access point for it.
Let’s look more closely at each of these methods.
Here’s a quick review of the different recording methods, and some examples of how Montréal could be represented using each of them.
Here we have a title page and a title proper transcription in the MARC 245 field. Notice the capitalization, which conforms to the guidelines in Appendix A. In English, this means capitalizing the first word of the title and then any proper nouns in the title. However, a cataloging agency may choose to follow the capitalization found on the resource or available from an electronic description, such as through ONIX data from publishers. The Library of Congress leaves this up to cataloger’s judgment – what is the easiest to do.
Here we have a title page and a title proper transcription in the MARC 245 field. Notice the capitalization, which conforms to the guidelines in Appendix A. In English, this means capitalizing the first word of the title and then any proper nouns in the title. However, a cataloging agency may choose to follow the capitalization found on the resource or available from an electronic description, such as through ONIX data from publishers. The Library of Congress leaves this up to cataloger’s judgment – what is the easiest to do.
Here we have a title page and a title proper transcription in the MARC 245 field. Notice the capitalization, which conforms to the guidelines in Appendix A. In English, this means capitalizing the first word of the title and then any proper nouns in the title. However, a cataloging agency may choose to follow the capitalization found on the resource or available from an electronic description, such as through ONIX data from publishers. The Library of Congress leaves this up to cataloger’s judgment – what is the easiest to do.