Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Jerome Overview

Jerome Overview

A high-level overview of the basics of unproject Jerome at the University of Lincoln.

C7f3b4756d808ef0e2548bd0965ac225?s=128

Nick Jackson

August 04, 2010
Tweet

More Decks by Nick Jackson

Other Decks in Technology

Transcript

  1. THE OVERVIEW 100% free of technical stuff

  2. WHAT WE’RE DOING • Building a new storage system for

    catalogue data. • Providing new faster search tools for the catalogue. • Opening access to the data stored within the library. • Starting work on a new ‘library portal’ for users.
  3. WHY WE’RE DOING IT • The current catalogue (Stored in

    Horizon) is difficult to get data from without using Horizon’s own portal. • The data isn’t provided in a way which computers can easily use to do interesting things with. • Horizon’s own portal doesn’t integrate well with other services like eJournals or reading lists.
  4. HOW WE’RE DOING IT Part 1: Data Storage

  5. CURRENT DATA STORAGE Horizon by SirsiDynix Can’t keep up with

    high-demand services, but is an LMS.
  6. NEW DATA STORAGE MongoDB by 10gen Very fast, but doesn’t

    provide LMS tools or search
  7. SEARCH Sphinx Very fast and provides full-text search

  8. THE PLAN Put them together and what have you got...

    Convert Horizon to MongoDB Make MongoDB ready to search
  9. HOW WE’RE DOING IT Part 2: Data Access

  10. THE USER Just some random person

  11. USER-FACING A user reads and searches library data via their

    web browser
  12. THE COMPUTER Could be anything at all, as long as

    it wants to read our data
  13. COMPUTER-FACING Computers can read and search library data over specialised

    ‘machine-readable’ services
  14. WHY COMPUTERS? People can use this information to build new,

    exciting services like book recommendation systems based around our data
  15. HOW WE’RE DOING IT Part 3: A New Portal

  16. THE PROBLEM • We have loads of services which we

    want people to use. • People have to visit them all individually, log in individually and learn a whole new interface for each service.
  17. HOW WE’RE FIXING IT • A new look based around

    the University’s Common Web Design. • All services have an access point based around a single portal. • Where possible, build access to features into the new site.
  18. MORE STUFF •Follow our blog: http://jerome.blogs.lincoln.ac.uk •Email me: nijackson@lincoln.ac.uk •Twitter:

    @jacksonj04 Awesome hand-drawn icons by Aleksandra Wolska (http://www.olawolska.com/)