...

Agenda

1. Announcements/Updates
   1. 2020-08 Online Fedora Users Group Meeting - American Timezones
   2. 2020-09 Online Fedora Users Group Meeting - European Timezones
2. Planned Breaking Changes (standing topic)
3. Mementos
   1. Binary and Binary Description Mementos:  to version together or apart?
   2. AG memento behavior (discussed at the bottom of the above document)
   3. Delete mementos?
4. PR Round Up
   1. Run ITests against all DBs
   2. Finish fleshing out new storage layer (This PR is blocking two additional PRs that I have ready that depend on it)
   3. FCREPO-3399 - External URI case sensitivity and handling changes
   4. Implements rdf_type parameter and output field in simple search.
   5. do not index deleted resources on rebuild
5. High availability
   1. The use case we've been hearing about
   2. What would it take for us to support
6. Fedora 6 Testing

7. Your Topic Here

   Expand
   title Tickets resolved this week...
   Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

...

1. Announcements/Updates
   1. Fedora user group just wrapped up. 35-40 people. Good participation, and interest in doing more in the future.
2. Planned Breaking Changes (standing topic)
   1. None
3. Mementos
   1. Binary and Binary Description Mementos:  to version together or apart?
      1. Leaning towards "Versioning together". Fairly clean approach, and can use transactions to get around double mementos.
   2. AG memento behavior (discussed at the bottom of the above document)
      1. Delete mementos?
   3. PR Round Up
      1. Run ITests against all DBs
      2. Finish fleshing out new storage layer (This PR is blocking two additional PRs that I have ready that depend on it)
      3. FCREPO-3399 - External URI case sensitivity and handling changes
      4. Implements rdf_type parameter and output field in simple search.
      5. do not index deleted resources on rebuild
   4. High availability
      1. The use case we've been hearing about
      2. What would it take for us to support
   5. 1. 1. Should all AG resources be versioned together or should the resources be versioned independently?
            1. After much discussion it was decided that the current main behavior is best
               1. AG time maps contain the mementos for all of their children
               2. AG part time maps only contain mementos that apply to the specific resource
               3. Mementos cannot be created directly on AG parts. They must be created at the AG level
         2. Should we allow creating mementos when there are no content changes?
            1. Currently, the thought is no. The current behavior is that the request returns success with a link to the head memento
         3. Should we be updating something other than the last modified timestamp?
            1. There has to be a binary change to a resources header file in order for a memento to exist. The current idea is to touch the last modified date so that the headers change. The downside of this is that the last modified date now no longer represents the last time the resource content changed. If this is a problem, we will need to touch a different field in the headers.
      2. Delete mementos?
         1. Didn't get covered
      Fedora 6 Testing

   Actions

   •  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-08-13- Fedora Tech Meeting)
   •  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-08-13- Fedora Tech Meeting)
   •  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
   •  Peter Winckles Create a Jira to update the locations files stored in OCFL
   •  migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.

   ...