Page History

...

1. Announcements

2. Sprint 2 Strategy and Goals
   1. Release candidate
      1. Vagrant
      2. Camel toolbox 
      3. java client

3. Open questions: 

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

      1. 4 Integration tests in FedoraLdpIT are breaking due to a 500 Error.  

      2. The cause of the 500 is

         Code Block
         javax.jcr.RepositoryException: The session with an ID of '060742fc6' has been closed and can no longer be used.

         
         

      3. It appears to be an OSX 10.13.x issue :  Jared Whiklo, Peter Eichman, and Danny Bernstein have reproduced.
         
         1. Danny Bernstein confirmed It was not a problem for OSX 10.10.5
         2. Any ideas of how to solve it? 
      4. If we can't resolve it,  what are our options? 
         1. Leave the tests in place - and document the problem in the README.
         2. @Ignore  the tests until we can sort out the issue .or it sorts itself out (OS fix)
         3. ?
   2. Data URIs in the constrainedBy link header
      1. https://github.com/fcrepo4/fcrepo4/commit/750426101de9330cafaa88838a3d694d1ef69580#diff-14e2f9192b9abd40557a43f9342f4481R44
      2. Proposal:  Remove and use standard URIs instead like we do with all other constraints.
   3. Prefer headers on Mementos:  https://github.com/fcrepo4/fcrepo4/pull/1420 
      1. Question1:  Should the original resource return  <> a ldp:Container and <> a ldp:RDFSource  when omitting server managed triples (currently these are being omitted in OriginalResource but not the Memento)
      2. Question2: How should fedora respond to requests to Prefer omit
         1. What would a use case for omitting server managed triples in memento?
         2. Proposal 1:  Mementos should behave like the original resource
            1. 1. Rationale?
               2. Action:  based on the answer to Question1 either omit the ldp types from memento or add them to the original resource response
         3. Proposal 2:  Mementos should not respond to Prefer omit
            1. 1. Rationale? 
         4. Proposal 3: ?
   4. All AuthZ tests assume literal agent values

4. <your agenda item here>

5. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

6. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

7. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

...