A Brief Presentation of PRESS OO For the CIDOC CRM SIG and FRBR/CRM Harmonisation WG 21 October 2013.

Slides:



Advertisements
Similar presentations
Modeling Continuing Resources in FRBR [and More] Judith A. Kuhagen CPSO, Library of Congress FRBR Workshop - OCLC May 2, 2005.
Advertisements

A centre of expertise in digital information management UKOLN is supported by: The Dublin Core Application Profile for Scholarly Works.
FRBR QUIZ Start quiz Take quiz by pointing to the answer and clicking on it.
F25 Performance Plan F1 Work F15 Complex Work F14 Individual Work F2 Expression F22 Self Contained Expression R1 is logical successor of (has successor)
8/3/20071 E65 Creation F30 Work Conception F1 Work F21 Complex Work Work F46 Individual Work R21 initiated (was initiated by) F2 Expression F20 Self Contained.
1 CIDOC CRM + FRBR ER = FRBR OO … an equation for a harmonised view of museum information and bibliographic information Martin Doerr First CASPAR Seminar.
ISO DSDL ISO – Document Schema Definition Languages (DSDL) Martin Bryan Convenor, JTC1/SC18 WG1.
Bibliographic Relationships and Bibliographic Families.
Session 6 Issues in Cataloging Loose-leaf Integrating Resources Original content by Rhonda K. Lawrence Head of Cataloging, UCLA Law Library.
MARC 21, FRBR, RDA Review terminology (especially for non-native English speakers) Conceptual models Elements Attributes Future: Probably not a bib record,
Chapter 7 Structuring System Process Requirements
RDA & Serials. RDA Toolkit CONSER RDA Cataloging Checklist for Textual Serials (DRAFT) CONSER RDA Core Elements Where’s that Tool? CONSER RDA Cataloging.
Resource Description and Access (RDA): a new standard for the digital world Ann Huthwaite Library Resource Services Manager, QUT.
Developing catalogues for customers (not cataloguers) Gordon Dunsire Presented at Branch/Group Day, CILIP in Scotland 5 th Annual Conference, 13 th June.
FRBR Functional requirements for bibliographic records (IFLA, 1998) Don Thornbury, RBSC Technical Services April 5, 2005.
FRBR: Functional Requirements for Bibliographic Records it is the Final Report of the IFLA Study Group on the Functional Requirements for Bibliographic.
Developing an Eye for Resemblances: FRBR and Relevancy Ranking in WorldCat Local Greg Matthews & Jon Scott WorldCat Discovery Day 30 July 2010.
RDA: A New Standard Supporting Resource Discovery Presentation given at the CLA conference session The Future of Resource Discovery: Promoting Resource.
Presented by IBM developer Works ibm.com/developerworks/ 2006 January – April © 2006 IBM Corporation. Making the most of Creating Eclipse plug-ins.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
1 CS 502: Computing Methods for Digital Libraries Lecture 17 Descriptive Metadata: Dublin Core.
© Copyright Eliyahu Brutman Programming Techniques Course.
IMT530- Organization of Information Resources1 Feedback Like exercises –But want more instructions and feedback on them –Wondering about grading on these.
CHAPTER 6 FILE PROCESSING. 2 Introduction  The most convenient way to process involving large data sets is to store them into a file for later processing.
RDA, FRBR & MARC RDA Cataloguing Seminars September 2012.
RDA AND AUTHORITY CONTROL Name: Hester Marais Job Title: Authority Describer Tel: Your institution's logo.
RDA for Print Materials 5 June 2013 Vicki Sipe. Resource Description and Access Timeline Tested and analyzed during Implemented March 31, 2013.
Tutorial 3: Adding and Formatting Text. 2 Objectives Session 3.1 Type text into a page Copy text from a document and paste it into a page Check for spelling.
October 23, Expanding the Serials Family Continuing resources in the library catalogue.
Chapter 7 Structuring System Process Requirements
Chapter 7: The Object-Oriented Approach to Requirements
Harmonising without Harm: towards an object-oriented formulation of FRBR aligned on the CIDOC CRM ontology Maja Žumer (University of Ljubljana) & Patrick.
RDA Training FRBR: a brief introduction British Library 2015 (2015 April RDA update)
1 Modelling Intellectual Processes: The object-orient FRBR Model Martin Doerr Center for Cultural Informatics Institute of Computer Science Foundation.
Chapter 7 Structuring System Process Requirements
Implementing a Serial Work in an Electronic Resources Management System NASIG 2004 Kristin Antelman.
Moving Cataloguing into the 21 st Century Presentation given at the CLA pre-conference Shaping Tomorrow’s Metadata with RDA June 2, 2010 by Tom Delsey.
Cataloguing Electronic resources Prepared by the Cataloguing Team at Charles Sturt University.
Conceptual models: museums & libraries towards an object-oriented formulation of FRBR aligned on the CIDOC CRM ontology The title of the present ELAG.
Jenn Riley Metadata Librarian IU Digital Library Program New Developments in Cataloging.
A CIDOC CRM – compatible metadata model for digital preservation
Presented by: CHAN LAI SAN ( ) REBAH DAW SARREB ( ) FIDA AL-OBAISI ( ) 08 April 2008 (Tuesday 6pm – 7:30pm)
CHAPTER TEN AUTHORING.
From AACR2 to RDA: An Evolution Kathy Glennan University of Maryland.
ELAG : Library Systems Seminar – 26 Roma – Biblioteca Nazionale Centrale, Aprile 2002 THE SEMANTIC WEB AND LIBRARIES.
ICS-FORTH March 14, Modelling Intellectual Processes: The object-orient FRBR Model Martin Doerr Paris, France March 14, 2006 Corrections made 9.
[insert WP name] Core concepts and elements [insert author name and photo if necessary]
RDA DAY 1 – part 2 web version 1. 2 When you catalog a “book” in hand: You are working with a FRBR Group 1 Item The bibliographic record you create will.
AACR2 versus RDA Presentation given at the CLA Pre-Conference Session From Rules to Entities: Cataloguing with RDA May 29, 2009 by Tom Delsey.
Introduction to Interactive Media Interactive Media Tools: Authoring Applications.
FRBR: Cataloging’s New Frontier Emily Dust Nimsakont Nebraska Library Commission NCompass Live December 15, 2010 Photo credit:
Functional Requirements for Bibliographic Records The Changing Face of Cataloging William E. Moen Texas Center for Digital Knowledge School of Library.
From FRBR to FRBR OO through CIDOC CRM… A Common Ontology for Cultural Heritage Information Patrick Le Bœuf, National Library of France International Symposium.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
LIS512 lecture 2: FRBR reading International Federation of Library Association “Fundamental Requirements for Bibliographic Records”, revised.
The Akoma Ntoso Naming Convention Fabio Vitali University of Bologna.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
F25 Performance Plan F1 Work F15 Complex Work F14 Individual Work F2 Expression F22 Self Contained Expression R1 is logical successor of (has successor)
ICS-FORTH September 10, Modelling Intellectual Processes: The object-orient FRBR Model Martin Doerr Gothenburg, Sweden September 12, 2006 Corrections.
OCR Nationals: Unit 22 – Creating Sound using ICT A02 – Design an audio clip Planning the clip.
RDA for Law Catalogers Serials and Integrating Resources Melissa Beck UCLA Law Library.
Harmonized EDM-CRM-FRBRoo
Modelling Intellectual Processes: The object-orient FRBR Model
From FRBR to FRBROO through CIDOC CRM…
Harmonized EDM-CRM-FRBRoo
FRBRoo and performing arts
Modelling Intellectual Processes: The object-orient FRBR Model
FRBR and FRAD as Implemented in RDA
Design Yaodong Bi.
Modelling Intellectual Processes: The object-orient FRBR Model
Presentation transcript:

