Versions Compared

Key

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

...

  1. Stylesheets (CSS)
  2. Layout
  3. Themes
  4. Internationalization

Project Timeline

(tick)

Ready

(thumbs up)

In Progress

Before May 24

  1. Obtain access to :
    • (tick) Wiki
    • (tick) 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?

Vibhaj: Confirmed that the possible migration shall not affect the REST interface and hence RestClient project.

May 25 - June 15

  1. (thumbs up) Get familiar with REST API
    1. collections, communities, items and bitstreams
      • create
      • (tick) view
      • edit
      • delete
    2. users and groups
      • (tick) view
    3. generating statistics
  2. (thumbs up) Decide the JavaScript Library to be used by discussing with the DSpace community from among the following
    1. Ext JS (preferred)
    2. JxLib
    3. UIZE
    4. MochaUI
  3. Design architecture for client run ServiceClient supported by RESTful (JSON) services
    • (thumbs up) Implement in Ext JS
  4. Design generic extensions to Views, LoadersRenderers, Templates and Renderers Modules for ServiceClient
    • (thumbs up) Implement in Ext JS
  5. Plan these extensions for RestClient

...