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/88068382811
  
  • Meeting ID: 880 6838 2811
  • 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. David Wilcox  
3. Jared Whiklo
4. Peter Winckles   (out)
5. Ben Pennell 
6. Calvin Xu
7. Michael Ritter  
8. Demian Katz
9. Geoff Scholl

Agenda

1. Announcements
2. Feedback Session Debrief
3. Camel Toolbox Sprint October 4-8: Sprint Board 
   1. What can we bring home in the next two days?
4. Current Work / New Issues/Bug

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3771

5. Tickets available to be worked before 6.1.0 release:

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3767

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3739

   3. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3700

   4.  

      Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3699

6. Your topic here

Tickets

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

Announcements

• Docuteam presentation will be Oct 20

Feedback Session Debrief

• Positive feedback about fedora and moving to 6
• Eli trying to do migration of dataset in S3, estimated it would have taken 10 months. Will need to parallelize across multiple machines using import/export tool.
• Action: create wiki page to record the process for performing migration parallelized across machines

Camel Toolbox Sprint October 4-8 Planning

• Trying to get PRs merged prior to sprint
• Work on HTTP message forwarding service is underway
• Goal is to be able to release toolbox shortly after sprint

Current Work / New Issues/Bugs

• Camel toolbox status - Fixity PR should go first, then the audit triple store
• Fcrepo-3771 - Should improve latency when writing binaries, regardless of storage system. Biggest impact for migration utils
  • This is in addition to a number of other performance improvements that have already been committed

Tickets available to be worked before 6.1.0 release

• Determining whether to drop the two unicode related bug tickets, checking with community if there is an immediate need
• Still determining how we would approach changing the mimetype of binaries

Indexing blank nodes in Solr

•  Could the ldpath transform support indexing blank nodes? Will require more research and possibly a custom approach.

Upgrading RDF ontology versions

• What do we do in fedora when ontology versions advance, such as PREMIS which is currently at v1, which could be v3.
• The PREMIS properties are generated, and it would likely be straight forward to the switch over without having to migrate RDF (for fedora produced properties at least).
• Would cause breakage in terms of clients reading RDF from fedora, since they would be different properties. Could require reindexing triple store.
• Could take the approach of using the PREMIS namespace URI from the namespace configuration, then users would edit the configuration to switch to newer namespace version.
  • This only works if it is just the namespace URI changes, it would not apply to cases where the predicate itself changed.
• Action: Create a ticket for allowing namespace URIs from configuration, tickets for documentation

Jira cleanup

• Reviewing old tickets, will create kahnban board for remaining 6.1.0 tickets.

Docker

• Mike: Added JMS base URL to configuration
• Thomas will be doing some further work based off Mike's work, configuration options, credentials