A Brief Presentation of PRESS OO For the CIDOC CRM SIG and FRBR/CRM Harmonisation WG 21 October 2013

How FRBR envisioned serials (1) The serial as “a distinct intellectual or artistic creation” = a WORK Its various (local) editions = EXPRESSIONS Not flexible enough, when a (local) edition is split into or merged with other serials, when it creates its own various editions, when an autonomous serial is transformed into the (local) edition of a distinct serial, etc.

How FRBR envisioned serials (2) WORK –Intended termination MANIFESTATION –Publication status –Numbering EXPRESSION –Extensibility –Sequencing pattern –Expected regularity of issue –Expected frequency of issue … Results in highly fragmented descriptions

FRBR and serials: a criticism Steve Shadle, “FRBR and Serials”, The Serials Librarian, 2006, 50(1-2), –Each of Serial, Issue, and Article are Works, each with their own Expressions and Manifestations –A Serial Work serves to collocate Issue Works  That is exactly what FRBR OO and PRESS OO do

Serials in FRBR OO /PRESS OO (1) Each serial = a WORK (a conceptual framework) –including local (linguistic, etc.) editions EXPRESSION of a Serial Work = textual (musical, graphic, etc.) content of the sum of all published issues of the Serial Work (once “completed”) –PRESS OO does not deny its existence, but is not really concerned with it MANIFESTATION of a Serial Work does not “exist” until the Serial Work is “completed” –PRESS OO does not deny its existence, but is not really concerned with it  PRESS OO actually focuses on one class only (from FRBR Group 1): F18 Serial Work

