Re: [Dspace-tech] [Dspace-devel] DSpace 5: Dates and Features

2014-10-06 Thread Peter Dietz 
Reminder to all:

DSpace 5 New Feature Pull Request Deadline Day is TODAY!!

So, if you are planning to contribute something for DSpace 5, you will need
to stay up all night and code, code, code, and then submit your pull
request. We would prefer that features be mostly complete. Over the review
process, expect that there might be a few bug-fixes or final improvements
to make based on testing and suggestions by others.


Also, to Hayden. There is a CRUD REST PR made by Czech Technical University
in Prague CZ.
https://github.com/DSpace/DSpace/pull/666

I'm currently evaluating that. It appears that it has some auth scheme
where your consumer makes a request to /login, passing username/password,
and receives a token in response. Further communication requires that
token. It appears to require SSL.




Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

On Thu, Sep 11, 2014 at 10:44 AM, Peter Dietz  wrote:

> Hi Hayden,
>
> Thanks for your interest in DSpace 4+ REST (Jersey).
>
> The readme has info on the endpoints:
> https://github.com/DSpace/DSpace/tree/master/dspace-rest
>
> Is it compatible, to go from a previous REST API, to the current Jersey
> API?  It depends.
> Play! Framework client (demo):
> http://dspace-rest-client-play.herokuapp.com/
> Ruby on Rails client (demo): http://dspace-rails.herokuapp.com/
>
> It might not have all the information your looking for, especially if you
> are expecting to receive restricted content, or to do CRUD actions. Recent
> development on the REST/Jersey api have been to work on search, and viewing
> statistics (thanks Anja). I expect to have that cleaned up, and merged in,
> before DSpace 5 release.
>
> Kim Shepherd and I have been discussing authentication. I'm in favor of
> using OAUTH1. But essentially, I don't want to add any CRUD endpoints,
> until we have authentication solidly figured out. i.e. It might work for
> one institution to hack something like ?epersonID=1 to authenticate within
> your firewall, but another institution might miss on some security
> concerns. So, I'm thinking its best to have an authentication stack that
> works great when complemented with SSL, but, can still securely transfer
> auth tokens without ssl.
>
> At Open Repository 2014, I heard that there were some groups that had
> added additional CRUD endpoints, to allow them to integrate their
> LMS/gradebook with DSpace REST (jersey), but skipped auth, since it was
> within their firewall. It would be interesting to hear from that group, and
> or see some code.
>
> So yes, ideally I would love to have proper auth, and full CRUD endpoints
> in DSpace REST in time for DSpace 5. I personally have a lot of my plate,
> that I don't see myself accomplishing that alone.
>
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com
> p: 740-599-5005 x809
>
> On Thu, Sep 11, 2014 at 9:54 AM, Hayden Young 
> wrote:
>
>>  What is the current situation on the Jersey REST API bundled with DSpace
>> 5 in regards to the additional endpoints documented at
>> https://wiki.duraspace.org/display/DSPACE/REST+API.
>>
>> We are attempting to support the Jersey REST API for existing production
>> DSpace instances by using the documented endpoints, in particular bitstream
>> retrieval and writing back to the DSpace archive.
>>
>> Additionally, what is the current status on alternative user
>> authentication mechanisms in Jersey REST? The documentation discusses
>> username/password being passed as part of the url although I believe there
>> was discussion around other authentication functions being implemented.
>>
>> Cheers
>>
>>
>> Hayden
>> email. hay...@knowledgearc.com
>> web. http://knowledgearc.com, http://knowledgearc.org
>>
>>
>> On 10/09/14 23:10, Peter Dietz wrote:
>>
>>  Greetings from the DSpace 5.0 Release Team!
>>
>> We have another exciting release of DSpace in the works that has been
>> growing steadily over the past few months. Many contributors have been busy
>> adding new features and improvements to DSpace. This speaks volumes to the
>> maturity, stability, and future of DSpace, that as the software project
>> approaches its 12th year, we're still going strong. Read on for ways to
>> help contribute, and find out the new features in DSpace 5.
>>
>> The full release schedule is here:
>>
>> https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.0+Status
>>
>> October 6: Deadline for Feature Pull Requests
>>
>> In plain English, October 6 is the last day you may submit new features
>> for acceptance into DSpace 5.0. If you are working on a new feature for
>> DSpace, we urge you to prepare a Pull Request now. Getting your work
>> visible early as a Pull Request allows others to review, and help steer
>> your contribution to inclusion in the next release.
>>
>> Here’s how:
>>
>> https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines
>> Other Important Dates:
>>
>> October 31  5.beta-1 - Release Can

