...

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

1. Announcements
   1. Fedora Workshop at the  SWIB  (Semantic Web in Libraries) Conference
      1. online
      2. November 29 - December 3
   2. Soliciting Community Feedback
      1. Institutional sessions will be starting soon
         1. Organizing 3 sessions, should be done by November
      2. Community Feedback form 
         1. Will send this out after the first institutional session
   3.  Webinar 9/14
2.  Optimization
   1. Currently, multiple resource type reads are occurring on single requests 
   2. Caching types on session could work, but a session could span multiple requests
      1. A more complicated cache could make this work
      2. This is largely a write optimization - not much room for optimization on reads
      3. What about a caching service? Really just an implementation detail.
   3. New round of performance tests based on input stream buffering?
      1. Community tests using Microsoft Azure did not see much improvement
      2. Should mostly benefit NAS implementations
3. Review of  Work in Progress 
   1. Camel Tool Box (CTB) Update 
      1. Reindexing Issue resolved
         1. Not sure if selective re-indexing is working but it is possible to reindex everything
      2.  PRs
         1.  https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/160 should be ready to go.
   2. Team at Villanova working on a project based on the Camel Toolbox now
4. Camel Toolbox Testing Feedback
   1. Solr indexing doesn't appear to work for NLM, may need a special plugin
      1. They need to index their XML, which isn't available by default
5. Technical solutions for graciously inviting registration/usage information.
   1. Current approach
      1. Registration is currently voluntary 
      2. We have a registry but not many people use it
   2. Possible approaches 
      1. What benefits of registration that we can offer to help cajole folks to participate?
         1. Swag, etc.
      2. Could have text on the landing page and in the logs with a startup option to suppress
      3. Could ask for email during download and nag that way
      4. Add registration prompts to GitHub release page, readme, etc.
      5. Reminders in Slack
      6. We can bring a short list of options to Steering for vetting
6. 5.1.2 status
   1. ModeShape 5.5 has an upgrade step if you're using S3 to store data, but this was timing out for Eli
   2. Ben manually updated the hardcoded timeout and sent a version to Eli to test