1. AERI 2012 Workshop Category: Curriculum Development/Research Methodology Metadata Models and Modelling Methods Entity-Relationship Modelling Method: “Bibliographic Universe”

2. Procedures: Points to Follow Why to model?: arguments Define the “universum”: bibliographic Define functions/required functionality: data & user Define the model/modelling methodology Define entities-atributes-relationships [data] Define user tasks [user] So what?, or, Then what?

3. Why to model?: arguments Change of technology: “external” forces Automated systems & large-scale databases Need to reduce cataloguing costs (re-use) Continued growth of publishing output Broad range of user expectations and needs “Internal” forces Theoretical implications of the above “We are not alone!”

4. 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.

5. Define the “universum”: bibliographic Toward IFLA FR-family of conceptual models 1990 – Stockholm seminar 1991-1998: FRBR – bibliographhic data 1999-2009: FRAD – name authority data 2005-2010: FRSAD – subject authority data 2011-[2013] – consolidated FR-conceptual model

6. 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.

7. Define the model/modeling methodology Entity-Relationship Object Oriented [CIDOC-CRM  FRBRoo] Event oriented

8. Define entities-atributes-relationships FRBRFRADFRSAD Work Expression Manifestation Item Person Corporate BodyBibliographic EntitiesThema FamilyNames and/or IdentifiersNomen ConceptControlled Acess Points ObjectRules EventAgency Place

9. Define user tasks FRBRFRADFRSAD Find Identify Select Obtain Explore Contextualize Justify

10. FRBR: 6.1 Mapping Attributes and Relationships to User Tasks

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

12. So what?, or, Then what? Impact on other models: CIDOC/CRM – FRBRoo & Archival models(?) Bibliographic standard: ISBD Cataloguing rules: REICAT, RDA WebPACs: FRBRized catalogues Semantic Web & Linked Data Vocabulary [E – A – R] + definitions  RDF (W3C) [generic, graph-based data model] Authorized, trustworthy data [provenance]

13. 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

14. The conventions for graphic presentation

15. FRBR: Bibliographic data - example