1. Enhancing life-long learning, teaching and research through information
resources and services
February 06, 2013
1

2. Putting the Aspire APIs to work
Dr Richard Cross, Resource Discovery and Innovation Team Manager
Libraries and Learning Resources
Talis Aspire User Group | Developer Unconference | 6 February 2013
February 06, 2013
2

3. Agenda
• Aspire List linking API
• Item linking API
• Bookmarklet API
• Aspire widgets
• Issues affecting API development
• APIs – possible future developments
February 06, 2013
3

4. Talis Aspire – list linking API
February 06, 2013
4

5. Aspire linking from the VLE
• Uses the Aspire list-linking API for dynamic deep-linking
February 06, 2013
5

6. Next version…
• In development:
displaying list content
directly within the Virtual
Learning Environment
• Calling .csv version of the
file
• Fastest and lightest of the
options
• Need still to review
grouping, priority,
pagination and
presentation options

7. • In development: tracking gaps in dynamic module provision

8. Talis Aspire – item linking API
February 06, 2013
8

9. Resource List item checker – mash-up
• Relic – Resource List Item Checker (using an Aspire API)
• http://www.urko.org.uk/library/rlms/relic/index.php?
type=doi&search=10.1177/0309132509105004
February 06, 2013
9

10. Talis Aspire – bookmarklet API
February 06, 2013
10

11. Passing OpenURL metadata to Aspire
• LLR developed an SFX-
RLMS bookmarking
service
• Uses the Bookmarking
API for Aspire (now
supports OpenURL)
• Enables any OpenURL
supporting service to
become a bookmarking
source
• Any metadata received by SFX can be sent to Aspire
• Several other customers have deployed this target service
February 06, 2013
11

12. Talis Aspire – widgets
February 06, 2013
12

13. ‘Suppress Availability Message’ widget
13

14. ‘Suppress Availability Message’ widget
February 06, 2013
14

15. ‘Not current time period’ warning on list edit
• Developed by Talis in response to post-Rollover scenario posed by
NTU
• Not customer coded! http://screencast.com/t/nDxTEpOfEu7
February 06, 2013
15

16. Talis Aspire – API issues
February 06, 2013
16

17. Issues affecting API development
Aspire side Local
• Limitations in the • Existence of lengthy and
functionality of the complex resource lists
existing APIs • Learning curve on RDF
• Absence of APIs outside • Lack of development time
the list / item context and resource
• Linked data structure can
require multiple data calls
to return data from RDF
triple store
• One-version-for-all API
configuration
February 06, 2013

18. Talis Aspire – APIs: possible future
developments
February 06, 2013
18

19. Future Aspire API developments
• Extension of parameters passable in existing APIs
• Extension of new APIs to new areas of functionality and data
• Particular focus on end user interface construction by API
• Extension to collaborative customer-to-customer framework
• Agreement on new method for prioritising possible API
enhancements
February 06, 2013
19

20. Comments?
Nottingham Trent University: Resource Lists
http://resourcelists.ntu.ac.uk
Richard Cross
Resource Discovery and Innovation Team Manager
Libraries and Learning Resources, Nottingham Trent University
richard.cross@ntu.ac.uk
February 06, 2013
20