Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://lyrasis.zoom.us/my/fedora
  
  • Dial-in: 
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

• Join fedora-project.slack.com on the "tech" channel

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. Ben Pennell 
11. Rosie Le Faive
12. Dan Field
13. Ben Cail
14. Mohamed Mohideen Abdul Rasheed
15. Joseph Rhoads
16. David Wilcox

Agenda

1. Announcements 
   1. Sprint 2
   2. ?
2. Proposed PersistentStorageSession interface 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

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

4. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

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.