Active Fedora

I've got a partial implementation of this lying around somewhere.

• gather stories, especially about how to handle/communicate exceptions - 0.5d
• implement - 1.5d
• test - 1d

Starter Spec for this feature:

http://bitbucket.org/mediashelf/active_fedora/src/tip/spec/unit/datastream_concurrency_spec.rb

1. you've submitted a last_modified_date with your update request
2. the submitted date is older than the datastream's last modified date

ActiveFedora will be updated to submit that last_modified_date with the update requests and handle 409 errors gracefully (raise a Net:HTTP 409 error).

In order to minimize the window for conflicts we will implement part of this as an improvement to Fedora rather than dealing with it on the Ruby side.

I've added the corresponding issue to Fedora's tracker as FCREPO-689.

I also introduced the issue during today's Fedora committers call, and we've agreed to include this work in the upcoming Fedora 3.4 release.

started stubbing out the datastream methods (in the REST API) to support lastModified. Created AbstractParam and DateTimeParam classes to handle lastModifiedDate QueryParams.

Originally intended to implement support in Fedora's SOAP API (since the REST methods delegate to SOAP). However, after locally implementing this for the SOAP modifyDatastream methods, I'm backing it out. Even though it's only a parameter change, it touches a lot of classes, schemas, config, tests etc. and although our tests are working we'd have to sink a lot more time into testing before I'd be confident we weren't introducing any regressions into 3.4. So as decided on the Fedora committers call yesterday, this feature will only be available in the REST API for 3.4

FYI, this is done in Fedora trunk, as of r8590 (http://fedora-commons.svn.sourceforge.net/fedora-commons/?rev=8590&view=rev).

ActiveFedora needs to be updated to take advantage of the addition of the lastModifiedDate query parameter on modifyDatastream and modifyObject