Transforming FRBR into FRBRoo / Patrick Le Boeuf

2,362 views

Published on

Conferenza tenuta presso la ex SSAB da Patrick Le Boeuf (Bibliothèque Nationale de France) il 10-05-2013 nell'ambito del 7. ciclo "Biblioteche libri documenti: dall'informazione alla conoscenza", a.a. 2012-2013, Prof.ssa M.T. Biagetti

Published in: Business, Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,362
On SlideShare
0
From Embeds
0
Number of Embeds
886
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Transforming FRBR into FRBRoo / Patrick Le Boeuf

  1. 1. Transforming FRBRinto FRBROOCiclo “Biblioteche, libri, documenti: dall‟informazione alla conoscenza”organizzato dalla prof.ssa Maria Teresa BiagettiRome, 10 May 2013Patrick Le Boeuf, National Library of France
  2. 2. INTRODUCTIONTransforming FRBR into FRBROO
  3. 3. FRBR:A Modelfor the 19thcentury?Charles A. Cutter,Catalogue of the Libraryof the Boston Athenæum(1874-82)
  4. 4. FRBR: A Modelfor the 21st century?• 2009: International Cataloguing Principles, ICP(replacing the ‘Paris Principles’)• 2009: Regole italiane di catalogazione, REICAT(replacing RICA)• 2010: Resource Description and Access, RDA(replacing AACR)
  5. 5. FRBR: A Family of Models• 1998: Functional Requirements forBibliographic Records, FRBR• 2009: Functional Requirements forAuthority Data, FRAD• 2011: Functional Requirements forSubject Authority Data, FRSAD• 20..: on the agenda: a single modelmerging FRBR, FRAD, FRSAD
  6. 6. FRBR: A Modelfrom the Librarians’ Community• In the meantime, in museums… 1995: development of ICOM’s CIDOC CRMICOM: International Council of MuseumsCIDOC : International Committee for DocumentationCRM: Conceptual Reference Model 2006: CIDOC CRM published as ISO 21127 Today: refinements still being made in theCIDOC CRM
  7. 7. FRBR + CIDOC CRM = FRBROO• 2003: International Working Group onFRBR and CIDOC CRM Harmonization• 2009: FRBROO version 1.0(bibliographic data only)• 2012-2013: FRBROO version 2.0(bibliographic + authority data)
  8. 8. QUICK REMINDER ON THE‘FR FAMILY’Transforming FRBR into FRBROO
  9. 9. Thema NomenRules Agencyis governed by creates/modifiesappliesis aboutPersonCorporate BodyFamilyItemManifestationExpressionConceptObjectEventPlaceWorkControlledAccess Pointis basis forNameIdentifierhas appellationFRBR + FRAD + FRSAD
  10. 10. BRIEF PRESENTATION OFCIDOC CRMTransforming FRBR into FRBROO
  11. 11. E39 Actor E28 Conceptual ObjectE18 Physical ThingE52 Time-Span E53 PlaceE55 TypeE41 Appellationinvolves affectsoccurs during occurs inidentifies any ofserves to categorize any ofE5 EventThe Core of CIDOC CRM
  12. 12. ‘IF THERE’S A DATE,THERE’S AN EVENT!’Transforming FRBR into FRBROO
  13. 13. Publication Date vs. Printing DateF30 PublicationEventP4 has time-spanF32 CarrierProduction EventF19 PublicationWorkF24 PublicationExpressionF5 ItemE52 Time-SpanE50 DateE52 Time-SpanE50 DateP4 has time-spanP78 is identified by P78 is identified by(in FRBR: „Date of Manifestation‟ attribute) (in FRBR: no attribute declared;would be „Date of Item‟)R3 is realised inR6 carriesR24 createdR23 created a realisation ofR28 produced
  14. 14. Externalizing an ExpressionF28 ExpressionCreationR17 createdE65 Creation E12 ProductionF2 ExpressionF4 ManifestationSingletonP4 has time-spanE52 Time-SpanE50 DateP78 is identified byR18 createdis a subclass of is a subclass of
  15. 15. Summary so farF30 PublicationEventF32 CarrierProduction EventF24 PublicationExpressionF5 ItemR6 carriesR24 createdR28 producedF28 ExpressionCreationR17 createdF2 ExpressionR14 incorporatesis a subclass of
  16. 16. FRBR: ‘The date of the work isthe date (normally the year) thework was originally created’
  17. 17. When was a Work‘originally created’?• = Earliest known Expression?• = Earliest known Manifestation Singleton?• But, then, Work Creation is in no waydistinct from Expression Creation? How tomodel the notion of ‘earliest known …’without using complex algorithms?
  18. 18. From ‘the date the Workwas originally created’…• … to:‘the date the Work was originally conceived‟• Controversial: How do we know? What if a Work is conceived by A and realized by B?• However, useful in order to expressthe notion of ‘Creator of the Work’
  19. 19. Work ConceptionP4 has time-spanE52 Time-SpanE50 DateP78 is identified byP4 has time-spanE52 Time-SpanE50 DateP78 is identified byF28 ExpressionCreationR17 createdF22 Self-ContainedExpressionF1 WorkF27 WorkConceptionE21 PersonE55 TypeP14 carried out byP14.1 in role ofE21 PersonE55 TypeP14 carried out byP14.1 in role ofR16 initiatedR3 is realised in(e.g., „author‟)(e.g., „translator‟)
  20. 20. Further Dates, Further EventsF29 RecordingEventP4 has time-spanE52 Time-SpanE50 DateP78 is identified byF31 PerformanceP4 has time-spanE52 Time-SpanE50 DateP78 is identified byF33 ReproductionEventP4 has time-spanE52 Time-SpanE50 DateP78 is identified by(of recording) (of performance) (of reproduction)
  21. 21. ‘Date’ Attribute for a PersonF51 PursuitP4 has time-spanE52 Time-SpanE50 DateP78 is identified byE21 PersonP14 carried out byE67 BirthP4 has time-spanE52 Time-SpanE50 DateP78 is identified byE69 DeathP4 has time-spanE52 Time-SpanE50 DateP78 is identified byP98 brought into life P100 was death of(of birth) (of activity) (of death)
  22. 22. ‘Date’ Attribute for a Family(declared, but not defined, in FRAD)F51 PursuitP4 has time-spanE52 Time-SpanE50 DateP78 is identified byF39 FamilyP14 carried out by(of activity)
  23. 23. ‘Date’ Attributefor a Corporate BodyDate of meeting,conference, etc.Date of establishment,dates of existenceE7 ActivityP4 has time-spanE52 Time-SpanE50 DateP78 is identified byF11 CorporateBodyP14 carried out byF51 PursuitP4 has time-spanE52 Time-SpanE50 DateP78 is identified byF11 CorporateBodyP14 carried out byE66 FormationP4 has time-spanE52 Time-SpanE50 DateP78 is identified byE68DissolutionP4 has time-spanE52 Time-SpanE50 DateP78 is identified byP95 formed P99 dissolved(of meeting,conference, etc.)(of formation) (of activity) (of dissolution)
  24. 24. FRAD: ‘Dates of Usage’Attribute for a NameP4 has time-spanE52 Time-SpanE50 DateP78 is identified by(of usage)F52 Name UseActivityE1 CRM Entity E41 AppellationP1 is identified byR63 named R64 used name
  25. 25. A MODELFOR AUTHORITY WORKTransforming FRBR into FRBROO
  26. 26. F35 Nomen UseStatementF52 Name UseActivityE1 CRM Entity(i.e., anything inthe real world)F50 ControlledAccess PointE41 AppellationR32 is warranted byR37statesR64usednameR8 consists ofF34 KOS(i.e., authority file)R35 is specified byF40 IdentifierAssignmentF43 Identifier RuleR52 used ruleF44 BibliographicAgencyP14 carried out byR45assignedtoe.g., saying:“Ciao tutti!mi chiamoUmberto Eco”e.g., Umberto Ecoe.g., RICAe.g., ICCUe.g., Eco, Umbertoe.g., statement in record ITICCU0000019852e.g., SBN as of April 10, 2013e.g.,Authority work in FRBROO(simplified view)e.g., creating record ITICCU0000019852E31 DocumentP70 documentse.g., Dizionario della letteratura…
  27. 27. WHAT ABOUT THE ‘WEMI’CLASSES IN FRBROO?Transforming FRBR into FRBROO
  28. 28. WorkF1 WorkF14 IndividualWorkF15 ComplexWorkF21 RecordingWorkF16 ContainerWorkF17 AggregationWorkF19 PublicationWorkF20 PerformanceWorkF18 SerialWorkis a subclass ofis a subclass of is a subclass of is a subclass ofis a subclass of is a subclass of is a subclass ofis a subclass ofis a subclass of
  29. 29. ExpressionF2 Expressionis a subclass ofF22 Self-ContainedExpressionF23 ExpressionFragmentF24 PublicationExpressionF25 PerformancePlanF26 RecordingF34 KOSF35 NomenUse Statementis a subclass of is a subclass ofis a subclass ofis a subclass of is a subclass of is a subclass of
  30. 30. ManifestationF24 PublicationExpressionF3 ManifestationProduct TypeCLR6 should carryF4 ManifestationSingletonF3 ManifestationProduct TypeCLR6 should carrye.g., hardcover e.g., paperbacka unique carrier,e.g., a manuscript
  31. 31. ItemF5 Item
  32. 32. WHO USES FRBROO?Transforming FRBR into FRBROO
  33. 33. IS FRBR/FRBROO ALREADYOUTMODED?Transforming FRBR into FRBROO
  34. 34. A Declaration of Imperialist War• November 2012: publication of theBIBFRAME model by Library of Congress Incompatible with RDA Incompatible with International CataloguingPrinciples Incompatible with FRBR Basically only compatible with MARC21 andAACR … but curiously, partially compatible with FRBROO:
  35. 35. F24 PublicationExpressionF3 ManifestationProduct TypeCLR6 should carry
  36. 36. BY WAY OF CONCLUSIONTransforming FRBR into FRBROO
  37. 37. By Way of Conclusion• No need to make FRBROO visible by end-users• No need to make FRBROO visible by cataloguers• FRBROO is not a display tool• FRBROO is a formalization of the meaning of theinformation embedded in catalogues• FRBROO is a tool to interpret and interconnectexisting data sets• FRBROO may well be more widely used in thefuture outside libraries than within them

×