Re: [Dspace-tech] [Dspace-devel] DSpace 5: Dates and Features

2014-09-11 Thread Peter Dietz 
Hi Hayden,

Thanks for your interest in DSpace 4+ REST (Jersey).

The readme has info on the endpoints:
https://github.com/DSpace/DSpace/tree/master/dspace-rest

Is it compatible, to go from a previous REST API, to the current Jersey
API?  It depends.
Play! Framework client (demo): http://dspace-rest-client-play.herokuapp.com/
Ruby on Rails client (demo): http://dspace-rails.herokuapp.com/

It might not have all the information your looking for, especially if you
are expecting to receive restricted content, or to do CRUD actions. Recent
development on the REST/Jersey api have been to work on search, and viewing
statistics (thanks Anja). I expect to have that cleaned up, and merged in,
before DSpace 5 release.

Kim Shepherd and I have been discussing authentication. I'm in favor of
using OAUTH1. But essentially, I don't want to add any CRUD endpoints,
until we have authentication solidly figured out. i.e. It might work for
one institution to hack something like ?epersonID=1 to authenticate within
your firewall, but another institution might miss on some security
concerns. So, I'm thinking its best to have an authentication stack that
works great when complemented with SSL, but, can still securely transfer
auth tokens without ssl.

At Open Repository 2014, I heard that there were some groups that had added
additional CRUD endpoints, to allow them to integrate their LMS/gradebook
with DSpace REST (jersey), but skipped auth, since it was within their
firewall. It would be interesting to hear from that group, and or see some
code.

So yes, ideally I would love to have proper auth, and full CRUD endpoints
in DSpace REST in time for DSpace 5. I personally have a lot of my plate,
that I don't see myself accomplishing that alone.



Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

On Thu, Sep 11, 2014 at 9:54 AM, Hayden Young 
wrote:

>  What is the current situation on the Jersey REST API bundled with DSpace
> 5 in regards to the additional endpoints documented at
> https://wiki.duraspace.org/display/DSPACE/REST+API.
>
> We are attempting to support the Jersey REST API for existing production
> DSpace instances by using the documented endpoints, in particular bitstream
> retrieval and writing back to the DSpace archive.
>
> Additionally, what is the current status on alternative user
> authentication mechanisms in Jersey REST? The documentation discusses
> username/password being passed as part of the url although I believe there
> was discussion around other authentication functions being implemented.
>
> Cheers
>
>
> Hayden
> email. hay...@knowledgearc.com
> web. http://knowledgearc.com, http://knowledgearc.org
>
>
> On 10/09/14 23:10, Peter Dietz wrote:
>
>  Greetings from the DSpace 5.0 Release Team!
>
> We have another exciting release of DSpace in the works that has been
> growing steadily over the past few months. Many contributors have been busy
> adding new features and improvements to DSpace. This speaks volumes to the
> maturity, stability, and future of DSpace, that as the software project
> approaches its 12th year, we're still going strong. Read on for ways to
> help contribute, and find out the new features in DSpace 5.
>
> The full release schedule is here:
>
> https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.0+Status
>
> October 6: Deadline for Feature Pull Requests
>
> In plain English, October 6 is the last day you may submit new features
> for acceptance into DSpace 5.0. If you are working on a new feature for
> DSpace, we urge you to prepare a Pull Request now. Getting your work
> visible early as a Pull Request allows others to review, and help steer
> your contribution to inclusion in the next release.
>
> Here’s how:
>
> https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines
> Other Important Dates:
>
> October 31  5.beta-1 - Release Candidate 1
>
> November 03-14 Testathon (mark your calendar)
>
> November 20  5.beta-2 - Release Candidate 2
>
> December (mid) DSpace 5.0 Release
>
> Of course, this also means we have a large pile of pull requests which
> need review, and other features that have been contributed but should still
> receive plenty of testing. We’d like to take a moment to call a few of
> those out, as they represent features we know are important to the
> community. If any of these features “speak to you” please consider pitching
> in with the review and testing work.
>
> The complete list of pull requests is here:
>
> https://github.com/dspace/dspace/pulls
>
> Six great new features in DSpace 5
>
> We couldn't choose just 5 great new features in DSpace 5, here's six great
> features you should take a look at:
>
> DS-1461/DSPR#591 Batch Import Items from ZIP through UI
>
> https://github.com/dspace/dspace/pull/591
>
> DS-1582/DSPR#629 Metadata for all DSpace objects (not just items)
>
> https://github.com/dspace/dspace/pull/629
>
> DS-2061/DSPR#568 Linked Open Data for DSpace
>
> https://github.com/dsp

