IT staff and librarians pull together:

1. IT staff and librarians pull together: Collaborative development of a new METS viewer Matthias Groß, Bavarian State Library Implementation: Dr. Petra Schröder IGeLU Berlin 2013

2. The BVB • BVB: cooperative association of scientific libraries in Bavaria • Bavarian State Library, 11 university libraries, 17+ libraries of universities of applied sciences, 10 regional state libraries, > 100 further libraries • Head office: IT service center for the member libraries (services: network catalogue B3Kat, ILS hosting, SFX, Rosetta, Primo … and DigiTool)

3. DigiTool@BVB • Material in our DigiTool installation: mostly digitized books and journals • > 13.000 digital entities of type METS or COMPLEX • child objects are usually single pages • large METS objects can have 8000 child objects • End user access • < 10% via Resource Discovery • > 90% via OPACs / Google / Wikipedia / newsgroups / bookmarks • Librarians (and, maybe, also end users …) were unhappy with the presentation of retro-digitized content in DigiTool IGeLU Berlin 2013

4. Kick-off meeting (round-table) • 8 interested librarians from 6 libraries using DigiTool • 3 BVB Head Office staff • specification of problems • collaborative analysis of well-done examples like eLuxemburgensia and dilibri this input  concept for our new METS viewer IGeLU Berlin 2013

5. Requirement #1 Start view • bibliograpic metadata at the left side, display can be switched off • metadata enhanced by: • Bookmark URL or, if available, „handle“ URL • URL of corresponding digital collection • URL of additional material, particularly for manuscripts • more room for the digitized page – the main actor! • breadcrumbs felt to be dispensable • side-by-side view is seldom used (hard to read) • other functionality of the top toolbar moved to the left IGeLU Berlin 2013

6. „Old“ start view

7. New start view IGeLU Berlin 2013

8. Requirement #2 Thumbnail overview: • much more thumbnails • for retro-digitized books the first images are usually not so interesting: binding, flyleafs, bastard title … • vertical scrolling is somehow confusing IGeLU Berlin 2013

9. Thumbnails Bundle of 50 throttled by JavaScript IGeLU Berlin 2013

10. Thumbnails IGeLU Berlin 2013

11. Thumbnails Bundle of 50throttled by JavaScript IGeLU Berlin 2013

12. Requirement #3 Display of StructMaps: • good StructMaps take a lot of work • truncating their display annihilates that work  line break • end users usually do not understand the concept of having several StructMaps  show only logical StructMap IGeLU Berlin 2013

13. ToCbefore IGeLU Berlin 2013

14. ToCnow • Bild neuer Viewer IGeLU Berlin 2013

15. ToCnow IGeLU Berlin 2013

16. Requirement #4 Deep linking to single pages • show bookmark URL for a single page • when retrieved, the TOC has to open at the right place IGeLU Berlin 2013

17. Get deep link IGeLU Berlin 2013

18. Use deep link IGeLU Berlin 2013

19. Requirement #5 Reliable full text search • handling of „umlauts“ • transfer of search terms from the Resource Discovery is problematic: RD adds further search terms (e.g. the collection ID) that do not appear in the plain full text • hit list should be easier to understand IGeLU Berlin 2013

20. Search resultbefore Transcription Viewer IGeLU Berlin 2013

21. Search resultnow Oracle Full Text Searchbuilt-in fuzzy search possible IGeLU Berlin 2013

22. Development • Start: September 30th, 2012 • viewer preprocessor • no appropiate viewer preprocessor found for COMPLEX+METS • developing a slim BVBContainerVPP (encouraged by Rosetta) • Table of Contents • mapping ToC => PIDs: in DigiTool a time-consuming job • Exlibris NMetsVPP keeps information in Session Management • ToCs change not frequently • we keep information in a file system cache • User Interface well known jquery libraries • Border layout : ui-layout • ToC tree view : jstree IGeLU Berlin 2013

23. Development • After only 10 weeks the new viewer could be tested by our inspiring librarians(delivery-Rules are really flexible  ) • Librarians‘ tasks: • Test how objects from their own library are displayed • Suggest ehnancements • Revise the „wording“ (German/English) • Tell us how to group the metadata for display • Switch to production • March 2013 (graded by library) IGeLU Berlin 2013

24. Benefits • Server main memory • 200 to 700 deliveries of METS/COMPLEX per day • before STP: close to maximum limit of 4 GByte • after STP: usually less than 3 GByte • difference: session management used more housewifely? • End User • no expired session after lunch break like before: IGeLU Berlin 2013

25. Side effect • We found J2K Viewer much too slow for delivery of large images • superfluous identify request • no caching of icons and css • redundant requests for css • New JPEG-Viewer • Default Viewer Preprocessor • Image viewer plugin for jquery: jquery.iviewer • zoom by mouse scroll • move section by mouse • Rotate image • Easy to integrate for everyone IGeLU Berlin 2013

26. Next steps • PDF download selection based on ToC instead of page numbers • Full Text Search: make also ToC searchable • Perhaps: facilitate SingleViewer • Many - partially souperfluos - icon requests without caching • Redundant calls of css (5 requests for just 2 different files) • Much too much code IGeLU Berlin 2013

27. You may test our viewer(s) yourself http://digipool.bib-bvb.de/bvb/IGeLU IGeLU Berlin 2013

28. Enjoy! IGeLU Berlin 2013