Serials in FRBR OO /PRESS OO (2) Describing a serial amounts to describing the predictability of its behavior, i.e., its publication plan (a set of issuing rules) –What features of the current issue can be expected to remain identical in the next one? –Which past issues displayed identical features and when, and what were those features?  PRESS OO actually focuses on class: Z12 Issuing Rule

Colour codes PRESS OO = extension of FRBR OO = extension of CIDOC CRM  In the following slides: F… R…, CLP… or CLR… E… P… Y… Z… = a class from CIDOC CRM = a property from CIDOC CRM = a class from FRBR OO = a property from FRBR OO = a class from PRESS OO = a property from PRESS OO

F3 Manifestation Product Type F5 Item F24 Publication Expression F18 Serial Work F19 Publication Work F24 Publication Expression F3 Manifestation Product Type F5 Item F22 Self-Contained Expression F1 Work Z9 Storage Unit PeriodicalIssueArticle R3 is realised in R10 has member R3 is realised in CLR6 should carry R7 is example of R6 carries CLP46 should be composed of CLR6 should carry R7 is example of R6 carries R14 incorporates R5 has component P46 is composed of Complete set of copies of issues Storage unit gathering copies of several issues Physical copy of one individual issue An individual issue (publisher’s input) Content of the complete set of issues An article (author’s input) Text of an article Concept of a periodical Physical features supposed to be shared by all copies of all issues F17 Aggregation Work F22 Self-Contained Expression An individual issue (editor’s input) R3 is realised in R14 incorporates Overview (dead)

Chronological boundaries F18 Serial Work F30 Publication Event R23 created a realisation of Z6 Starting of Publication Z7 Ending of Publication = Publication of earliest known issue= Publication of latest known issue P116 starts P115 finishes Y17 launched Y18 ended

Describing a periodical F18 Serial WorkZ12 Issuing Rule Y38 has current issuing rule Y37 has former or current issuing rule Most of the description elements are not directly associated with the instance of F18 Serial Work, but through multiple instances of Z12 Issuing Rule indicating various aspects of the plan for publication

