Page tree
Skip to end of metadata
Go to start of metadata

A number of institutions are interested in collaborating on the creation of a REST API for DSpace, and a library of client code/apps. This page will serve as a place to facilitate that collaboration, and to make the work transparent to the DSpace developer community.

Interested Participants (if you are interested in participating in this collaboration, add your name here, and contact one of us to let us know):

Google Group:!forum/dspace-rest

Meeting notes from the DSpace Futures discussion: DSpace Futures REST API Meeting Notes 


Use Cases

  • JavaScript widgets for researcher pages
  • Integrate DSpace data into other systems
    • To provide statistics / analysis. Data visualization / Data mining.
    • Queryable
    • Integrate with Drupal, Omeka
  • External user interfaces
    • in any language (PHP, Ruby, Python, Java, ...)
    • web UI or desktop UI
    • mobile applications
    • administrative UI or a discovery UI (although for pure discovery UI, consider using Solr directly, see e.g. SkylightUI)
    • interfaces for specialized collections

Technical Feedback

  • Look up Item by Handle, in addition to ID.
  • It should be able to scale well, (implement caching)
  • Some of the business logic being un-earthed could make other UI's get modified. 
    • i.e. OAI / RSS feeds to use REST API for certain parts
    • lots of business logic should go somewhere DRY

Proof of Concept

Production Level Examples

  • Monash University Pharmacy Faculty Saber project utilising Wijiti REST API version and Joomla with JSpace connector.

  • No labels

1 Comment

  1. It will be interesting to see what results if we arrive at a REST API from this direction. Instead of simply picking an existing REST module that has been built to reflect the DSpace data models and schemas, what if we describe 2-3 high value web widgets and determine what the "javascript-widget-developer-friendly" REST API should look like?