Summary
Project |
DSpace ClientUI built on RESTful API |
Student |
|
Mentors |
|
Technologies |
DSpace REST |
Proposal |
|
Location for project |
Requirements
- Client run interface
- Attractive look and feel
- Easy to customize
Functional Specifications
Features to be supported
- Respository Browsing
- Repository Manipulation
- Content Searching
- Statistics
- Administration
Customizations to be supported
- Stylesheets (CSS)
- Layout
- Themes
- Internationalization
Project Timeline
Before May 24
- Obtain access to :
- Wiki
- Project repository
- Download, build and install local DSpace instance
- Download, build and install DSpace REST module
- Test and verify the installation
- Go through the functionality of DSpace and DSpace REST API
- Compare possible JavaScript UI frameworks -- Ext JS preferred
- Get familiar with REST API by adding and manipulating new collections, communities, items and bitstreams and generating statistics
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
- Design architecture for client run EntityBrowser supported by RESTful (JSON) services
- Implement first working version
June 15 - June 30
- Configure EntityBrowser to provide support for :
- Respository Browsing and Manipulation
- Communities
- Collections
- Items
- Bitstreams
- Content Searching
- Statistics
- Reports
- Graphs and visualization
- Administration
- Groups
- Users
- Respository Browsing and Manipulation
July 01 - July 11
- Testing
- Partial documentation
July 12 - July 18
- GSoC mid term evaluations