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/j/396037251
  
  • Meeting ID: 396 037 251
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

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

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein
2. Andrew Woods 
3. Peter Winckles
4. Ben Pennell  
5. Ben Cail 
6. David Wilcox
7. Calvin Xu 
8. Thomas Bernhart

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

   Tickets resolved this week...

   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.

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

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. 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.
   3. Delete mementos?
      1. Didn't get covered

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
• migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.