Jenn Riley gave a presentation on FRBR (Functional Requirements for Bibliographic Records) at the 2006 Indiana Library Federation Annual Conference. She introduced the core concepts of FRBR, including entities, attributes, relationships, and user tasks. She discussed the FRBR group 1, 2, and 3 entities and how they are related. Riley also covered the Library of Congress' proposals to fit FRBR into existing MARC record structures and why libraries should care about FRBR, such as to improve user search and discovery experiences. She concluded by mentioning some existing FRBR implementations and encouraging attendees to learn more about FRBR.
This document provides an overview of FRBR (Functional Requirements for Bibliographic Records), including:
1. FRBR defines user tasks like finding and identifying bibliographic entities and provides a conceptual model of works, expressions, manifestations and items.
2. It describes attributes and relationships between these entities using the example of Newton's Principia.
3. FRBR is influential in cataloguing standards like RDA and the design of library discovery systems but has limitations around implementation and fitting non-text works.
This document discusses FRBR (Functional Requirements for Bibliographic Records) and how it relates to RDA (Resource Description and Access). It begins by outlining the goals of understanding the FRBR model of relationships between bibliographic entities and how RDA uses FRBR as the basis for new cataloging rules. It then explains the FRBR model which organizes creative works, expressions, manifestations and items into groups and describes their relationships. It contrasts FRBR with traditional cataloging models and discusses how RDA updates some AACR2 rules to better align with FRBR.
FRBR, FRAD and RDA I don't speak cataloging why should I careDeann Trebbe
This document discusses FRBR, FRAD, and RDA. It begins with an overview of the acronyms: FRBR is the Functional Requirements for Bibliographic Records, a conceptual model; FRAD is the Functional Requirements for Authority Data, also a conceptual model; and RDA is Resource Description and Access. It then provides more details on FRBR and FRAD, including their purposes and entities. FRBR is based on user tasks of finding, identifying, selecting, and acquiring resources. FRAD similarly maps authority data to user tasks. The document concludes that FRBR and FRAD encourage new ways of looking at bibliographic and authority data, and that like libraries, they continue to evolve.
RDA and FRBR aim to modernize cataloging practices by moving away from MARC and AACR2 towards a more flexible model based on user tasks. RDA splits the general material designation field into separate fields for content, media, and carrier types. It also requires transcribing entire statements of responsibility and added entries for all contributors. While intended to simplify practices, RDA's development faced political challenges. Its impact remains uncertain as catalogers and systems adapt to the new model.
The document provides an introduction and schedule for a training session on RDA, the new cataloging code. It discusses the background and history of RDA, including how it is based on FRBR and FRAD models and is designed to be used online. The schedule outlines topics to be covered such as differences from AACR2, examples, and a demonstration of the RDA Toolkit.
This document provides an overview of FRBR (Functional Requirements for Bibliographic Records), including:
1. FRBR defines user tasks like finding and identifying bibliographic entities and provides a conceptual model of works, expressions, manifestations and items.
2. It describes attributes and relationships between these entities using the example of Newton's Principia.
3. FRBR is influential in cataloguing standards like RDA and the design of library discovery systems but has limitations around implementation and fitting non-text works.
This document discusses FRBR (Functional Requirements for Bibliographic Records) and how it relates to RDA (Resource Description and Access). It begins by outlining the goals of understanding the FRBR model of relationships between bibliographic entities and how RDA uses FRBR as the basis for new cataloging rules. It then explains the FRBR model which organizes creative works, expressions, manifestations and items into groups and describes their relationships. It contrasts FRBR with traditional cataloging models and discusses how RDA updates some AACR2 rules to better align with FRBR.
FRBR, FRAD and RDA I don't speak cataloging why should I careDeann Trebbe
This document discusses FRBR, FRAD, and RDA. It begins with an overview of the acronyms: FRBR is the Functional Requirements for Bibliographic Records, a conceptual model; FRAD is the Functional Requirements for Authority Data, also a conceptual model; and RDA is Resource Description and Access. It then provides more details on FRBR and FRAD, including their purposes and entities. FRBR is based on user tasks of finding, identifying, selecting, and acquiring resources. FRAD similarly maps authority data to user tasks. The document concludes that FRBR and FRAD encourage new ways of looking at bibliographic and authority data, and that like libraries, they continue to evolve.
RDA and FRBR aim to modernize cataloging practices by moving away from MARC and AACR2 towards a more flexible model based on user tasks. RDA splits the general material designation field into separate fields for content, media, and carrier types. It also requires transcribing entire statements of responsibility and added entries for all contributors. While intended to simplify practices, RDA's development faced political challenges. Its impact remains uncertain as catalogers and systems adapt to the new model.
The document provides an introduction and schedule for a training session on RDA, the new cataloging code. It discusses the background and history of RDA, including how it is based on FRBR and FRAD models and is designed to be used online. The schedule outlines topics to be covered such as differences from AACR2, examples, and a demonstration of the RDA Toolkit.
FRBR stands for Functional Requirements for Bibliographic Records.
Functional Requirements for Bibliographic Records is a conceptual entity-relationship model developed by the International Federation of Library Associations and Institutions (IFLA).
A conceptual entity relationship model that relates user tasks of retrieval and access in online library catalogs and bibliographic databases from a user’s perspective.
A new conceptual model for bibliographic universe with a strong users focus .
The purpose of this entity relationship analysis was to discover the logical nature of bibliographic data in terms of entity, attributes and relationship.
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.
This document summarizes a presentation on the Functional Requirements for Bibliographic Records (FRBR). It introduces FRBR as a conceptual model developed by IFLA to define the functional requirements of bibliographic records based on user tasks and needs. The presentation covers the basic concepts in FRBR including entities, attributes, relationships, and the three main groups of entities. It also discusses the needs FRBR addresses, benefits it provides, and its role as the foundation for the new cataloging code RDA. The overall purpose of FRBR is to improve the user experience in bibliographic databases and catalogs.
This document summarizes a presentation on RDA (Resource Description and Access) and FRBR (Functional Requirements for Bibliographic Records). RDA is a new cataloging code being developed to replace AACR2. It is based on FRBR and FRAD models which conceptualize bibliographic entities and relationships. The presentation outlines the goals and major changes in RDA, including a principle-based approach, greater authority control focus, and online availability. Implementation plans target late 2009, though concerns remain about backwards compatibility and FRBR integration.
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.
The document discusses the Functional Requirements for Bibliographic Records (FRBR), a conceptual model that relates user tasks in library catalogs and databases. It describes FRBR's three groups of entities - works, expressions, manifestations, and items in Group 1; persons, corporate bodies in Group 2; and subjects in Group 3. FRBR aims to better represent relationships between these entities and the user tasks of finding, identifying, selecting, and obtaining resources. The document outlines how FRBR differs from traditional cataloging and has influenced the new cataloging standard RDA and next-generation library systems.
The document discusses Resource Description and Access (RDA), a new cataloging standard intended to replace Anglo-American Cataloguing Rules (AACR). It examines RDA's goals of being less Anglo-centric, enabling data sharing, and solving problems like multiple versions, but notes concerns that RDA was not adequately tested and may not be compatible with existing metadata standards and library systems. It predicts RDA will not be widely adopted and AACR2 will continue to be used.
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
FRBR (Functional Requirements for Bibliographic Records) is a 1998 recommendation of the International Federation of Library Associations and Institutions (IFLA) to restructure catalog databases to reflect the conceptual structure of information resources
This document provides an overview of a two-day training course on RDA for original catalogers. Day one will cover the background and history of RDA, FRBR concepts, authority records, and cataloging monographic materials using RDA. Day two will cover cataloging serials, audiovisual materials, online resources, and provider-neutral records using RDA, as well as relationships. The document outlines the course, provides context on the development and testing of RDA, and previews some of the key changes and concepts in RDA compared to AACR2.
The course will examine the conceptual foundations and structure of RDA, which represents a major change from previous cataloging rules. Students will critically analyze recent journal articles on RDA and lead discussions to evaluate its impact and implementation. The goal is for students to gain a thorough understanding of RDA to improve information organization and access. Assessment will include presentations, class participation, and a research paper.
Slides prepared for a guest appearance at Jane Greenberg's metadata class at the University of North Carolina, Chapel Hill. Delivered Monday, Dec. 6, 2010.
The RDA Vocabularies: What They Are, How They WorkDiane Hillmann
The document discusses RDA vocabularies and their structure when represented in RDF. It explains that RDA properties are declared as a generalized vocabulary without explicit relationships to FRBR entities, and subproperties can then be explicitly related to FRBR entities. This allows the vocabularies to be used more broadly by both library and non-library implementers. It also discusses how aggregated RDA statements like publication statements are represented, either through pre-coordinated subproperties or by using RDA syntax encoding schemes. The generalized approach makes the vocabularies more flexible and extensible.
Diane Hillmann: RDA Vocabularies in the Semantic WebALATechSource
The document discusses the RDA vocabularies, including a brief history of their development. It provides an overview of the structure of the vocabularies, explaining how RDA properties are defined both with and without relationships to FRBR entities. This allows the properties to be used more broadly by both library and non-library implementers. The document also discusses how RDA properties and statements can be represented in RDF using a generalized approach.
Library Catalogues: from Traditional to Next-GenerationKC Tan
Presented at Lecture on 13 Sep 2007 for CS3255 Information Organization for 3rd Year IS students of the School of Computing, National University of Singapore
The document provides guidance on finding information for a film studies course, including an overview of subject guides, books, periodical articles, databases, and citation management tools. It outlines strategies for searching the library catalog and databases to find materials on cultural influences on Akira Kurosawa's films. Examples are given of subject headings, reference sources, and databases for film studies research.
This is intended to be a two day workshop on RDA. This workshop will explore RDA with a specific focus on theories, practicalities, authority work and hands on cataloging. The workshop will take the student through understanding the theories behind RDA and then cataloging by RDA standards.
NISO Webinar:
Experimenting with BIBFRAME: Reports from Early Adopters
About the Webinar
In May 2011, the Library of Congress officially launched a new modeling initiative, Bibliographic Framework Initiative, as a linked data alternative to MARC. The Library then announced in November 2012 the proposed model, called BIBFRAME. Since then, the library world is moving from mainly theorizing about the BIBFRAME model to attempts to implement practical experimentation and testing. This experimentation is iterative, and continues to shape the model so that it’s stable enough and broadly acceptable enough for adoption.
In this webinar, several institutions will share their progress in experimenting with BIBFRAME within their library system. They will discuss the existing, developing, and planned projects happening at their institutions. Challenges and opportunities in exploring and implementing BIBFRAME in their institutions will be discussed as well.
Agenda
Introduction
Todd Carpenter, Executive Director, NISO
Experimental Mode: The National Library of Medicine and experiences with BIBFRAME
Nancy Fallgren, Metadata Specialist Librarian, National Library of Medicine, National Institutes of Health, US Department of Health and Human Services (DHHS)
Exploring BIBFRAME at a Small Academic Library
Jeremy Nelson, Metadata and Systems Librarian, Colorado College
Working with BIBFRAME for discovery and production: Linked data for Libraries/Linked Data for Production
Nancy Lorimer, Head, Metadata Dept, Stanford University Libraries
The document discusses metadata, including how it is used in cultural heritage organizations and the different types of metadata. It talks about how metadata is stored and shared using databases, XML, and RDF. The presentation notes that metadata standards are evolving due to linked data technologies, which are connecting metadata in larger graphs. As a result, metadata is becoming less separated between organizations and more open and intelligent systems are needed to handle the growing scale and connections in metadata. Cultural heritage organizations need to rethink their workflows and business models in light of these changes.
FRBR stands for Functional Requirements for Bibliographic Records.
Functional Requirements for Bibliographic Records is a conceptual entity-relationship model developed by the International Federation of Library Associations and Institutions (IFLA).
A conceptual entity relationship model that relates user tasks of retrieval and access in online library catalogs and bibliographic databases from a user’s perspective.
A new conceptual model for bibliographic universe with a strong users focus .
The purpose of this entity relationship analysis was to discover the logical nature of bibliographic data in terms of entity, attributes and relationship.
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.
This document summarizes a presentation on the Functional Requirements for Bibliographic Records (FRBR). It introduces FRBR as a conceptual model developed by IFLA to define the functional requirements of bibliographic records based on user tasks and needs. The presentation covers the basic concepts in FRBR including entities, attributes, relationships, and the three main groups of entities. It also discusses the needs FRBR addresses, benefits it provides, and its role as the foundation for the new cataloging code RDA. The overall purpose of FRBR is to improve the user experience in bibliographic databases and catalogs.
This document summarizes a presentation on RDA (Resource Description and Access) and FRBR (Functional Requirements for Bibliographic Records). RDA is a new cataloging code being developed to replace AACR2. It is based on FRBR and FRAD models which conceptualize bibliographic entities and relationships. The presentation outlines the goals and major changes in RDA, including a principle-based approach, greater authority control focus, and online availability. Implementation plans target late 2009, though concerns remain about backwards compatibility and FRBR integration.
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.
The document discusses the Functional Requirements for Bibliographic Records (FRBR), a conceptual model that relates user tasks in library catalogs and databases. It describes FRBR's three groups of entities - works, expressions, manifestations, and items in Group 1; persons, corporate bodies in Group 2; and subjects in Group 3. FRBR aims to better represent relationships between these entities and the user tasks of finding, identifying, selecting, and obtaining resources. The document outlines how FRBR differs from traditional cataloging and has influenced the new cataloging standard RDA and next-generation library systems.
The document discusses Resource Description and Access (RDA), a new cataloging standard intended to replace Anglo-American Cataloguing Rules (AACR). It examines RDA's goals of being less Anglo-centric, enabling data sharing, and solving problems like multiple versions, but notes concerns that RDA was not adequately tested and may not be compatible with existing metadata standards and library systems. It predicts RDA will not be widely adopted and AACR2 will continue to be used.
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
FRBR (Functional Requirements for Bibliographic Records) is a 1998 recommendation of the International Federation of Library Associations and Institutions (IFLA) to restructure catalog databases to reflect the conceptual structure of information resources
This document provides an overview of a two-day training course on RDA for original catalogers. Day one will cover the background and history of RDA, FRBR concepts, authority records, and cataloging monographic materials using RDA. Day two will cover cataloging serials, audiovisual materials, online resources, and provider-neutral records using RDA, as well as relationships. The document outlines the course, provides context on the development and testing of RDA, and previews some of the key changes and concepts in RDA compared to AACR2.
The course will examine the conceptual foundations and structure of RDA, which represents a major change from previous cataloging rules. Students will critically analyze recent journal articles on RDA and lead discussions to evaluate its impact and implementation. The goal is for students to gain a thorough understanding of RDA to improve information organization and access. Assessment will include presentations, class participation, and a research paper.
Slides prepared for a guest appearance at Jane Greenberg's metadata class at the University of North Carolina, Chapel Hill. Delivered Monday, Dec. 6, 2010.
The RDA Vocabularies: What They Are, How They WorkDiane Hillmann
The document discusses RDA vocabularies and their structure when represented in RDF. It explains that RDA properties are declared as a generalized vocabulary without explicit relationships to FRBR entities, and subproperties can then be explicitly related to FRBR entities. This allows the vocabularies to be used more broadly by both library and non-library implementers. It also discusses how aggregated RDA statements like publication statements are represented, either through pre-coordinated subproperties or by using RDA syntax encoding schemes. The generalized approach makes the vocabularies more flexible and extensible.
Diane Hillmann: RDA Vocabularies in the Semantic WebALATechSource
The document discusses the RDA vocabularies, including a brief history of their development. It provides an overview of the structure of the vocabularies, explaining how RDA properties are defined both with and without relationships to FRBR entities. This allows the properties to be used more broadly by both library and non-library implementers. The document also discusses how RDA properties and statements can be represented in RDF using a generalized approach.
Library Catalogues: from Traditional to Next-GenerationKC Tan
Presented at Lecture on 13 Sep 2007 for CS3255 Information Organization for 3rd Year IS students of the School of Computing, National University of Singapore
The document provides guidance on finding information for a film studies course, including an overview of subject guides, books, periodical articles, databases, and citation management tools. It outlines strategies for searching the library catalog and databases to find materials on cultural influences on Akira Kurosawa's films. Examples are given of subject headings, reference sources, and databases for film studies research.
This is intended to be a two day workshop on RDA. This workshop will explore RDA with a specific focus on theories, practicalities, authority work and hands on cataloging. The workshop will take the student through understanding the theories behind RDA and then cataloging by RDA standards.
NISO Webinar:
Experimenting with BIBFRAME: Reports from Early Adopters
About the Webinar
In May 2011, the Library of Congress officially launched a new modeling initiative, Bibliographic Framework Initiative, as a linked data alternative to MARC. The Library then announced in November 2012 the proposed model, called BIBFRAME. Since then, the library world is moving from mainly theorizing about the BIBFRAME model to attempts to implement practical experimentation and testing. This experimentation is iterative, and continues to shape the model so that it’s stable enough and broadly acceptable enough for adoption.
In this webinar, several institutions will share their progress in experimenting with BIBFRAME within their library system. They will discuss the existing, developing, and planned projects happening at their institutions. Challenges and opportunities in exploring and implementing BIBFRAME in their institutions will be discussed as well.
Agenda
Introduction
Todd Carpenter, Executive Director, NISO
Experimental Mode: The National Library of Medicine and experiences with BIBFRAME
Nancy Fallgren, Metadata Specialist Librarian, National Library of Medicine, National Institutes of Health, US Department of Health and Human Services (DHHS)
Exploring BIBFRAME at a Small Academic Library
Jeremy Nelson, Metadata and Systems Librarian, Colorado College
Working with BIBFRAME for discovery and production: Linked data for Libraries/Linked Data for Production
Nancy Lorimer, Head, Metadata Dept, Stanford University Libraries
Similar to De-Mystifying FRBR: A Whirlwind Introduction (20)
The document discusses metadata, including how it is used in cultural heritage organizations and the different types of metadata. It talks about how metadata is stored and shared using databases, XML, and RDF. The presentation notes that metadata standards are evolving due to linked data technologies, which are connecting metadata in larger graphs. As a result, metadata is becoming less separated between organizations and more open and intelligent systems are needed to handle the growing scale and connections in metadata. Cultural heritage organizations need to rethink their workflows and business models in light of these changes.
Designing the Garden: Getting Grounded in Linked DataJenn Riley
Riley, Jenn. “Designing the Garden: Getting Grounded in Linked Data.” Beyond the Looking Glass: Real World Linked Data. What Does it Take to Make it Work? ALCTS Preconference, San Francisco, CA, June 26, 2015.
Riley, Jenn. “Launching metaware.buzz.” Panelist, Experimental Scholarly Publishing: Building New Models with Distributed Communities of Practice”, Digital Library Federation Forum, October 28, 2014, Atlanta, GA.
Riley, Jenn. “Getting Comfortable with Metadata Reuse.” O Rare! Performance in Special Collections: The 54th Annual RBMS Preconference, Minneapolis, June 23 – 26, 2013
Handout for Digital Imaging of PhotographsJenn Riley
This document provides guidelines for digitizing sheet music collections at the Lilly Library, including specifications for file formats, resolution, naming conventions, and scanning procedures. Key steps include wearing gloves, handling pages carefully, scanning pages sequentially in color or grayscale as needed, using consistent pixel dimensions within each item, and recording metadata in a scan log spreadsheet. The goal is to digitally capture all relevant content like illustrations, advertisements, and annotations, while preserving the original order and organization of the physical materials.
The Open Archives Initiative and the Sheet Music ConsortiumJenn Riley
Dunn, Jon and Jenn Riley. “The Open Archives Initiative and the Sheet Music Consortium.” Digital Library Program Brown Bag Presentation, October 10, 2003.
Cushman Exposed! Exploiting Controlled Vocabularies to Enhance Browsing and S...Jenn Riley
Dalmau, Michelle and Jenn Riley. "Cushman Exposed! Exploiting Controlled Vocabularies to Enhance Browsing and Searching of an Online Photograph Collection." Digital Library Program Brown Bag Presentation, May 17, 2004.
The document summarizes the Variations2 project, which is building on an earlier Variations project funded by the National Science Foundation. Variations2 aims to create an integrated digital library of musical works, scores, and recordings. It is staffed by several librarians and supported by various Indiana University departments. The project involves developing a data model and software framework to provide search and retrieval of diverse music formats. Usability research is also being conducted to improve the user experience.
Handout for Merging Metadata from Multiple Traditions: IN Harmony Sheet Music...Jenn Riley
Riley, Jenn. "Merging Metadata from Multiple Traditions: IN Harmony Sheet Music from Libraries and Museums." Digital Library Program Brown Bag Presentation, October 19, 2005.
Merging Metadata from Multiple Traditions: IN Harmony Sheet Music from Librar...Jenn Riley
Riley, Jenn. "Merging Metadata from Multiple Traditions: IN Harmony Sheet Music from Libraries and Museums." Digital Library Program Brown Bag Presentation, October 19, 2005.
Challenges in the Nursery: Linking a Finding Aid with Online ContentJenn Riley
Johnson, Elizabeth, and Jenn Riley. "Challenges in the Nursery: Linking a Finding Aid with Online Content." Digital Library Program Brown Bag Presentation, March 8, 2006.
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar Kanvaria
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
Thinking of getting a dog? Be aware that breeds like Pit Bulls, Rottweilers, and German Shepherds can be loyal and dangerous. Proper training and socialization are crucial to preventing aggressive behaviors. Ensure safety by understanding their needs and always supervising interactions. Stay safe, and enjoy your furry friends!
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
How to Fix the Import Error in the Odoo 17Celine George
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
Executive Directors Chat Leveraging AI for Diversity, Equity, and InclusionTechSoup
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
1. De-Mystifying FRBR: A
Whirlwind Introduction
Jenn Riley
Metadata Librarian
IU Digital Library Program
jenlrile@indiana.edu
4/13/2006
Indiana Library Federation Annual Conference
1
2. Agenda
Introduction to FRBR
LC proposals for fitting FRBR into existing
record structures
Why you should care
4/13/2006
Indiana Library Federation Annual2
Conference
3. Agenda
Introduction to FRBR
LC proposals for fitting FRBR into existing
record structures
Why you should care
4/13/2006
Indiana Library Federation Annual3
Conference
4. What is FRBR?
Functional Requirements for Bibliographic
Records
Either F-R-B-R or “Ferber”
Outlined in a 1997/1998 report from IFLA
A “conceptual model”
entities
attributes
relationships
4/13/2006
Indiana Library Federation Annual4
Conference
5. Contents of FRBR Report
Introduction
Objectives, Scope, and Methodology
Entities
Attributes
Relationships
User Tasks
Basic Requirements for National
Bibliographic Records
4/13/2006
Indiana Library Federation Annual5
Conference
6. User Tasks
FRBR
Find
Identify
Select
Obtain
Cutter
To enable a person to find a book of
which either
...is known
To show what the library has
by a given author
on a given subject
in a given kind of literature
To assist in the choice of a book
4/13/2006
the author
the title
the subject
as to its edition (bibliographically)
as to its character (literary or topical)
Indiana Library Federation Annual6
Conference
7. Group 1 Entities
WORK
“a distinct intellectual an expression of a work”
“the physical embodiment of or artistic creation”
“a single exemplar of a manifestation”
“the intellectual or artistic realization of a work”
is realized through
EXPRESSION
is embodied in
w1 Franz Schubert's Trout quintet
w1 Harry Lindgren's Geometric dissections
w1 Ronald Hayman's Playback
-e1 the composer's score
-e1 the author's text Geometric
-e1 original text entitlededited for
-e2 a performance by the Amadeus
dissections
publication Hephzibah Menuhin on
Quartet and
-m1 the book published in 1973 by
piano -m1 the book published in 1964by Van
Davis-Poynter
-e3 Nostrand
a performance by the Cleveland
-e2 revised Yo-Yo Ma onRecreational
Quartet and copy autographed by the
-i1 text entitled the cello
problems in geometric dissections ....
-. . .author
.
-m1 the book published in 1972 by
Dover
4/13/2006
MANIFESTATION
is exemplified by
ITEM
Indiana Library Federation Annual7
Conference
8. Not always clear where a real-world
situation falls
New preface
New illustrations
Braille
Screenplay
Serials
Aggregations
4/13/2006
Indiana Library Federation Annual8
Conference
9. Expression entity uncertainty
FRBR report, p. 19:
“Strictly speaking, any change in intellectual or artistic
content constitutes a change in expression. Thus, if a text
is revised or modified, the resulting expression is
considered to be a new expression, no matter how minor
the modification may be.”
“On a practical level, the degree to which bibliographic
distinctions are made between variant expressions of a
work will depend to some extent on the nature of the work
itself, and on the anticipated needs of users.”
Expression entity working group now formed
4/13/2006
Indiana Library Federation Annual9
Conference
10. Group 2 Entities
“…responsible for the intellectual or artistic
content, the physical production and
dissemination, or the custodianship of the
entities…” in Group 1
Person
Corporate body
[Family]
4/13/2006
Indiana Library Federation Annual10
Conference
11. Group 3 Entities
Subjects of Works
Groups 1 & 2 entities
Concept
Object
Event
Place
4/13/2006
Indiana Library Federation Annual11
Conference
12. FRANAR
Functional Requirements and Numbering of
Authority Records IFLA Working Group
Released FRAR report in 2005
Companion document to FRBR
Discusses cataloging process more than
entity-relationship analysis
4/13/2006
Indiana Library Federation Annual12
Conference
13. Agenda
Introduction to FRBR
LC proposals for fitting FRBR into existing
record structures
Why you should care
4/13/2006
Indiana Library Federation Annual13
Conference
14. Possible FRBR applications
Scenario A - Now
Authority
Work/
Expression
Uniform
Title
Bibliographic
Holding
Person
Series
(work/expression)
Uniform
Title
Concept
Manifestation
Item
19. New record structures
No decisions made yet about the best way to
proceed within MARC
Any changes will be phased in over time
Any changes will represent steep challenges
both to ILS vendors and to implementing
libraries
Any changes will be made with user
functionality as a prime consideration
4/13/2006
Indiana Library Federation Annual19
Conference
20. Agenda
Introduction to FRBR
LC proposals for fitting FRBR into existing
record structures
Why you should care
4/13/2006
Indiana Library Federation Annual20
Conference
21. How many records are affected?
Average work has 1.5 manifestations
78% of works have a single manifestation
~99% of all works in WorldCat have seven
manifestations or less
~30,000, or ~1% have more than 20 manifestations
R. Bennett et. al. (2003) "The concept of a work in WorldCat: an application of FRBR" Library
Collections Acquisitions & Technical Services 27, 45-59.
So why do we need FRBR?
4/13/2006
Indiana Library Federation Annual21
Conference
23. End-users
Grouping and disambiguation of search
results [example]
Better distinction between versions
Better support for browsing, discovery of
previously unknown items
ILL
Holds
4/13/2006
Indiana Library Federation Annual23
Conference
24. RDA & FRBR
“The FRBR and FRAR models provide RDA
with an underlying framework that has the
scope needed to support comprehensive
coverage of all types of content and media,
the flexibility and extensibility needed to
accommodate newly emerging resource
characteristics, and the adaptability needed
for the data produced to function within a
wide range of technological environments.”
4/13/2006
Indiana Library Federation Annual24
Conference
25. Other cataloging changes
Non-MARC environments
Many already doing FRBR-like things
Tend to have lots of programming support
MARC environments
Need more innovation from ILS vendors
Catalogers used to looking at 1 record (well, 2
records) showing everything
Need to provide complex relationships when
necessary, hide when not
Supporting legacy records will be complicated
4/13/2006
Indiana Library Federation Annual25
Conference
26. Perspectives from the 2005 ALCTS
FRBR ALA Preconference
Glenn Patton (OCLC)
Clearer understanding of why we do what we do
Better collocation and navigation
Clearer, more useful relationships
More controlled, authoritative information for
productivity
Jennifer Bowen (Rochester): “Is FRBR really
coming? It’s already here!”
4/13/2006
Indiana Library Federation Annual26
Conference
27. Some implementations & related
projects
OCLC FictionFinder and Curioser
RLG RedLightGreen
AustLit Gateway
VTLS Virtua ILS system
III Millennium 2005 ILS system
IU Variations2
4/13/2006
Indiana Library Federation Annual27
Conference
28. So what do I do now?
Learn more!
4/13/2006
Indiana Library Federation Annual28
Conference
29. For further information
FRBR report
Readings on handout
FRBR listserv
FRBR blog
jenlrile@indiana.edu
These presentation materials:
<http://www.dlib.indiana.edu/~jenlrile/presentations/ilf2006/>
4/13/2006
Indiana Library Federation Annual29
Conference
Editor's Notes
<number>
When we catalog, we start with an item we have at hand. From it we construct a bibliographic record that is intended to describe the manifestation, that is any copy held anywhere, so the record can be re-used by others in a shared cataloging environment.
We also make authority records to control the way we identify works and expressions that are embodied in the manifestation we are describing, and that in turn may be linked to a name authority record for the person or corporate body that is responsible for creating the work or expression. In some integrated library systems this link between the bib and authority records is real, which also makes database maintenance and global update changes easier than when these links are not present.
<number>
Here’s a scenario for the future, where we would make use of authority records for works and expressions and do more linking directly at the authority record level for the classification and subject headings that are appropriate to the work. Those authority records would also be available to display for each linked bib record, and we could save cataloger’s time by not needing to classify and provide subject headings for all the manifestations of that same work/expression combination.
For the location, call number for the items, We’d still need to cutter for the individual item or copy we were adding, but that would be a lot simpler than all the other subject cataloging work that is now done. The item information for inventory control, circulation, interlibrary loan, etc. would be entered as part of the holdings record and would reflect the call number for the copy held locally.
I really like this model, but we need to experiment to see if this is best or perhaps there is a better implementation model for FRBR. This model will require some changes to the authority record – to include 65X’s for the subject headings – we already have a field for classification.
<number>
Here’s another scenario, where we could use the bib records for works and expressions, link the subjects or even use the 650’s in bib records as we can now, but somehow get our local systems to use the linked work/expression records as part of the displays when we view the manifestation records… This model, in my view is not really ideal… It would take a lot of work on the part of vendors to know how to display the linked work/expression records with the related bib records.
<number>
Here’s yet another scenario for the future, where we would use the MARC holdings record to capture all of the data elements (attributes) of the manifestation and items – that is, the physical characteristics – the physical media, publisher, distributor, manufacturer information relevant to the recording of the content.
Attaching holdings records to authority records should not be a giant programming job, but many current integrated library systems avoid authority records altogether, which is a pity. The potential in the future for using the authority record and its ability to cluster the variant names given to things and to link to specific resources, opens up tremendous flexibility to meet future user demands. This might be particularly interesting for serials. The title of a serial is a controlled access point. Logically that would be in an authority record.
But there is also the manifestation aspect of the physical format of any given serial and various attributes associated with the manifestation – its publisher, its numbering and dates, its physical medium (microform, digital online or a tangible digital object like a CD-ROM) and mode of issuance (e.g., successively issued or integrating resource) – we now put the manifestation information in bibliographic records
And the item information may be in both bibliographic records or holdings in the MARC format and item records in local systems.
If we had a clear way of identifying the attributes for a particular work/expression/ manifestation/item combination, we could theoretically combine all such combinations for the same work in a single record, and just display the needed elements as the application or user specified. There are many ways this could work.
<number>
Here’s yet another scenario – a variation from the last where we’d use the bib record again for the work/expression record…and the holdings record for manifestations and items…but this has the same drawbacks as Scenario C..
A lot of this depends on vendors to come up with system designs and for cataloging rules to be clear about needed entities and attributes and relationships – which brings us back to FRBR and cataloging rules.