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.
BOOK READER BINGO:
WHICH PAGE TURNER SHOULD I USE?
Eben English, Boston Public Library
@ebenenglish
Code4Lib 2015
WHAT WE TALK ABOUT
WHEN WE TALK ABOUT PAGE
TURNERS
Source: https://flic.kr/p/6Dpfff
WHAT’S IN SCOPE
• web-based
• open source
• updated in last 2 years
ONE OF THESE THINGS IS
NOT LIKE THE OTHERS
Source: http://murlocparliament.com/wp-content/uploads/2010/12/1Of_These_Things...
EVERYTHING IS AWESOME
Source: http://cdn.screenrant.com/wp-content/uploads/lego-movie-poster-1970s-astronaut-570x350.jpg
FORYOUR CONSIDERATION
• Internet Archive BookReader
• WDLViewer
• Wellcome Player
• Diva.js
• Mirador 2*
INTERNET ARCHIVE
BOOKREADER
https://github.com/openlibrary/bookreader
INTERNET ARCHIVE
BOOKREADER
Strengths
•lots of examples to draw on
•supports keyword search
•embeddable (via <iframe>)
Dra...
WDLVIEWER
https://github.com/LibraryOfCongress/wdl-viewer
WDLVIEWER
Strengths
•supports search (in a branch)
•tile-based zooming
•image rotation
Drawbacks
•search results display “...
WELLCOME PLAYER
https://player.digirati.co.uk/
WELLCOME PLAYER
Strengths
•book-smart page numbering
•supports multi-volume works
•keyword searching, structural nav, item...
DIVA.JS
http://ddmal.github.io/diva.js/
DIVA.JS
Strengths
•controls for changing brightness, contrast, rotation
•supports keyword search
•vertical and horizontal ...
MIRADOR 2*
http://github.com/iiif/m2
MIRADOR 2*
Strengths
•side-by-side comparison of multiple items
•annotation support
•structural navigation
Drawbacks
•no s...
OTHER CRITERIA
(SEE APPENDIX)
• how actively maintained is it?
• code weight
• documentation
• mobile/tablet UX
• older br...
IIIF PRESENTATION API
http://iiif.io/api/presentation/2.0
• API to deliver structural and presentation info
• returns JSON...
IIIF PRESENTATION API
ranked by level of compliance
• Mirador 2: fully compliant
• Internet Archive BookReader: IIIF-compl...
USABILITY TESTING
• What features do users really want?
• What features are most useful?
• What features are lacking?
• Wh...
USABILITY OBSERVATIONS
PRINT READING MODELS
DON’T ALWAYS TRANSLATE
“If I have to use the Table of Contents, it
means somet...
USABILITY OBSERVATIONS
USERS MOVE IN
MYSTERIOUS WAYS
•controls should be consistent no matter what view or mode
is being u...
USABILITY OBSERVATIONS
FUNCTION OVER FORM...
...but form is still important.
•maintaining the “book” feel adds to the user...
USABILITY OBSERVATIONS
USERS ARE IMPATIENT
• the app needs to be fast
• any image loading should be clearly communicated
W...
USABILITY OBSERVATIONS
MOSTVALUABLE FEATURES
•keyword searching
•structural navigation
•page # input
•in-reading research ...
USABILITY OBSERVATIONS
MISSING FEATURES
•selecting and copying text
•printing pages
•annotations
•bookmarks
SO WHICH ONE SHOULD I USE?
• content types are important
• IIIF API support
• mobile/tablet usage will continue to increas...
ACKNOWLEDGEMENTS
• BPL: Steven Anderson, Manny Adumbire
• Simmons College UXPA Group
QUESTIONS
Eben English
eenglish [at] bpl.org
@ebenenglish
APPENDIX
ACTIVELY MAINTAINED
ranked by # of commits in the last 12 months
1. Diva.js
2. Mirador 2*
3. Wellcome Player
4. I...
APPENDIX
CODE WEIGHT
ranked (lightest to heaviest) by total KB of JS + CSS + images (uncompressed)
1. WDL Viewer
2. Diva.j...
APPENDIX
DOCUMENTATION
(subjectively) ranked by comprehensiveness and helpfulness of documentation
1. Diva.js
2. Wellcome ...
APPENDIX
MOBILE/TABLET UX
(subjectively) ranked by user experience on iOS and Android
1. Mirador 2*
2. WDL Viewer
3. Diva....
APPENDIX
OLDER BROWSERS UX
ranked by user experience in IE8
YEP: Wellcome Player, WDL Viewer
NOPE: Diva.js, Internet Archi...
APPENDIX
# OF IMPLEMENTATIONS
ranked by # of forks of GitHub repo
1. Internet Archive BookReader
2. Diva.js
3. Wellcome Pl...
APPENDIX
IMPLEMENTATION
(subjectively) ranked by ease of implementation
1. WDL Viewer
2. Internet Archive BookReader
3. Mi...
Upcoming SlideShare
Loading in …5
×

