Hi
Yes, as Bojan notes, we are actively working on what we now call a 'fast
read api' (for lack of a better term) based on Bojan's DSpace REST
API work: Thanks Bojan! Major improvements include speed and pagination.
We haven't touched the code for the write side of the DSpace REST API but
we have removed all endpoints we don't need; including the write side
endpoints. So to use our work re-integration will be needed.
We will document our new/changed endpoints when we get a moment to breathe.
Regards
mark
Thanks to Jorum for funding this work
And thanks Tim for the update yesterday on the Sakai bus etc
On Wed, Feb 29, 2012 at 3:05 PM, Mark van Harmelen <m...@cs.man.ac.uk>wrote:
> Hi
>
> Yes, as Bojan notes, we are actively working on what we now call a 'fast
> read api' (for lack of a better term) based on Bojan's DSpace REST
> API work: Thanks Bojan! Major improvements include speed and pagination.
>
> We haven't touched the code for the write side of the DSpace REST API but
> we have removed all endpoints we don't need; including the write side
> endpoints. So to use our work re-integration will be needed.
>
> We will document our new/changed endpoints when we get a moment to breathe.
>
> Regards
> mark
>
> With thanks to JISC and Jorum for funding our work,
> and thanks to Tim for yesterday's update about the API discussions and the
> Sakai bus thoughts .
>
>
> On Wed, Feb 29, 2012 at 12:27 AM, Bojan Suzic (Commented) (DuraSpace JIRA)
> <no-re...@duraspace.org> wrote:
>
>>
>> [
>> https://jira.duraspace.org/browse/DS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24319#comment-24319]
>>
>> Bojan Suzic commented on DS-1109:
>> ---------------------------------
>>
>> In the meantime I took a look at the code. It seems that Hedtek is
>> actively reworking/refactoring, they pushed commits generally everyday. The
>> contribution improved the code quality significantly. I would suggest to
>> wait for their contribution to be complete.
>> Also I noticed an ongoing discussion at Developers Virtual Summits and
>> there are some other proposals related to REST API. Probably it would be a
>> good idea to wait a few days for a general agreement on that side.
>>
>> > Incorporate Hedtek Improvements to REST-API
>> > -------------------------------------------
>> >
>> > Key: DS-1109
>> > URL: https://jira.duraspace.org/browse/DS-1109
>> > Project: DSpace
>> > Issue Type: Code Task
>> > Components: REST API (experimental)
>> > Reporter: Peter Dietz
>> >
>> > A group of developers at Hedtek contacted the mailing list making us
>> aware of their improvements they have made to the REST-API. Their
>> improvements include tests, and other bug fixes to improve stability of the
>> REST api. Their improvements have been made to their Git repository, which
>> isn't quite a clone of the svn project for the dspace rest project.
>> > My / PeterDietz's question...
>> > Shall the dspace-rest project be moved to Github to make it easier for
>> community contributions? Including to merge in these improvements from
>> Hedtek. DSpace is potentially moving all code to GitHub, and if so, it
>> would make sense for modules to move there as well anyways. Tim has
>> recently moved the dspace-replicate module code there.
>> > If so, then I have no problem stitching together the history of our
>> code history from SVN, and their disjoint work in their github. From then
>> on, hedtek can fork the future consolidated git repository, and continue
>> development as they had been. The next benefit is that DSpace can then
>> merge in their improvements much easier. Merge, cherry-pick, or
>> Pull-Request.
>> > Subject: [Dspace-devel] Testing the DSpace REST API
>> > From: Mark van Harmelen
>> > Hi everyone
>> > Through Jorum [1] we've been doing some JISC [2] funded work on testing
>> the DSpace REST API. To date we have tested most of the 'read' side of the
>> API, later we may be moving onto the 'write' side.
>> > You can find out what we have done so far at
>> http://hedtek.com/2011/dspace-rest-api-testing/ including the URL of
>> our github repo (that contains slightly modified code for the API and our
>> tests).
>> > What we have found out about the API so far appears in the sole/first
>> comment on the blog post.
>> > I am the sole Hedtek person on this list, if you want to ask questions
>> or comment, I will pick them up, but even better please to cc them to
>> hed...@googlegroups.com
>> > Thanks/regards
>> > mark
>> > [1] http://www.jorum.ac.uk/
>> > [2] http://www.jisc.ac.uk/
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA
>> administrators:
>> https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Dspace-devel mailing list
>> Dspace-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>>
>
>
--
Dr Mark van Harmelen
Hedtek Ltd
cell/mobile +44 7830 212 464 / 07830 212 464
skype markvanharmelen
web http://hedtek.com
Hedtek Ltd is a limited company registered in England and Wales, Co Reg No
6300001
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