Re: [Dspace-tech] [Dspace-devel] DSpace 5: Dates and Features

2014-09-11 Thread Hayden Young 
What is the current situation on the Jersey REST API bundled with DSpace 
5 in regards to the additional endpoints documented at 
https://wiki.duraspace.org/display/DSPACE/REST+API.


We are attempting to support the Jersey REST API for existing production 
DSpace instances by using the documented endpoints, in particular 
bitstream retrieval and writing back to the DSpace archive.


Additionally, what is the current status on alternative user 
authentication mechanisms in Jersey REST? The documentation discusses 
username/password being passed as part of the url although I believe 
there was discussion around other authentication functions being 
implemented.


Cheers


Hayden
email. hay...@knowledgearc.com
web. http://knowledgearc.com, http://knowledgearc.org

On 10/09/14 23:10, Peter Dietz wrote:


Greetings from the DSpace 5.0 Release Team!


We have another exciting release of DSpace in the works that has been 
growing steadily over the past few months. Many contributors have been 
busy adding new features and improvements to DSpace. This speaks 
volumes to the maturity, stability, and future of DSpace, that as the 
software project approaches its 12th year, we're still going strong. 
Read on for ways to help contribute, and find out the new features in 
DSpace 5.



The full release schedule is here:

https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.0+Status


October 6: Deadline for Feature Pull Requests

In plain English, October 6 is the last day you may submit new 
features for acceptance into DSpace 5.0. If you are working on a new 
feature for DSpace, we urge you to prepare a Pull Request now. Getting 
your work visible early as a Pull Request allows others to review, and 
help steer your contribution to inclusion in the next release.



Here’s how:

https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines


Other Important Dates:

October 31 5.beta-1 - Release Candidate 1

November 03-14 Testathon (mark your calendar)

November 20 5.beta-2 - Release Candidate 2

December (mid)DSpace 5.0 Release


Of course, this also means we have a large pile of pull requests which 
need review, and other features that have been contributed but should 
still receive plenty of testing. We’d like to take a moment to call a 
few of those out, as they represent features we know are important to 
the community. If any of these features “speak to you” please consider 
pitching in with the review and testing work.



The complete list of pull requests is here:

https://github.com/dspace/dspace/pulls


Six great new features in DSpace 5

We couldn't choose just 5 great new features in DSpace 5, here's six 
great features you should take a look at:



DS-1461/DSPR#591 Batch Import Items from ZIP through UI

https://github.com/dspace/dspace/pull/591


DS-1582/DSPR#629 Metadata for all DSpace objects (not just items)

https://github.com/dspace/dspace/pull/629


DS-2061/DSPR#568 Linked Open Data for DSpace

https://github.com/dspace/dspace/pull/568


DS-2049/PR#612 ORCID Integration

https://github.com/DSpace/DSpace/pull/612


DS-2052/PR#587 Mirage2 Responsive Theme

https://github.com/DSpace/DSpace/pull/587


DS-2108/PR#615 Google Analytics Statistics viewer (page views and 
downloads)


https://github.com/DSpace/DSpace/pull/615


There are also many more great proposals for DSpace 5. The status page 
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.0+Statushas 
a full listing of things that we hope would make it in, contributions 
welcome. Lastly, we are still looking for more people to join the 
Release Team. Responsibilities include attending weekly developer 
meetings, reviewing pull requests, and ensuring requests get proper 
feedback and testing.


Peter Dietz
Longsight
www.longsight.com 
pe...@longsight.com 
p: 740-599-5005 x809


--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk


___
Dspace-devel mailing list
dspace-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel


--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette