...

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

Announcements

1. 5.1.0 release is out
   • Includes bugfix that allows import/export to work correctly
   • Testing of round-tripping is encouraged
2. Michael Klein has put out a new Docker image

Fedora 6 Pilots

General updates

1. Three pilot institutions
   • DocuTeam
   • Natl Library of Medicine
   • Univ of Wisconsin - Madison
2. It would be great to have addtional "partners"
   • Even if not as full "pilots"
3. Collecting requirements from pilot partners
4. Pilot effort will be running for the ~next year
5. Pilot meetings will be scheduled as needed
6. There is an open #fedora6-pilots Slack channel

OCFL Implementation

1. Peter W has put something together recently
2. Open questions around what the interface should look like
3. Currently supports PUT/GET... and most of the OCFL spec

F6 Architecture

1. Important for us to establish a shared understanding of transactions/locking/etc on how the architectural layers should interact
2. https://wiki.duraspace.org/display/FF/Fedora+2019+Architectural+Diagrams
   • HTTP Layer remains intact
   • Kernel Layer
     • Could potentially support swappable implementations
     • Session manages transactions/locking
   • Persistence Layer
     • Some features from prior ModeShape layer will move here
   • OCFL Layer
     • State may be maintained at different layers
3. Transactions and Locking
   • Currently, support txns across resources
   • Maybe scoping txns to a single OCFL object may make sense
   • If we want to scope txns across objects, that would have to be managed at the Fedora level... and the problem becomes more challenging
   • Proposal: scope txns to a single OCFL object
     • Primary use case: batch loader creating a complex resource
   • Do we want to consider architecting for cross-object txns?
     • Design the HTTP API to potentially support other scopes of txn, but implement for the single OCFL object case
     • Archive Groups may be a door for broader scope for txns
   • Would be nice if the txn-endpoint were advertised as a resource header... as opposed to a triple
   • Ideally not coupling txn-model to ldp-model
     • Bulk updates require cross-object txns
   • Do we need to maintain session state across clients?

...The conversation will be continuing at 1pm ET

migration-utils 

Mike Durbin created migration-utils to facilitate 3-4 migration.  Andrew has extended that project to migrate from Fedora 3 to OCFL.

...