Book Reader Bingo: Which Page-Turner Should I Use?

Presented at Code4Lib 2015 in Portland, OR on February 10, 2015 by Eben English (eenglish [at] bpl.org, Boston Public Library)

Another day, another library reinventing the book-viewer wheel. When will the madness end? This talk will explore the current landscape of book-viewer/page-turner applications for digital library systems with an eye towards helping you make the right decision for your project. We'll look at some the major players on the market (such as Internet Archive BookReader, Wellcome Player, Mirador, and WDL-Viewer to name a few) and compare them based on a number of criteria: feature sets, mobile/tablet friendliness, ease of integration, code health, test coverage, "market share" (number of implementers), and other important factors. We'll look at the results of ACTUAL USABILITY TESTS to see what features users REALLY want in a book-viewer, and how each app measures up.

We'll also discuss important recent trends (such as the IIIF
Presentation API) that have the potential to shape the book-viewer development landscape in the immediate future. Which page-turner applications are best poised to adopt/integrate/leverage these emerging standards? Which will become obsolete? This talk has the answers you need.

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

Book Reader Bingo: Which Page-Turner Should I Use?

  1. 1. BOOK READER BINGO: WHICH PAGE TURNER SHOULD I USE? Eben English, Boston Public Library @ebenenglish Code4Lib 2015
  2. 2. WHAT WE TALK ABOUT WHEN WE TALK ABOUT PAGE TURNERS Source: https://flic.kr/p/6Dpfff
  3. 3. WHAT’S IN SCOPE • web-based • open source • updated in last 2 years
  4. 4. ONE OF THESE THINGS IS NOT LIKE THE OTHERS Source: http://murlocparliament.com/wp-content/uploads/2010/12/1Of_These_Things.jpg
  5. 5. EVERYTHING IS AWESOME Source: http://cdn.screenrant.com/wp-content/uploads/lego-movie-poster-1970s-astronaut-570x350.jpg
  6. 6. FORYOUR CONSIDERATION • Internet Archive BookReader • WDLViewer • Wellcome Player • Diva.js • Mirador 2*
  7. 7. INTERNET ARCHIVE BOOKREADER https://github.com/openlibrary/bookreader
  8. 8. INTERNET ARCHIVE BOOKREADER Strengths •lots of examples to draw on •supports keyword search •embeddable (via <iframe>) Drawbacks •harder to work with images of varying sizes •zoom not tile-based •lacks: rotation, page # input, structural nav
  9. 9. WDLVIEWER https://github.com/LibraryOfCongress/wdl-viewer
  10. 10. WDLVIEWER Strengths •supports search (in a branch) •tile-based zooming •image rotation Drawbacks •search results display “linear”-only •page # index display reflects image index rather than book pages •lacks: structural nav
  11. 11. WELLCOME PLAYER https://player.digirati.co.uk/
  12. 12. WELLCOME PLAYER Strengths •book-smart page numbering •supports multi-volume works •keyword searching, structural nav, item information Drawbacks •page loading status unclear •confusing image # input •lacks: 2-page “book” view, full-screen view
  13. 13. DIVA.JS http://ddmal.github.io/diva.js/
  14. 14. DIVA.JS Strengths •controls for changing brightness, contrast, rotation •supports keyword search •vertical and horizontal reading layouts Drawbacks •requires IIP Image server •image vs. page numbering •lacks: structural nav, contextual info
  15. 15. MIRADOR 2* http://github.com/iiif/m2
  16. 16. MIRADOR 2* Strengths •side-by-side comparison of multiple items •annotation support •structural navigation Drawbacks •no search support (yet) •controls sometimes obscured by content •lacks: keyboard shortcuts for page navigation
  17. 17. OTHER CRITERIA (SEE APPENDIX) • how actively maintained is it? • code weight • documentation • mobile/tablet UX • older browsers UX • implementation process • # of implementations
  18. 18. IIIF PRESENTATION API http://iiif.io/api/presentation/2.0 • API to deliver structural and presentation info • returns JSON-LD • abstracting page sequence out of the data passed to viewer functions • allows for richer structural navigation • easily share works between repositories Source: http://iiif.io/api/presentation/2.0/img/objects.png
  19. 19. IIIF PRESENTATION API ranked by level of compliance • Mirador 2: fully compliant • Internet Archive BookReader: IIIF-compliant fork (https://github.com/aeschylus/IIIFBookReader) • Diva.js: branch with work on Image and Presentation APIs • Wellcome Player: Image API, but not Presentation API (yet) • WDLViewer: no known activity?
  20. 20. USABILITY TESTING • What features do users really want? • What features are most useful? • What features are lacking? • Which book-reader do they like best?
  21. 21. USABILITY OBSERVATIONS PRINT READING MODELS DON’T ALWAYS TRANSLATE “If I have to use the Table of Contents, it means something’s not working right.” Winners: Wellcome Player, Mirador 2
  22. 22. USABILITY OBSERVATIONS USERS MOVE IN MYSTERIOUS WAYS •controls should be consistent no matter what view or mode is being used •reading and research functionality (cite, link, info, etc.) should be integrated Winners: Wellcome Player, Internet Archive BookReader
  23. 23. USABILITY OBSERVATIONS FUNCTION OVER FORM... ...but form is still important. •maintaining the “book” feel adds to the users’ enjoyment of the interface Winners: WDL Viewer, Internet Archive BookReader
  24. 24. USABILITY OBSERVATIONS USERS ARE IMPATIENT • the app needs to be fast • any image loading should be clearly communicated Winners: Diva.js, WDL Viewer
  25. 25. USABILITY OBSERVATIONS MOSTVALUABLE FEATURES •keyword searching •structural navigation •page # input •in-reading research functions (download, link, info, etc.) Winners: Wellcome Player, Internet Archive BookReader
  26. 26. USABILITY OBSERVATIONS MISSING FEATURES •selecting and copying text •printing pages •annotations •bookmarks
  27. 27. SO WHICH ONE SHOULD I USE? • content types are important • IIIF API support • mobile/tablet usage will continue to increase • care and feeding of the code
  28. 28. ACKNOWLEDGEMENTS • BPL: Steven Anderson, Manny Adumbire • Simmons College UXPA Group
  29. 29. QUESTIONS Eben English eenglish [at] bpl.org @ebenenglish
  30. 30. APPENDIX ACTIVELY MAINTAINED ranked by # of commits in the last 12 months 1. Diva.js 2. Mirador 2* 3. Wellcome Player 4. Internet Archive BookReader 5. WDL Viewer
  31. 31. APPENDIX CODE WEIGHT ranked (lightest to heaviest) by total KB of JS + CSS + images (uncompressed) 1. WDL Viewer 2. Diva.js 3. Internet Archive BookReader 4. Mirador 2* 5. Wellcome Player
  32. 32. APPENDIX DOCUMENTATION (subjectively) ranked by comprehensiveness and helpfulness of documentation 1. Diva.js 2. Wellcome Player 3. Internet Archive BookReader 4. WDL Viewer
  33. 33. APPENDIX MOBILE/TABLET UX (subjectively) ranked by user experience on iOS and Android 1. Mirador 2* 2. WDL Viewer 3. Diva.js 4. Wellcome Player 5. Internet Archive BookReader
  34. 34. APPENDIX OLDER BROWSERS UX ranked by user experience in IE8 YEP: Wellcome Player, WDL Viewer NOPE: Diva.js, Internet Archive BookReader, Mirador 2*
  35. 35. APPENDIX # OF IMPLEMENTATIONS ranked by # of forks of GitHub repo 1. Internet Archive BookReader 2. Diva.js 3. Wellcome Player 4. WDL Viewer
  36. 36. APPENDIX IMPLEMENTATION (subjectively) ranked by ease of implementation 1. WDL Viewer 2. Internet Archive BookReader 3. Mirador 2* 4. Wellcome Player 5. Diva.js

×