...

1. Danny Bernstein 
2. Peter Winckles 
3. Jared Whiklo 
4. Bethany Seeger 
5. Andrew Woods  
6. Ben Pennell 
7. Ben Cail  
8. David Wilcox
9. Peter Eichman 
10. Daniel Lamb
11. Mohamed Mohideen Abdul Rasheed
12. Dan Field

Image Added

Part 2: 

1. Danny Bernstein 
2. Jared WhikloBen Pennell
3. Ben CailBen Pennell 
4. Bethany Seeger
5. Peter Eichman

Agenda

1. Announcements
2. OCFL Community Call Update
3. Landing the Sprint
   1. Set sprint closing meeting time 
   2. Issues in progress 
   3. Issues in revewreview (PRs)
   4. Status of Search / Containment Index Design
   5. Handling RDF in Fedora 6
   6. Decisions and Open Questions
      Sprint closing meeting time
      1. Establishing clear description of F6's RDF (on disk, from non-Fedora OCFL, what changes, etc)
         1. Trim `ldp:contains` and other SMTs
         2. Normalize URLs to internal URIs
         3. Normalize serialization
   7. Draft functional requirements for repositories based on NDSA Levels of Preservation 2.0 (update)
   8. <Your question/topic here>

   ...

   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

   ...

   1.  Announcements
      All are encouraged to join
      1. OCFL
      Community call next week

      Sprint updates

      CRUD

      1. Implementing services:
         • create/update resources
         • persisting to OCFL
      2. Team is working in layers
         • OCFL
         • Persistence
         • Services
         • HTTP
         • Indexing
      3. Integration testing
         • We should be turning disabled tests back on as soon as possible

      Migration-utils

      1. So far cleaning up from last sprint
      2. Beginning on move features forward
      3. Dev team is slim

      OCFL client

      1. Updates and fixes being applied as required

      Search / Containment Index Design

      1. Beginning to sketch the DB schema
      2. Interest in tying DB updates into internal message-bus
      3. Details
         • If txn is acting on a resource that is updated outside of the txn, the txn wi
           ll fail on commit
         • Containment index: potential simplifying modeling assumption: children have only one parent container
      4. States of the index
         • In a txn
         • head
         • Within a version
      5. Need to define the expected behavior within a transaction
         • Are updates happening outside of the txn visible within the txn?
         • or, the repo state is a snapshot from the point when the txn was started
      6. ACTION: Peter to investigate approaches for txn behavior
         • ideal (complete isolation within the txn)
         • F5
         • most practical
      7. Conversation will continue at 1pm ET
         • Should also include resolution of "Open Questions"

      Open Questions: 

      1. 1. call - discussed a couple issues, planning to add some language to OCFL spec or implementation notes. Stanford has a new validator (Ruby gem).
         2. Desire to make sure Fedora 6 runs properly in the cloud. Can test S3 on OpenStack. Need details on what exactly people want to do in the cloud.
            1. ocfl-java client - starting to add support  for S3 (incomplete). More complicated, may have more requirements (eg. DB).
      2. Landing the Sprint
         1. sprint closing meeting - 1pm EST (Friday)
         2. issues in progress/review
            1. get to the point of running Fedora 6 - put something in, get it back out
            2. should make some good progress on PRs today. Things should be pretty clear. Get PRs merged even with some cleanup to do afterward.
            3. 3129 - implement get headers. Put together a proposal for fcrepo sidecar, then work on ticket.
            4. 3119 - try to get that in, base 3129 on 3119.
            5. migration-utils - things are progressing, single-stream.
            6. transaction piece -should be wrapped up this afternoon
         3. search/containment index design
            1. realigned with proposed interface, writing code to retrieve data from DB - WIP PR. Discuss later today.
         4. handling RDF in Fedora 6
            1. shared doc about handling server-managed triples, and OCFL objects from outside Fedora.
               1. 4 approaches: ignore SMT, how much to interpret RDF/directories on OCFL objects. How Fedora would behave in different cases.
               2. leaning toward ignoring SMTs, but still discussing.
               3. working on follow-up document.
               4. discuss more in Part 2.
               5. is it possible to push json-ld in, and get it exactly back out? Agreement to trim SMTs.
               6. info:fedora URI from Fedora 3 - could make it configurable to support multiple use-cases. Optionally translate URI prefix.
               7. roll out simplest things first, then add more features.
               8. should RDF files be containers? what should migration-utils do? Discuss in doc.
         5. design/open questions
            1. object deletions - root of Archive Group - add a tombstone, then delete ocfl object when tombstone is deleted?
               1. F4/5 - when object is deleted, you get a tombstone, and all the info is all lost
               2. what would other backends support? It's not part of the API. Could be specific to OCFL backend to allow bringing back an object that was deleted.
               3. could provide access to version history of tombstones, or not.
               4. Are people OK with the memory of a deleted object still being there?
               5. Could fit somewhat with Fedora 3 'D' state
      3. We went through the list of open questions.  Many items moved into the decided list.  A couple moved to nearly decided.  A few questions remain.
      4. See Decisions and Open Questions for details
         1. 1. 1. .

      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.
        
      •  Call for comments on https://docs.google.com/document/d/18rSFqqoxixmozZrgPKON59Ojpg5iOu4lsHDNMm23soY/edit# till tuesday
      •  Clarify in in documentation that multiple simultaneous writes to OCFL are not supported

      ...