Page History

...

1. Transaction use cases
   1. Islandora CLAW update
      1. https://github.com/Islandora-CLAW/CLAW/wiki/January-27%2C-2016#minutes
      2. Islandora CLAW Transaction Use Case
      3. Consistency requirements nailed down.
      4. Isolation is still an outstanding question, polling community for consensus.
   2. Events for transaction end
      1. Are we able to emit events when a transaction ends?
         1. If we treat transactions as resources, we can emit messages on transaction begin and transaction completion, be it a 'Commit' or 'Rollback' event.  Easy to support as long as we tie it to the transaction as a resource.  Need to present transactions/operations as a first class resource.
         2. It may be recommended to use the User Agent mechanism to tag transaction events. This would allow tracking of independent transactions and identify which messages result from which transactions.
2. 4.5.0 release status
   
   1. Finished!  Esmé Cowles and Nick Ruest has wrapped up their work, awaiting Andrew Woods to write up and announce.
3. Question around deployable artifacts in related libraries
   1. fcrepo-camel-webapp 4.4.0 deprecated war file usage in favour of OSGi deploy via Karaf
   2. We should document that automated work should rely on Maven as the canonical source of artifacts to avoid the issue of needing to place copies in many places.
4. Component Compatibility Matrix
   1. Do we need to refactor this?  Is there a way we can highlight a components compatibility in a clear fashion?
5. Open Repositories 2016 proposals
   1. Proposals are due Feb 8th
   2. Discussion around potential proposals
   3. Could be nice to curate the list of talks that are of interest to the Fedora community once the schedule is published.
6. Status of "in-flight" tickets

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1830

       - Jared Whiklo did some debugging, and is wondering if there is an easy way to go backwords from a version to the base resource without getting into the implementation.  – Is there a triple?  Is there a context for version triples?  – If these are RDF resources are they present right there?  If they are binary resources, they should be in the header and if they aren't they should be.
      1. Aaron - class called VersionsRDFContext in the modeshape implementation that may be the place to start 
   2.   "Body not JSON-LD as requested" email thread
      1. Should this be filed as a Bug, and an Improvement, or just wait for the Improvement to be completed to resolve the bug.
      2. Ticket(s) will be filed.

         1. Jira
            server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1878

         2. Jira
            server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-18781879

      3. What happens when you ask for a serialization that Fedora does not support?  Returns a supported serialization format and sets the header accordingly. Perhaps gives more information in a 299 header.

...