...

Attendees

Part 1: 

1. Danny Bernstein 
2. Andrew Woods
3. Peter Winckles
4. Jared Whiklo 
5. Bethany Seeger 
6. Youn Noh 
7. Thomas Bernhart 
8. Daniel Lamb  
9. Aaron Birkland
10. Andrew Woods  
11. Ben Pennell 
12. Rosie Le Faive
13. Dan Field
14. Ben Cail
15. Mohamed Mohideen Abdul Rasheed
16. Joseph Rhoads
17. David Wilcox
18. Peter Eichman

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?
   3. Consider multi-object transactions
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

   
   

Notes

Fedora 6 and OCFL: managing active updates

1. Islandoracon feedback
   • How will objects-in-motion be handled
   • Suggestion:
     • Keep everything in OCFL (mutable head)
     • Concern about complexity of having separate storage approaches
     • Interest in Fedora6 transparency, rebuildability, preservation
       • Complexity may not be worth it
   • Noting, Fedora is optional in Islandora
2. Implementation of a mutable-head
   • It is possible... but maybe not as strong of consistency as other approaches
3. Rebuildability and completeness is vital
4. In-motion content is a new concept to the community
5. Is there any issue with the notion of a mutable-head
   • not really
   • important that mutable-head be in the spec
   • This could raise to the level of a Fedora governance question
6. There is still importance in creating versions
   • Even though this is a new concept to the community
7. Complexity in Fedora's implementation is that some Fedora content will never be versioned
   • Must be able to support rebuildability
   • One solution is that un-versioned content will not be preserved
   • This would not be a solution that is palatable with much of the existing Fedora community
8. Is auto-versioning also a potential solution
   • Is inventory/size bloat an issue?
9. Counter-point: if users do not care about versioning, do they care about OCFL?
   • Users still want the benefits of OCFL
   • Users still want co-located content, if sometimes versioning is used
10. ACTION: Andrew to bring mutable-head to OCFL spec editors
11. Interest in alternate storage backends?
    • For folks who do not care about OCFL qualities, other backends are possible
12. Conversation at Islandoracon has come from Fedora birds-of-a-feather and hallway talk

Actions

•  Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
•  David Wilcox will review the NDSA matrix and pull out the concrete technical requirements that could be considered during the Fedora 6 development.
  

...