...

Agenda

1. Announcements 
   1. Sprint 2
   2. ?
2. Proposed PersistentStorageSession interface changes changes 
   1. What is wrong with the current approach?
      1. Having two separate layers responsible for creating FedoraResources seems confusing.
      2. Passing a mutable FedoraResource to the persistenceStorage for create and update could be confusing.
   2. What would improve things?
      1. immutable FedoraResource
         1. fedora resource is a view of the resource on disk - doesn't provide all details unless they were requested
         2. implementations are responsible for throwing exceptions when  particular details (such as a binary stream or the server managed triples) are not provided by the view. 
   3. For reference:  proposed additions to the persistence API
3. Fedora 6 and OCFL: managing active updates
   1. What are we planning to implement?
   2. How do we want to implement it?
4. Thinking about object stores in the cloud (S3, etc) 
5. <add topics here>

Tickets

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. 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

   
   

3. 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

   
   

4. 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

   
   

...