Functional Requirements for Bibliographic Records explained

Functional Requirements for Bibliographic Records (FRBR) is a conceptual entity–relationship model developed by the International Federation of Library Associations and Institutions (IFLA) that relates user tasks of retrieval and access in online library catalogues and bibliographic databases from a user’s perspective. It represents a more holistic approach to retrieval and access as the relationships between the entities provide links to navigate through the hierarchy of relationships. The model is significant because it is separate from specific cataloguing standards such as Anglo-American Cataloguing Rules (AACR), Resource Description and Access (RDA) and International Standard Bibliographic Description (ISBD).

User tasks

The ways that people can use FRBR data have been defined as follows: to find entities in a search, to identify an entity as being the correct one, to select an entity that suits the user's needs, or to obtain an entity (physical access or licensing).[1]

FRBR comprises groups of entities:

Group 1 entities are the foundation of the FRBR model:

Group 1 entities are not strictly hierarchical, because entities do not always inherit properties from other entities.[3] Despite initial positive assessments of FRBR clarifying the thoughts around the conceptual underpinnings of works, there has been later disagreement about what the Group 1 entities actually mean.[4] The distinction between Works and Expressions is also unclear in many cases.

Relationships

In addition to the relationships between Group 1 and Groups 2 and 3 discussed above, there are many additional relationships covering such things as digitized editions of a work to the original text, and derivative works such as adaptations and parodies, or new texts which are critical evaluations of a pre-existing text.[5] FRBR is built upon relationships between and among entities. "Relationships serve as the vehicle for depicting the link between one entity and another, and thus as the means of assisting the user to ‘navigate’ the universe that is represented in a bibliography, catalogue, or bibliographic database."[6] Examples of relationship types include, but are not limited to:[7]

Equivalence relationships

Equivalence relationships exist between exact copies of the same manifestation of a work or between an original item and reproductions of it, so long as the intellectual content and authorship are preserved. Examples include reproductions such as copies, issues, facsimiles and reprints, photocopies, and microfilms.

Derivative relationships

Derivative relationships exist between a bibliographic work and a modification based on the work. Examples include:

Descriptive relationships

Descriptive relationships exist between a bibliographic entity and a description, criticism, evaluation, or review of that entity, such as between a work and a book review describing it. Descriptive relationships also includes annotated editions, casebooks, commentaries, and critiques of an existing work.

See also

Further reading

External links

Notes and References

  1. https://www.ifla.org/files/assets/cataloguing/frbr/frbr_2008.pdf p.79
  2. Web site: Functional Requirements for Bibliographic Records - Final Report - Part 1. ifla.org. 15 April 2014.
  3. Renear. Allen H.. Choi. Yunseon. Modeling Our Understanding, Understanding Our Models - The Case of Inheritance in FRBR. Proceedings of the American Society for Information Science and Technology. 10 October 2007. 43. 1. 1–16. 10.1002/meet.14504301179. free.
  4. Floyd. Ingbert. Multiple interpretations: Implications of FRBR as a boundary object. Proceedings of the American Society for Information Science and Technology. 2009. 46. 1. 1–8. 10.1002/meet.2009.14504603110. free.
  5. Web site: Tillett. Barbara. What is FRBR?. Library of Congress. 5 August 2017.
  6. Web site: Functional Requirements for Bibliographic Records - Final Report - Part 2. ifla.org. 15 April 2014.
  7. Web site: International Federation of Library Associations and Institutions. Functional Requirements for Bibliographic Records: Final Report. 3 December 2013.