...

1. Danny Bernstein 
2. David Wilcox  
3. Jared Whiklo  t
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. Docker PR: https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/163
      2. Fixity and Audit Services
         1. PRs are up but need testing instructions
      3. Calvin's external content issue
      4. Fixity PR

         DMDINDEX xml metadata indexed to solr via cameltool box XPATH for item metadata

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

      What do we want to go into the next releases and when to release?

      1. 1. 1. 3760

         2. Audit Triplestore PR
         3. fcrepo
            1. issuses
               1.  Important
                  1. Upgrade jena: https://fedora-repository.atlassian.net/browse/FCREPO-3767
                  2. Cannot change mime/filename: https://fedora-repository.atlassian.net/browse/FCREPO-3739
               2. Maybe important
               3. Unicode filename encoding: https://fedora-repository.atlassian.net/browse/FCREPO-3700
               4. Filename special chars: https://fedora-repository.atlassian.net/browse/FCREPO-3699
               5. link-format memento problem: https://fedora-repository.atlassian.net/browse/FCREPO-3655
               6. TimeMap prefer headers: https://fedora-repository.atlassian.net/browse/FCREPO-3660

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

               3584

               3761

            2. Andy's work

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

                  3635

                  3770

            3. Villanova work

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

                  1. https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/1663597

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

            1. https://github.com/fcrepo/fcrepo/pull/19413585

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

            1. 1774Good and easy to do:Duraspace in webconsole: https://github.com/fcrepo/fcrepo-storage-ocfl/pull/44
            2. migration-utils cleanup: 
               1. fedora-repository.atlassian.net/browse/FCREPO-3749Important but can wait:Async rebuild: https://fedora-repository.atlassian.net/browse/FCREPO-3735
            3. release target date?
            migration-utils
            1. 1. github.com/fcrepo/fcrepo/pull/1942
               1. https://
               fedora-repository.atlassian.net/browse/FCREPO-3679
               1. github.com/fcrepo-exts/fcrepo-upgrade-utils
            1. ?
            fcrepo-migration-validator
            1. 1. /pull/47
      2. Upgrading RDF ontology versions
      3. Tickets available to be worked before 6.1.0 release:

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

            3772
         2. fcrepo-import-export
         3. all projects:
            1. Duraspace in code headers 
      4. Jira cleanup update
      5. Upgrading rdf ontology versions
      6. Reminder of low hanging documentation tickets:
         1. https://fedora-repository.atlassian.net/browse/FCREPO-3756 
         2. https://fedora-repository.atlassian.net/browse/FCREPO-3751
         3. https://fedora-repository.atlassian.net/browse/FCREPO-3573

      7. 1. 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

      8. Your topic hereYour topic

      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

      ...

      1. Looking to fill David's position
      2. No feature asks from users that they met with

      ...

      1. Sprint coming up
      2. There's a PR for getting the toolbox running in docker
      3. Calvin needs component for indexing xml metadata. Some discussion about what would be a more general use case and supporting pluggable components in the toolbox
      • 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

      ...

      1. Do it – there is a mime type deprecation that may affect people

      ...

      1. Do it

      ...

      1. Jakov will test filename character encodings
      2. Need to know importance from Ben

      ...

      1. Not that critical

      ...

      1. Danny to followup with Scott to see how important this is

      ...

      1. Not important for next release

      ...

      1. This is a big change due to the package changes and should probably wait

      ...

      1. This only affects rdf resources and is not an important change

      ...

      1. We can't solve this problem better than we currently are yet

      ...

      1. This would be a nice to have if some one is willing to add it

      ...