Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "A Brief Presentation of PRESS OO For the CIDOC CRM SIG and FRBR/CRM Harmonisation WG 21 October 2013."— Presentation transcript:

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

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

3 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

4 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

5 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

6 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

7 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

8 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)

9 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

10 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

11 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…)

12 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

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

14 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

15 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

16 ‘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

17 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

18 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

19 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

20 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

21 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)


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

Similar presentations


Ads by Google