1. Using the Aleph REST API to
support item requests from a
separate discovery system
(Aquabrowser)
by Corinna Baksik
Development work by:
Michael Vandermillen
2. Why? #1: Seamless user experience
http://hollis.harvard.edu/?itemid=|library/m/aleph|012353769
http://cheetham.hul.harvard.edu:8992/F/?func=item-hold-
request&doc_library=HVD50&adm_doc_number=012353769&item_sequence=0000
10
5. Setting up JBOSS server
1. Start / stop server via util/w
(Server does not appear in util/w/1 (Monitor
servers)
2. Type jlog at prompt to see log
3. Update global.properties file with ports /
server names
4. $alephe_root/dlf_eng/dlf-global.tng
(we use to delete private data we don’t need)
5. open port 189#
6. Design
Aquabrowser
Link to local app (with ADM + Item Seq. #)
PIN System
Authentication
Local app
Retrieve Patron ID via call to X-server
REST Check Check for Show Request Send
Borrower Patron Options and Request
API Expiration Blocks Instructions
Date
14. Patron Blocks: Aleph OPAC
• Patron is
presented with a
confirmation
screen.
• When they go to
library to get
book they’ll be
told they can’t
check it out due
to blocks.
15. Patron Blocks: Aleph OPAC
The only
place they
would see a
block is in
their My
Account
page
27. About the local app
(Developer: Michael Vandermillen, Harvard Library)
• Resides on separate server
• Tomcat application, running behind Apache
• Groovy and Grails web app framework (Java
platform)
28. Future Plans ?
• Create new interface for all My Account info?
• Create an interface that also includes other
patron requests, so users can see all library
activity in one place
(ILL, Borrow Direct, EDD, Aeon)
29. Questions?
See also:
• Ex Libris Commons
• “Aleph Restful APIs “ Powerpoint on Doc Center
Corinna Baksik
Systems Librarian, Office for Information Systems
Harvard Library
Email: corinna_baksik@harvard.edu
Skype: corinna_baksik