Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project

DSpace ClientUI built on RESTful API

Student

Vibhaj Rajan

Mentors

Technologies

DSpace REST
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0eafdcca76ca74ee-6873ae64-463d4773-85c1a6b6-636464625814b12ff7d3e86b"><ac:plain-text-body><![CDATA[JavaScript [Ext JS]

]]></ac:plain-text-body></ac:structured-macro>

Location for project

(not received yet)

...

  1. Obtain access to :
    • (tick) Wiki
    • Project repository
  2. (tick) Download, build and install local DSpace instance
  3. (tick) Download, build and install DSpace REST module
  4. (tick) Test and verify the installation
  5. (tick) Go through the functionality of DSpace and DSpace REST API
  6. (tick) Compare possible JavaScript UI frameworks -- Ext JS preferred
  7. Get familiar with REST API by adding and manipulating new collections, communities, items and bitstreams and generating statistics
Note

Mark: I would like to see a bit more dialog with Bojan concerning the REST API contracts and migration to Spring, mainly, are we happy with these API contracts and using them for the students project, or do we need to consider some possible changes int he API to adopt to using Spring REST instead of Entity Broker. And if so, is there a timeline for providing those changes in scope of the 1.8 release?

May 25 - June 15

  1. Design architecture for client run EntityBrowser supported by RESTful (JSON) services
  2. Implement first working version

...