Describing a periodical: aspects of a publication plan Z12 Issuing Rule Y24 foresees use of title Z12 Issuing Rule Z10 Sequencing Pattern Z11 URL E35 Title E56 Language E54 Dimension E55 Type Y21 foresees use of language Y22 foresees sequencing pattern Y23 foresees dimension Y20 foresees type Y28 foresees URL (of frequency, carrier, digital format, content, medium…)

Describing a periodical: changes in a publication plan Z12 Issuing Rule Y15 replaced Z5 Issuing Rule Change Y16 replaced with E52 Time-Span E50 Date P4 has time-span P78 is identified by E61 Time Primitive P82 at some time within

Relationships among periodicals Z12 Issuing Rule Y25 foresees association with Z12 Issuing Rule Y26 foresees other edition Y27 foresees translation in (supplement, insert…) (different type of carrier, abridged edition, local edition…) (Not expressed directly from F18 Serial Work to F18 Serial Work, as the relationship can be stopped at any time without loss of identity for the involved serials: the relationship is therefore viewed as part of the production plans for the two serials involved in the relationship)

Relationships between periodicals and monographs Y39 is enhanced by monograph Y40 enhances monograph (special issue, supplementing monograph…) (base volume for an updating loose-leaf, supplemented monograph…) (Expressed directly from F18 Serial Work to F19 Publication Work, as the relationship remains valid at any point in time throughout the life of the periodical) F18 Serial Work F19 Publication Work

Continuations F18 Serial Work Y29 evolved into P119 meets in time with Z1 Serial Transformation F18 Serial Work F27 Work Conception F30 Publication Event Y1 provided a continuation to Y2 initiated as continuation R23 created a realisation of P134 continued Z7 Ending of Publication Z6 Starting of Publication P115 finishes P116 starts

‘Supersedes’ relationship F18 Serial Work Y31 was superseded by Z1 Serial Transformation F18 Serial Work F30 Publication Event Y3 provided a replacement to Y4 initiated as replacement R23 created a realisation of P134 continued Z7 Ending of Publication Z6 Starting of Publication P115 finishes P116 starts F27 Work Conception

Absorptions F18 Serial Work Y35 was absorbed in P119 meets in time with Z2 Absorption F18 Serial Work F30 Publication Event Y9 absorbed Y10 enhanced R23 created a realisation of P10 falls within E7 Activity Z7 Ending of Publication P115 finishes

Separations F18 Serial Work Y30 was partially continued by Z3 Separation F18 Serial Work F30 Publication Event Y12 separated from Y11 separated R23 created a realisation of P10 falls within F27 Work Conception Z6 Starting of Publication P116 starts

Mergers F18 Serial Work Y34 was merged to form Z1 Serial Transformation F18 Serial Work F30 Publication Event Y7 merged R23 created a realisation of P134 continued F18 Serial Work F30 Publication Event R23 created a realisation of Y7 merged Y33 was merged with Y34 was merged to form P134 continued Y8 merged into F27 Work Conception Z7 Ending of Publication Z6 Starting of Publication P115 finishes P116 starts Z7 Ending of Publication P115 finishes P119 meets in time with

Splits F18 Serial Work Y11 was split into Z1 Serial Transformation F18 Serial Work F30 Publication Event Y5 split Y6 initiated R23 created a realisation of P134 continued F18 Serial Work F30 Publication Event R23 created a realisation of Y6 initiated P134 continued Y32 was split into Z7 Ending of Publication Z6 Starting of Publication P115 finishes P116 starts Z6 Starting of Publication P116 starts P119 meets in time with F27 Work Conception

Temporary replacements F18 Serial Work Z4 Temporary Substitution F18 Serial Work F30 Publication Event P9 consists of F30 Publication Event R23 created a realisation of Y36 had surrogate F27 Work Conception F30 Publication Event Y14 substituted with Y13 provided surrogate to R23 created a realisation of R16 initiated P9 consists of P134 P10 falls within (if the replacing serial pre-exists) P20 had specific purpose (if the replacing serial is created specifically to replace the other one)