Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Creating better user interfaces for libraries catalogues: how to present and interact with (FRBR-based) bibliographic data? (ELAG 2013 Workshop)


Published on

Elag2013 slides and report for workshop "Creating better user interfaces for libraries catalogues: how to present and interact with (FRBR-based) bibliographic data?" by Tanja Merčun and Maja Žumer

Published in: Education, Technology
  • Be the first to comment

Creating better user interfaces for libraries catalogues: how to present and interact with (FRBR-based) bibliographic data? (ELAG 2013 Workshop)

  1. 1. Creating better user interfaces forlibrary catalogueshow to present and interact with(FRBR-based) bibliographic data?ELAG WorkshopGhent, 26. - 28. 5. 2013
  2. 2. Workshop LeadersMaja Žumer, PhDProfessorUniversity of Ljubljana, Sloveniamaja.zumer@ff.uni-lj.siTanja Merčun, PhDResearch AssistantUniversity of Ljubljana,
  3. 3. ELAG Workshop• not a tutorial• identification of issues, trends, and possible solutions• sharing of experience from different institutions• discussion on future work
  4. 4. Workshop OutlineOverview– missing features in library catalogues– FRBR & its potentials– FRBR-inspired library catalogue implementations &experiments– implementing FRBR-based displays
  5. 5. Generalwhat kind of search andexploration features do wewant/need to offer our users?• user needs• catalogue objectivesWorkshop OutlineDiscussion TopicsFRBRhow will FRBR-based userinterfaces look like?• how to make the best use ofFRBR-based data?• what will have to beconsidered in designingFRBR-based user interfaces?
  6. 6. Workshop Participants186610 5 10 15 20I am interested in the topic of librarycatalogue user interfaces.I want to learn more about FRBR.I want to discuss issues related toimplementing FRBR.No particular reason, it just soundedinteresting.Why did you decide to attend this workshop?
  7. 7. Workshop Participants612400 2 4 6 8 10 12 14I am not familiar with FRBR.I have basic understanding of FRBR.I am quite familiar with FRBR.I have in-depth knowledge of FRBR, itsissues and current developments.How familiar are you with FRBR?
  8. 8. Workshop Participants516YesNoHave you personally been involved in any projects involving theimplementation of FRBR in a library catalogue?
  9. 9. Workshop Participants35950 2 4 6 8 10Yes, we have already made some FRBRimplementations in our catalogue.Yes, it is one of our ongoing projects.We are thinking about it.No, not at this moment.Is FRBR-based catalogue redesign something you aredealing with or are thinking about in your institution?
  10. 10. Workshop ParticipantsTopics suggested for discussion:- alternatives to WEMI- advantages of FRBR-based catalogue redesign- user navigation / user expectations
  11. 11. Library Catalogueits troubles & current statusOVERVIEW
  12. 12. Why Change?• the information environment is changing– libraries are facing competition for the first time– new technologies, new approaches to knowledgeorganization, new generations of users– changes are becoming a reality also in libraries(new cataloguing rules, new formats)
  13. 13. Why Change?• issues with current catalogues– not perceived as intuitive (compared to other tools andservices)– users actively avoid using the catalogue– do not fully support users in their information seeking process– do not fulfil their main objectives– fail to bring out the richness and value of bibliographic data
  14. 14. Theory: catalogue objectives(2009) Statement of International Cataloguing PrinciplesThe catalogue should be an effective and efficient instrument thatenables a user:to find bib. resources in a collection as the result of a search using attributesor relationships of the resource :- to find a single resource- to find sets of resources representingall resources belonging to the same workall resources embodying the same expressionall resources exemplifying the same manifestationall resources associated with a given person, family, or corp. bodyall resources on a given subjectall resources defined by other criteria (language, date, contenttype, carrier, etc.)
  15. 15. Theory: catalogue objectives(2009) Statement of International Cataloguing Principlesto identify a bibliographic resource or agent (to confirm or to distinguish);to select a bibliographic resource that is appropriate to the user’s needs;to acquire or obtain access or to access, acquire, or obtain authority orbibliographic data;to navigate within a catalogue and beyond (…presentation of relationshipsamongworks, expressions, manifestations, items, persons, families, concepts,…).
  16. 16. Theory: catalogue objectives(1876) Cutter: Rules for a Printed Dictionary Catalog(1961) Paris Principlesknown-item search discoveryenable a person to find aknown-item specified byauthor, title, or some otheridentificationenable a person to discover:• which works by a particularauthor• which editions of a particularwork• what works on a specificsubjectare in the library.
  17. 17. RealityHow well does your library catalogue answer basicquestions about the library collection:– What works by Charles Dickens does the library hold?– Which is the latest work (!not edition) by Haruki Murakami?– Which works in the library collection have been performed byand which composed by Vladimir Horowitz?– What English translations of Iliad can you choose from?– Borrowing Pinocchio, whose illustrations can I choose from?
  18. 18. Reality• library catalogues– library catalogues are edition-centric– not very efficient or useful for inquiries beyond known-item search– Wikipedia as the resource for the fastest and mostcomplete answer to some questions
  19. 19. Reality• librarians– libraries are not questioning (enough) their tools– rely on tradition– often focused on minor issues, but forget to think aboutthe big picture• what questions should a library catalogue be able to answer• what kind of information seeking behaviour should itsupport
  20. 20. Reality• users– relatively satisfied with the current state/design ofcatalogue– current user expectations shaped (limited) by existingsystems– do not expect to find such information in a librarycatalogue
  21. 21. Theory vs. Reality• Don‘t we want to be THE source for such information?• Aren‘t libraries supposed to be the source of SUCHinformation? (not only library catalogues, also nationalbibliographies)• What is the added value of current bibliographicinformation systems?
  22. 22. FRBRpotentialsOVERVIEW
  23. 23. „The FRBR revolution“• user-oriented view of bibliographic data• catalogue as a database and not a replica of a cardcatalogue• re-thinking of current cataloguing theory and practice
  24. 24. FRBR Basic Concepts
  25. 25. FRBR Basic ConceptsFRBR conceptual model: entities, relationships & attributes1: products of intellectual or artistic endeavourWORKEXPRESSIONMANIFESTATIONITEM- an intellectual or artistic creation- an intellectual or artistic realization of a work- a physical embodiment of one or more expressions- a single exemplar of the manifestation
  26. 26. FRBR Basic Concepts
  27. 27. FRBR Basic Concepts
  28. 28. EXPRESSIONPerformance ofPaganini ViolinConcerto No. 1EXPRESSIONPerformance ofSaint-Saëns ViolinConcerto No. 3embodied inembodiesWORKSaint-Saëns ViolinConcerto No. 3WORKPaganini ViolinConcerto No. 1is realised inrealisesis realised inrealisesPERSONCamille Saint-SaënsMANIFESTATIONCDD 100186embodied inembodiesPERSONNicolo Paganinicreatedcreated bycreatedcreated byPERSONGli SharamCORPORATE BODYNew YorkPhilharmonicCORPORATE BODYDeutscheGrammophonPERSONGuiseppe Sinopoliperformed byperformedperformed byperformedperformed byperformedpublishedpublished by
  29. 29. Many Interesting Aspects…• conceptual model• FRBR family of models• frbrization – transformation of legacy data• identifiers• FRBR & catalogization (rules, standards, formats)• FRBR & catalogue user interface
  30. 30. Why FRBR & User Interfaces?• moving towards implementing FRBR in our cataloguesBUT– FRBR-based data is not a solution to library catalogueproblems in itself– pitfall = only partial implementation of FRBR that will failto bring the desired effect
  31. 31. Why FRBR & User Interfaces?• current library catalogue linear display approach is notsuited to the FRBR entity-relationship model• need to design a new type of display to take advantage ofthe richness (relationships!) and possibilities of FRBR-based data• knowing the end result we want to achieve help identify what is needed help develop the right set of rules, standards & tools help to implement a better library catalogue
  32. 32. FRBR Potential• create better bib. info. system user interfaces– meaningful clustering & exploration– different levels of abstraction• verified by user studies
  33. 33. FRBRuser interface implementations/experimentsOVERVIEW
  34. 34. FictionFinder OCLC
  35. 35. AustLit
  36. 36. AustLit
  37. 37. OLAC
  38. 38. Flemish Central Catalogue
  39. 39. Flemish Central Catalogue
  40. 40. Scherzo
  41. 41. VTLS
  42. 42. VTLS• hierarchical layout• WEMI• also expressions• reverse tree
  43. 43. FrbrVis• Motivation:– presentation of and interaction with FRBR-based data = unexplored– bibliographic universe  complex network of entities– traditional user interface displays  too limited• displaying FRBR structures & relationships• insight, exploration & discovery of bibliographic data– different approaches needed• allow exploration• overview of entities and relationships– develop, implement and evaluate an alternative model
  44. 44. MMMMMMMMM44
  45. 45. MM M M M M M M ME E EE EEEEW W W W W W45
  46. 46. novelliterary criticismTV documentaryWWWW WWWWWWW WWWWWWWWWWWWWWWWWWWW Wnovelmotion picturemusicalpicture bookplayillustrationsforeward46
  47. 47. W AbyWWWWWWWWWWWWWWW WWWWWWWWWWWWWWWWWWWWWWauthor aboutWWWWbiographiesTVdocumentariesWWreferenceworksliterarycriticismWWWnovelsfairy talesplayspoemspoemschildren‘sstoriesessays47
  48. 48. FrbrVisversions display
  49. 49. FrbrVisversions & editions of the workrelated worksworks related to the authorworkexpressionmanifestationworkauthorwork family
  50. 50. FrbrVis• information visualization• hierarchical technique: 4 layouts
  51. 51. FrbrVisrelated works display
  52. 52. FrbrVisby/about author display
  53. 53. FrbrVismissing attributesunidentified entitiesinconsistent catalogingconsistent use of descriptiveidentificationusing field linkingrelating attributes and agents to correctentities when there are more works orexpressions within a manifestationadding relator codesdistinguishing between the roles ofagents and connecting them toappropriate primary entity levelcreating relationshipsbetween primary entitiesmissing W-W, E-E, M-M relationshipsIDENTIFIED PROBLEMS RECORD IMPROVEMENTS
  54. 54. 0010080200411002402452603003363373383806557007007007761101410111108263064953081203s2008 nyua sb 000 0 eng d$a9780307272119$aeng $hswe$aLarsson, Stieg $d1954-2004 $4aut$aMillenium $n1 $pMan som hatar kvinnor $leng$aThe girl with the dragon tattoo $cby Stieg Larsson ; translated from theSwedish by Reg Keeland$aNew York $bAlfred A. Knopf $c2008$a1 online resource (465 p.)$atext$abook$aelectronic$aNovel$acrime fiction$aKeeland, Reg $d1943- $4trl$isequel $aLarsson, Stieg $d1954-2004 $tMillennium $n2 $pFlickan somlekte med elden $kNovel $4aut$iadapted as $tLuftslottet som sprängdes $kMotion picture$ielectronic reproduction of $aLarsson, Stieg, 1954-2004 $tThe girl with thedragon tattoo $b1st United States ed $dNew York : Alfred A. Knopf, 2008$h465 p. ; 25cm $z9780307269751CONSISTENT USE OFDESCRIPTIVE IDENTIFICATIONRELATOR CODESCREATING RELATIONSHIPS
  55. 55. 00100802004124526030033633733838038052052060065565570070070070001012121211000589797940128s1994 enk b 000|1 eng$a0192827650$aeng$aLittle women $cLouisa May Alcott ; with an introduction by Valerie Alderson$aOxford $bOxford University Press $c1994$axxxvi, 489 p. $c19cm$atext $81 $82 $83$abook$aprint$aNovel $81 $82$aForeword $83$aThe joys and sorrows of the four March sisters as they grow into youngwomen in nineteenth-century New England. $81$a Three years on from "Little Women", the March girls and their friend Laurieare young adults with their futures, full of trials ahead of them. $82$aAlcott, Louisa May $d1832-1888 $tLittle women $kNovel $4aut $83$ayoung adult fiction $81 $82$anon-fiction $83$aAlcott, Louisa May $d1832-1888 $tLittle women $leng $4aut $81$aAlcott, Louisa May $d1832-1888 $tGood wives $leng $4aut $82 $84$aAlderson, Valerie $t[Introduction to Little women] $leng $4aui $83$isequel to $aAlcott, Louisa May $d1832-1888 $tLittle women $4aut $84FIELD LINKING
  56. 56. Little women[Series]Little women[Novel]English, textpartL.M. Alcottbook - electronicOxford Press1994sequelGood wives[Novel]Little women[Play]English, text English, textbook – printDramatic Pub.1941realizationembodiedK. Laurencecreatedembodimentaudio book – CDBriliance, 1998English, spoken wordEnglish, spoken wordrealization realizationembodimentadaptationcreatedEnglish, textIntroduction toLittle women[Foreword]V. Aldersoncreatedis subject ofadaptationadaptationrealizationS. Burrrealized
  57. 57. FrbrVis• hierarchical visualization techniques– not a perfect match for complex networks of bib. data– enables grouping based on rel. types and attributes– more effective and user friendly display– quick overviews and efficient navigation• missing horizontal and bottom-up relationships– partial solution = multiple views in a work record display
  58. 58. FrbrVis• FrbrVis prototype – beyond classical WEM display• established relationships within a broader work family• interactive exploration• particularly useful for complex work sets• future development: sunburst and indented list
  59. 59. Obstacles to Implementation• conservative views• model is perceived as ‘very abstract and theoretical’• open to interpretation (e.g. expression)• legacy data• no data model, no cataloguing rules
  60. 60. Discussion Topics
  61. 61. Group discussion• What do we need to do to design FRBR-based interfaces?– Are any questions/issues missing?– Which should be answered first?• Your solutions/ideas connected to any of the questions?
  62. 62. Future Library Cataloguea) Functional & Content Requirements– What functions should be supported?– Is the full implementation of the FRBR model what we need toachieve? Is it too much or too little?– What data do we need to enable the desired features? Is thisdata included in our catalogue records or will it be?– What entities, relationships, and attributes are important?– How much do functions and data depend on the type ofmaterial or the type of catalogue?
  63. 63. Future Library Catalogueb) Interaction Design & Information Architecture– How should entities be clustered? Will we adopt the FRBR WEMIapproach? Or maybe create less granular or more granularcategorizations?– How do we deal with the varying complexities of works and authors?Is there a one size fits all solution?– What will be presented to the user at what point in their search?
  64. 64. Future Library Cataloguec) Interface & Navigation Design– What kind of links-paths for exploration should be enabled at aparticular point in the catalogue?– How would we best display the hierarchical and networkrelationships in the data? Is visualization a viable option?
  65. 65. Workshop Report
  66. 66. Strategydefine the jobs to be donesite objectivesuser needscontentrequirementsfunctionalspecificationsinformationarchitectureinteraction designinterface design navigation designvisual design(Garrett, 2002)
  67. 67. Scopedefine the data neededdefine the FRBRimplementation modelsite objectivesuser needscontentrequirementsfunctionalspecificationsinformationarchitectureinteraction designinterface design navigation designvisual design(Garrett, 2002)
  68. 68. Structure• define elements & clustering- for different complexities- for different types of data• define navigation pathsat different search/exploration pointssite objectivesuser needscontentrequirementsfunctionalspecificationsinformationarchitectureinteraction designinterface design navigation designvisual design(Garrett, 2002)
  69. 69. Skeleton• define presentation& layoutssite objectivesuser needscontentrequirementsfunctionalspecificationsinformationarchitectureinteraction designinterface design navigation designvisual design(Garrett, 2002)
  70. 70. Discussion OutcomesWho is going to lead the development of FRBR-basedcatalogues?
  71. 71. Discussion Outcomes• libraries are thinking about implementing FRBR, butcurrently there is no centre, group or library to turn to– huge task– no forum for exchange of ideas, experience, implementationmodels– no tools available– do not even know what has been or is being done in individualinstitutions– most libraries cannot afford to develop everything from scratch
  72. 72. Discussion Outcomes• What should be the result set?Works, expressions, manifestations or a combination?• How to create intuitive displays that would not beconfusing to the users?• no one-size-fits-all solutions: different interfaces fordifferent purpuses, needs, circumstances
  73. 73. Discussion Outcomes• our first important mission is to get the data right• frbrization of records vs FRBR only in discovery layer• FRBR-born data need new interfaces to support FRBR-based catalogization• WEMI model might be too complicated
  74. 74. Discussion Outcomes• stop waiting for everything to be perfect & start with thechanges• incremental modelling and development approach• start with small steps to improve existing functionalityand data• we cannot solve all the problems, but we need to startsomewhere
  75. 75. thanks for participating!contact: tanja.mercun@ff.uni-lj.sislides and the report prepared by Tanja Merčun and Maja Žumer