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  
5. David Wilcox  
6. Ben Cail 
7. Thomas Bernhart 
8. Daniel Lamb
9. Ben Pennell

Agenda

1. Announcements

   1. New tickets/bugs: 
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - prevents Jenkins from building
2. Committers leaders call on Wed @11am ET
   1. What are the take-aways?
3. Open PRs
   1. https://github.com/fcrepo4/fcrepo4/pull/1667
   2. https://github.com/fcrepo4/fcrepo4/pull/1669
4. Pre-Sprint focus:
   1. simple search plan
      1. What do we plan to support in 6.0.0? 
      2. Samvera / Valkyrie is noted below, does Islandora have an interest in the Search Service?
      3. 2019-02 Fedora Design Summary
      4. Query Service Specification
      5. Samvera / Valkyrie Queries
      6. Islandora Community Feedback:

         1. Seth Shaw: Show me all the resources updated since x date

         2. Don Richards:  search for resources  by hash

         3. Danny Lamb:  consistently hears:  basic object counts: how many resources [ in repository | with matching path | contained by x\

         4. Mark Jordan:  all subjects with a specific predicate and property value - possibly with configurable predicate list ?

   2. Plain Vanilla Support Proposal:  Peter Winckles
   3. OCFL file name disambiguation
      1. The problem :   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Solutions?
      3. Plain-Vanilla: are there any issues here? 
5. Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
6. Fedora 6 testing
7. Containment Index
   1. How to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
8. Housekeeping PRs
   1. https://github.com/fcrepo4-labs/fcrepo4-docker/pull/38
   2. https://github.com/fcrepo4/fcrepo4/pull/1628 
9. Fedora 6 Roadmap?

10. <Add 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

Actions

• Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-04-30 - Fedora Tech Meeting)
• Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-04-30 - Fedora Tech Meeting)
• Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
• Who:  After team has a chance to comment, send Ghost Node idea to general community for feedback
• Who: Decide who works on what in the next sprint