AERI 2012Workshop Category: Curriculum

Development/Research Methodology

Metadata Models and Modelling MethodsEntity-Relationship Modelling Method:

“Bibliographic Universe”

Procedures: Points to Follow

Why to model?: argumentsDefine the “universum”: bibliographicDefine functions/required functionality: data

& user Define the model/modelling methodologyDefine entities-atributes-relationships [data]Define user tasks [user]So what?, or, Then what?

Why to model?: arguments

Change of technology: “external” forcesAutomated systems & large-scale databasesNeed to reduce cataloguing costs (re-use)Continued growth of publishing outputBroad range of user expectations and needs

“Internal” forcesTheoretical implications of the above“We are not alone!”

Or, in other words:Elaine Svenonius. The Intellectual Foundation of Infromation

Organization. Cambridge, Mass.; London: The MIT Press, 2000, p.51

The variables of interest in bibliographic theory will inevitably exhibit a certain amount of vagueness, ambiguity, and limited applicability. As long as the practice is affected by this only sporadically, there is no reason for concern. But if the numbers of bibliographic entities that can be described in a uniform and exact manner begin to get out of hand, then it is time to question traditional concepts and theories.

Define the “universum”: bibliographic

Toward IFLA FR-family of conceptual models1990 – Stockholm seminar1991-1998: FRBR – bibliographhic data1999-2009: FRAD – name authority data2005-2010: FRSAD – subject authority data

2011-[2013] – consolidated FR-conceptual model

Define functions/required functionality: data & user

Functional requirements for...a framework that identifies and clearly defines the

entities of interest to users of bibliographic records, the attributes of each entity, and the types of relationships that operate between entities

serve as the basis for relating specific attributes and relationships (reflected in the record as discrete data elements) to the various tasks that users perform when consulting bibliographic records.

Define the model/modeling methodology

Entity-Relationship

Object Oriented [CIDOC-CRM FRBRoo]Event oriented

Define entities-atributes-relationships

FRBR FRAD FRSAD

Work Work

Expression

Manifestation

Item

Person

Corporate Body Bibliographic Entities Thema

Family Names and/or Identifiers Nomen

Concept Controlled Acess Points

Object Rules

Event Agency

Place

Define user tasks

FRBR FRAD FRSAD

Find Find Find

Identify Identify Identify

Select Select

Obtain

Explore

Contextualize

Justify

FRBR: 6.1 Mapping Attributes and Relationships to User Tasks

FRSAD: 6.4 Mapping of Attributes, Relationships, and User Tasks

So what?, or, Then what?

Impact on other models: CIDOC/CRM – FRBRoo & Archival models(?)

Bibliographic standard: ISBDCataloguing rules: REICAT, RDAWebPACs: FRBRized cataloguesSemantic Web & Linked Data

Vocabulary [E – A – R] + definitions RDF (W3C) [generic, graph-based data model]

Authorized, trustworthy data [provenance]

Entity-Relationship Methodology

An entity analysis technique that is used in the development of conceptual models for relational database systems. Steps:

(1)isolate the key objects that are of interest to users of information in a particular domain; serve as the focal point for a cluster of data

(2) define the relationships that normally hold between one type of entity and another type of entity

(3) identify the important characteristics or attributes of each entity

The conventions for graphic presentation

FRBR: Bibliographic data - example