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  
5. Ben Pennell
6. Calvin Xu 
7. Michael Ritter  
8. Demian Katz
9. Geoff Scholl 
10. Jon Roby 

Agenda

1. Announcements
2. Feedback Session Debrief
3. Camel Toolbox Sprint October 4-8 Planning
4. Current Work / New Issues/Bugs
   1. Camel toolbox status
      1. Fixity PR
         1. FCREPO-3760 - Getting issue details... STATUS
      2. Audit Triplestore PR
         1. FCREPO-3761 - Getting issue details... STATUS
      3. Andy's work
         1. FCREPO-3770 - Getting issue details... STATUS
      4. Villanova work
         1. FCREPO-3753 - Getting issue details... STATUS
            1. https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/166
   2. FCREPO-3773 - Getting issue details... STATUS
      1. https://github.com/fcrepo/fcrepo/pull/1941
   3. FCREPO-3771 - Getting issue details... STATUS
      1. https://github.com/fcrepo/fcrepo-storage-ocfl/pull/44
         1. https://github.com/fcrepo/fcrepo/pull/1942
         2. https://github.com/fcrepo-exts/fcrepo-upgrade-utils/pull/47
5. Upgrading RDF ontology versions
6. Tickets available to be worked before 6.1.0 release:
   1. FCREPO-3767 - Getting issue details... STATUS
   2. FCREPO-3739 - Getting issue details... STATUS
   3. FCREPO-3700 - Getting issue details... STATUS
   4.   FCREPO-3699 - Getting issue details... STATUS
7. Your topic here

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

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