Successfully reported this slideshow.
Your SlideShare is downloading. ×

FRBR in a simplified way : Status report

Ad

FRBR in a simplified wayFRBR in a simplified way
Status reportStatus report
ADLUG Users Group MeetingADLUG Users Group Mee...

Ad

3 FRBR in a simplified way :
What is FRBRizationWhat is FRBRization
 Applying the FRBR conceptual modelApplying the FRBR ...

Ad

4 FRBR in a simplified way :
What have NSZL done so far?What have NSZL done so far?
Translated FRBR into HungarianTransla...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Upcoming SlideShare
Survival guide mojacar
Survival guide mojacar
Loading in …3
×

Check these out next

1 of 15 Ad
1 of 15 Ad
Advertisement

More Related Content

Advertisement

FRBR in a simplified way : Status report

  1. 1. FRBR in a simplified wayFRBR in a simplified way Status reportStatus report ADLUG Users Group MeetingADLUG Users Group Meeting Venice, 29-31 October, 2008Venice, 29-31 October, 2008 ÁdámÁdám HorváthHorváth NSZLNSZL
  2. 2. 3 FRBR in a simplified way : What is FRBRizationWhat is FRBRization  Applying the FRBR conceptual modelApplying the FRBR conceptual model on existing bibliographic informationon existing bibliographic information – Converting existing bibliographic dataConverting existing bibliographic data – Or just interpreting (run-time)Or just interpreting (run-time)  Different levels of ambitionDifferent levels of ambition – Following the FRBR model or just FRBR-inspiredFollowing the FRBR model or just FRBR-inspired – User interface only – presenting search results andUser interface only – presenting search results and allowing users to navigate along the axis of FRBRallowing users to navigate along the axis of FRBR relationshipsrelationships – Data model that implements (part of) the FRBR modelData model that implements (part of) the FRBR model
  3. 3. 4 FRBR in a simplified way : What have NSZL done so far?What have NSZL done so far? Translated FRBR into HungarianTranslated FRBR into Hungarian Matched the FRBR entities with HUNMARCMatched the FRBR entities with HUNMARC fields and subfieldsfields and subfields Analysed our cataloguing practiceAnalysed our cataloguing practice – Do we use fields that are no longer necessaryDo we use fields that are no longer necessary in the digital age?in the digital age? In cataloguing decisions we consult withIn cataloguing decisions we consult with the FRBR modelthe FRBR model
  4. 4. 5 FRBR in a simplified way : What have NSZL done so far?What have NSZL done so far? Adopted the OCLC work set algorithm toAdopted the OCLC work set algorithm to HUNMARC in Oracle levelHUNMARC in Oracle level Programmed the algorithm forProgrammed the algorithm for monographsmonographs
  5. 5. 6 FRBR in a simplified way : FRBRization planFRBRization plan We do not want to includeWe do not want to include thethe FRBRizFRBRizationation into the cataloguing processinto the cataloguing process – It would mean extra workIt would mean extra work • Work and expression records must also be createdWork and expression records must also be created – How much extra work?How much extra work? • Depends on the implementationDepends on the implementation – Our cataloguers refuse to do any extraOur cataloguers refuse to do any extra cataloguing workcataloguing work
  6. 6. 7 FRBR in a simplified way : FRBRization planFRBRization plan DecisionDecision – Implement the FRBR model just in the OPACImplement the FRBR model just in the OPAC – Implement just partlyImplement just partly • Show the other editions of a given documentShow the other editions of a given document • This information is needed frequentlyThis information is needed frequently • Currently it is not easy to get this information fromCurrently it is not easy to get this information from the OPACthe OPAC – It should be the integral part of the OPACIt should be the integral part of the OPAC
  7. 7. 8 FRBR in a simplified way : FRBRization planFRBRization plan Two possibilitiesTwo possibilities – Create work records and store theCreate work records and store the relationships thererelationships there • Needs writing in many tablesNeeds writing in many tables • Needs major change in the OPACNeeds major change in the OPAC – Store just the relationshipsStore just the relationships • Easier to implementEasier to implement • No change in the current OPACNo change in the current OPAC
  8. 8. 9 FRBR in a simplified way : First resultFirst result We can show the other editions ofWe can show the other editions of monographsmonographs – Needed minimal changes in the AmicusNeeded minimal changes in the Amicus databasedatabase – There was no need to make any changes inThere was no need to make any changes in our OPACour OPAC
  9. 9. 10 FRBR in a simplified way : DemonstrationDemonstration
  10. 10. 11 FRBR in a simplified way : DemonstrationDemonstration
  11. 11. 12 FRBR in a simplified way : DemonstrationDemonstration
  12. 12. 13 FRBR in a simplified way : Evaluation of the resultEvaluation of the result To many relationships have to be storedTo many relationships have to be stored The other edition relationship is displayedThe other edition relationship is displayed among the otheramong the other „„ordinaryordinary”” relationshipsrelationships – It would need a separate listIt would need a separate list Slows down the OPACSlows down the OPAC
  13. 13. 14 FRBR in a simplified way : Where to go now?Where to go now? FRBR service?FRBR service? – Based on a (RDF?) database outside ofBased on a (RDF?) database outside of AmicusAmicus – The service will be called from the OPACThe service will be called from the OPAC – It would show the entire work treeIt would show the entire work tree • How can we get back to the OPAC to the sameHow can we get back to the OPAC to the same session?session? • AJAX might help?AJAX might help? The final solution still needs discussionsThe final solution still needs discussions
  14. 14. adam@oszk.huadam@oszk.hu Thank you for your attentionThank you for your attention

×