Project |
DSpace ClientUI built on RESTful API |
Student |
|
Mentors |
|
Technologies |
DSpace REST |
Proposal |
|
Repository |
|
Demo |
http://ec2-107-20-35-121.compute-1.amazonaws.com:8080/restclient/ |
Notes |
DSpace REST |
Built on the DSpace REST API developed as GSoC project in 2009-10 |
FireSpark |
Interface powered by FireSpark - JavaScript Service Computing Platform - which |
RESTClient Extensions |
Services and Workflows built for RESTClient using FireSpark for providing core |
jQuery Templates |
Client side processing supported by flexible templates written in JavaScript |
CKEditor |
HTML Rich Text Editor supported for easier text input during repository |
|
Ready |
|
Base done, Improvement phase |
|
In Progress |
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. |
(/) Decide the JavaScript Library to be used by discussing with the DSpace community: *jQuery* \[decided by community\] |