This document discusses using the Aleph REST API to support item requests from the separate Aquabrowser discovery system. It allows for a seamless user experience and better statistics. The setup involves configuring the JBOSS server and ports. Authentication uses the Harvard PIN system. REST calls retrieve patron information and check statuses and blocks. Users can request holds through a similar interface in both systems. Future plans may include consolidating patron account information and requests.

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

3. Why? #2: Better stats

4. Why? #3: Better mobile experience

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

7. Aquabrowser interface
http://hollisservices.lib.harvard.edu/itemrequest?bibid=HVD01012809860
&itemid=HVD50012353769000010

8. Authentication
• Harvard PIN Server
• Harvard ID  Aleph Patron ID
http://cheetham.hul.harvard.edu:8992/
X?op=bor-by-key
&bor_id={HUID}&verification={HUID}&library=hvd50
&user_name={clientID}&user_password={clientPW}

9. REST call for patron info
http://cheetham.hul.harvard.edu:1892/rest-dlf/patron/
{patronID}/patronInformation/address

10. Expired ID: Aleph OPAC

11. Expired ID: Aquabrowser

12. REST call:
http://cheetham.hul.harvard.edu:1892/rest-dlf/patron/
{patronID}/patronStatus/registration

13. Patron Blocks: Aleph OPAC

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

16. Patron Block: Aquabrowser

17. Use REST to check for block
http://cheetham.hul.harvard.edu:1892/rest-dlf/patron/
{patronID}/patronStatus/blocks

18. Hold Request: Aleph OPAC

19. Hold Request: Aquabrowser

20. Hold Request
http://cheetham.hul.harvard.edu:1892/rest-dlf/patron/
{patronID}/record/HVD01{bib}/items/HVD50{ADM}{SEQ}/hold

21. Use XSL to modify what Aleph returns
Example: Item on loan with a waitlist

22. Apply XSLT to XML from Aleph API
Notes
returned
by Aleph
API
XSLT
applied
to Notes

23. On Loan until 12/31/99

24. Send Request
http://cheetham.hul.harvard.edu:1892/restdlf/patron/
{patronID}/record/HVD01{bib}/items/HVD50{ADM}{SEQ}/hold
post_xml=
<hold-request-parameters>
<pickup-location>
{pickup-location@code}
</pickup-location>
<note-1><note-1>
<note-2></note-2>
</hold-request-parameters>

25. Success

26. Mobile stylesheet
http://hollisservices.lib.harvard.edu/hollisservices/itemrequest?bibid=HVD01012809860&
itemid=HVD50007605221000010

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