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. Jared Whiklo  
3. Andrew Woods  
4. Peter Winckles  (out)
5. Ben Pennell  
6. Ben Cail 
7. David Wilcox 
8. Thomas Bernhart
9. Ralf Claussnitzer
10. Daniel Lamb

Agenda

1. Announcements/Updates

   1. Search Demo
   2. New search work in the offing:
      1. https://jira.lyrasis.org/browse/FCREPO-3349 : move search to it's own table
      2. https://jira.lyrasis.org/browse/FCREPO-3353 : modified and created date
      3. https://jira.lyrasis.org/browse/FCREPO-3354: fields
      4. Rebuild search index
      5. Update search via event bus
2. Housekeeping
   1. https://github.com/fcrepo4/fcrepo4/pull/1701
   2. JMS: Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
      1. ACTION: Jared to investigate potential impact on Camel tooling - updates?
      2. Ralf Claussnitzer Message headers are useful for filtering (Camel and Nifi) → No need to parse message JSON body.
         1. https://nifi.apache.org/
   3. "master" → "main" :  when / how / who?
3. July Sprint 
   1. Fedora 6 Feature Tracking
   2. Fedora Test Suite Results
4. Review state of the Docker work
5. Performance testing
6. Defining Fedora ID limits
   1. What are limits are non-negotiable
   2. Of those that are negotiable, what is the recommendation
      1. is it user friendly?
      2. will it be performant?
      3. will anyone be unable to use Fedora as a result?
   3. List of limits to consider:
      1. OCFL object root directories
      2. uri limits
      3. invalid characters or character patterns
      4. ?
7. Community-raised bug:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

8. 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
   1. Search demo
      1. Now available on YouTube
   2. Issues with search integration tests
      1. These have been addressed and merged 
2. Housekeeping
   1. https://github.com/fcrepo4/fcrepo4/pull/1701
      1. Peter reviewed but was unable to build
      2. Danny will test and merge
   2. JMS: Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
      1. Jared investigated potential impact on Camel tooling
         1. Not relying on headers coming from Fedora
      2. Ralf Claussnitzer Message headers are useful for filtering (Camel and Nifi) → No need to parse message JSON body.
         1. Camel can read and process message headers, but this is not so easy with Nifi
         2. Not currently causing problems so we will probably keep unless there is a good reason to remove
   3. "master" → "main" :  when / how / who?
3. Fedora Docker file
   1. Doesn't seem to be ready for production. No way to configure credentials, etc.

Actions

• Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-06-18 - Fedora Tech Meeting)
• Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-06-18 - Fedora Tech Meeting)
• Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
• Jared Whiklo to investigate impact of removing JMS Headers on camel tooling.