...
- Performance issues during browsing bigger datasets. This is generally related to DSpace API. I have reported this problem and proposed solution at http://jira.dspace.org/jira/browse/DS-659. However as I am not sure whether it will be accepted and included in the upcoming release I will change the code and translate some functions used from DSpace API to DSpace REST API. This way some handling will be done directly at REST API level. Consequently some additional features related to sorting/ordering will be available.
- Multiple loops in listing Collections and some other entities. This issue is resolved as of end September. Additionally, option to fine-grain details level of the output is implemented (three levels).
- HTTP Basic Auth - this is easily to implement and will be done shortly
- Some Authorization related issues: the authorization handling is done on the level of DSpace API. However some functions translated to REST API are not directly available to users and thus do not provide Authorization mechanisms. In order to prevent misuse etc. this gap should be filled at REST API level.
- Not finished end-points. Working on them.
- Testing. Testing. I also need cooperation of you potential users. I need repository for testing containing at least several hundreds of items. If you can provide me with that please contact me via email.
- DSpace 1.5 and older versions support - planned to be implemented at the end of initial public release.
Recent changes
- June 10: XML input/digestion change, based on the input from Dhaivat Dave
- June 6: Added support for logo in communities and collections (issue reported by Vibhaj Rayan and Hayden Young)
- June 1: Applied Peter Dietz's patches (https://gist.github.com/952058) and pom.xml improvements discussed bellow on this page; fixed collection/items display reported by Hayden Young
...