Page Comparison

Jakub Skoczen

• Q1 2020 Release Management
  • Release environment: https://folio-fameflower.dev.folio.org/
  • https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8/edit#gid=0
  • Bugfix releases since last report:
    • ui-erm-usage 2.7.1
    • data-import-processing-core v1.0.1
    • mod-inventory-storage 19.1.1
    • mod-source-record-storage v3.1.2
    • stripes-erm-components 2.3.1
    • ui-licenses 3.7.2
    • mod-data-import-converter-storage v1.7.1
    • stripes-acq-components v2.0.2
    • ui-invoice v2.0.2
    • ui-receiving v1.0.1
    • ui-organizations v2.0.1
    • mod-organizations-storage v3.0.1
    • mod-source-record-manager v2.1.1
    • mod-pubsub v1.1.1
    • mod-inventory 14.1.0
    • od-orders-storage v10.0.1
    • ui-orders v2.0.1
    • ui-data-import v1.8.1
    • mod-circulation 18.0.1
    • mod-invoice-storage 3.1.1
    • mod-erm-usage-harvester 1.6.1
    • mod-licenses v2.1.1
    • mod-finance 2.0.1
    • mod-ncip v1.1.0
    • edge-ncip v1.2.0
    • mod-data-export 1.1.0 

• Core Platform development  in Sprint 84
  • Hit count issues reported during bugfest: 

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-591

     
  • RMB 29.4.0: released feature back-port for Edelweiss:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-575

       blocker for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-413

  • RMB 29.5.0 (master), IN DEVELOPMENT:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-588

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-164

  • Okapi 2.38.0 released with the following performance fixes:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-813

       reported by Martin Tran, related:

  • • • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-817

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-818

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-811

       reported by Wayne Schneider, related:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-820

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-821

  • Automatic Migrations / Module Upgrade  related:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-804

Jakub Skoczen

• Q1 2020 Release Management
  • Release environment: https://folio-fameflower.dev.folio.org/
  • https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8/edit#gid=0

  • platform-core: all modules released

  • platform-complete: all modules released
  • Bugfix releases:
    • mod-inventory 14.0.1
    • Okapi 2.37.2

• Core Platform development  in Sprint 84
  • RMB 29.3.2: released
    • Julian working on mod-inventory-storage 19.1.1  with RMB 29.3.2 and optimized upgrade path for Edelweiss → Fameflower
  • RMB 29.4.0 (branch) feature backport for Edelweiss:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-575

       blocker for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-413

  • RMB 29.5.0 (master), IN DEVELOPMENT:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-588

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-164

• Automatic Migrations / Module Upgrade  related:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-773

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-804

• Performance related:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-813

     memory leak reported by Martin Tran, heap dumps delivered from the "no dropwizard" branch are invalid, Martin has been asked to repeat tests

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-811

     reported by Wayne Schneider

Cate Boerema (Deactivated)

• Core Functional
  • All Q1 features closed
  • Have begun to work on Q2 features (esp Withdrawn items and Claimed returned part 2)
  • Svitlana (backend developer) will roll of team at end of week to join performance testing task force reducing our backend capacity to 2 FTE
  • Cap planning suggests Spine labels will have to be delayed until Q3
  • Currently blocked on two Q2 features:
    • Loan: Declared Lost (Stories dependent on fines/fees work) - Blocked by UNAM work
    • Inventory. Search call number, normalized (Core functional) - Stories not ready

Jakub Skoczen

• Q1 2020 Release Management
  • Platform team handled mod-user-import and mod-login-saml upgrades to RMB 29.x and  Q1 releases.
  • Release candidate env not bootstrapped due to missing module releases.
  • https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8/edit#gid=0

  • platform-core: Missing/unannounced module releases as of Monday 3/16 according to the release spreadsheet (maintainers and POs notified):

    • VEGA : mod-calendar, mod-email, mod-event-config, mod-feesfines, mod-template-engine, mod-sender, ui-calendar, ui-checkin, ui-circulation, ui-myprofile, ui-plugin-find-instance

    • Core:functional ui-checkout, ui-developer, ui-inventory, ui-service-points, ui-tags, ui-user

    • Update as of Tuesday 3/17: Vega modules marked as released. CF: ui-users pending release, rest released.

    • Updated as of Wednesday 3/18 : ui-users has been released. ui-requests had dependency issues which were addressed by Zak. ui-inventory has dependency issues with stripes-util 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-1021

    • Note: All but mod-event-config (26.x) and mod-sender (26.x) upgraded to RMB 29.x.
  • platform-complete : Missing/unannounced module releases as of Monday 3/16 according to the release spreadsheet (maintainers notified):
    • FSE: edge-patron, edge-sip2, mod-audit, mod-audit-filter, mod-patron, mod-rtac
    • Update as of Tuesday 3/17: All modules marked as released in the spreadsheet or removed from the release.
    • Update as of Wednesday 3/18: mod/edge-patron, mod/edge-rtac and edge-sip2 releases are not compatible with Q1. Matt and Bohdan have been notified. plugin-find-import-profile has dependency issues with stripes-acq-components Taras Tkachenko has been notified.

• Core Platform development  in Sprint 84
  • RMB 29.3.1 hotfix release to address regressions like  

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-455

    . Upgraded mod-inventory-storage 19.1.0 already shipped for Q1.
  • RMB 29.3.2 (branch):

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-583

       more complete solution to problems like 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-455

       and a blocker for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-575

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-552

       automatic migrations/module upgrade performance releated
  • RMB 29.4.0 (master):

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-575

       blocker for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-413

• Automatic Migrations / Module Upgrade  related:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-773

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-804

• Performance related:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-813

     memory leak reported by Martin Tran, heap dumps delivered from the "no dropwizard" branch are invalid, Martin has been asked to repeat tests

Anton Emelianov (Deactivated)

• Meeting today to coordinate data prep for bugfest environment 
• System is up and running now but need POs to go in and do the data setup work but coordinate whether data will be setup before or after Q1 migration
• Met with 40 plus testers yesterday
• Only 30% of test cases have been claimed
• This week will be dedicated to configuring bugfest system and prepping it for Monday
• About 10 new members have joined bugfest community (many from Germany)

Goldenrod Focus Tracks

Jakub Skoczen

• Platform development  in Sprint 84

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-583

     a blocker for 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-413

     (blocked in PR due to poor performance) but also for a "keyword" search performance regressions 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-455

     discovered last week 
• Automatic Migrations / Module Upgrade  related:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-773

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-552

     (impact on migration performance)
• Performance related:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-813

     memory leak reported by Martin Tran, a branch out for testing
• Q1 2020 Release Management 
  • Most modules upgraded to RMB 29.x on master
  • Modules still without a maintainer/team:
    • mod-login-saml
    • mod-user-import
  • mod-user-import release at risk for Q1 2020 –  Spitfire (responsible for changes in Q1) has no capacity to maintain the module. The Plaform team has picked up 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUIMP-9

     to ease the release efforts

Jakub Skoczen

• Platform Development in Sprint 83:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-559

     – streaming utility for RMB, requested by Kruthi Vuppala (Concorde) for 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-196

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-499

     – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-647

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-438

  • Okapi bug reports – tested by Hongwei with good results

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-795

       (raised by Hongwei)

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-796

       (raised by Hongwei)

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-509

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-773

• Migrations  Discussed Q4 migration performance with Carole Godfrey. Julian has analysed the logs and script and identified long migration time as related to to the "effective location" migration script and not an issue in RMB/Okapi. Specifically for Q4 timeouts should be extended to accommodate long migration time. 
• Performance Discussed Daisy vs Edelweiss performance with Martin Tran. There has been perf regressions of response time of ~30% for check-in/check-out. It's not clear if it's related to a specific module (e.g Inventory calls saw an improvement). We have speculated that the regression might be related to

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-56

  . Martin will run the test again on a combination of older mod-authtoken and newer Okapi and use Giraffe to try to analyze where the degradation happens. Also, Okapi 2.37 was tested and there's a 30% increase in response times.
• Search by call number: 

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-985

    
    Only "lightweight" normalisation for the "eye readable" search will be addressed in Q1. Blocked on 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-444

     which does not require new Platform development (only new index configuration). 
• Security Audit : three vulnerabilities reported in the first round, four in the second:
  • High: lack of permissions on an endpoint potentially carrying sensitive information – actual severity is lower as the sensitive information is not used for production deployments. Potentially related: 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-767

  • Medium: header injection. Fixed in RMB in Q4

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-478

    lack of rollout in certain module likely cause of the problem
  • Medium: token expiry. Known, 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-1233

     severity is low due to

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-56

    : 

• FOLIO DevOps sprint 82:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2427

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2428

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2401

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2336

     documented at https://dev.folio.org/guides/branch-preview-kubernetes/. Next steps?
• FOLIO DevOps sprint 83:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2467

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2444

• Release Management  Q1 2020 (Fameflower):
  • Final release timeline: Fameflower (Q1 2020)
  • Release planning spreadsheet: https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8

Cate Boerema (Deactivated)

• 2 weeks until RMB, Stripes, OKAPI deadline 
• 3 weeks until general module release deadline
• Core Functional Q1 2020 features:

• In addition to the above features, CF has made significant progress on 

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-88

   which wasn't originally targeted for Q1 but the stories were ready and we were blocked on other things (e.g. 

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2260

   was blocked by 

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2246

  )  Lesson: features with ready requirements get developed.  Those that aren't ready are left behind.
• Core Functional taking Call number searching (thin thread) from Core Platform, as they weren't tracking to get it done

Jakub Skoczen

• Platform Development in Sprint 82:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-559

     – streaming utility for RMB, requested by Kruthi Vuppala (Concorde) for 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-196

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-499

     – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-647

  • Okapi bug reports: 

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-795

       (raised by Hongwei)

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-796

       (raised by Hongwei)
• Discussed Q4 migration performance with Carole Godfrey. Julian has analysed the logs and script and identified long migration time as related to to the "effective location" migration script and not an issue in RMB/Okapi. Specifically for Q4 timeouts should be extended to accommodate long migration time. 
• Search by normalised call numbers: 

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-985

     

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-857

     should be considered in requirements analysis phase (not ready for development) latest implementation proposal from Frances Webb addresses most 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-985

     but not all scenarios (

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-857

    )
• Security Audit: three vulnerabilities reported so far (details kept private):
  • High: lack of permissions on an endpoint potentially carrying sensitive information – actual severity is lower as the sensitive information is not used for production deployments. Potentially related: 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-767

  • Medium: header injection. Fixed in RMB in Q4

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-478

    lack of rollout in certain module likely cause of the problem
  • Medium: token expiry. Known, 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-1233

     severity is low due to

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-56

    : 

• FOLIO DevOps:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2427

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2428

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2401

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2336

     documented at https://dev.folio.org/guides/branch-preview-kubernetes/. Next steps?
• Release Management Q1 2020 (Fameflower):
  • Final release timeline: Fameflower (Q1 2020)
  • Release planning spreadsheet: https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8

Cate Boerema (Deactivated)

• Discussion of how to store

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-81

   data is ongoing
  • Vince and Marc were able to agree that the first step is to store check-ins so we will do that now which will allow us to complete the feature (because the data will be persisted)
  • More conversations are still needed to decide on whether and how to use mod-audit for storing and reporting on this data.  See comments in this story for some of the considerations: 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-182

• Per the Thunderjet team, it's best to wait before using PubSub until some performance issues have been addressed
  • Given this, Core Functional will hold off on pursuing PubSub to address data synchronization:

    • Jira Legacy
      server System

      Jira

      JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-378

    • Jira Legacy
      server System

      Jira

      JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-345

• Core Functional is picking up

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-439

  from Concorde but is blocked awaiting Core Platform work
• Core Functional is considering picking up 

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2185

   from Core Platform, as this work is delayed.  Might be a good way to expose some additional backenders to RMB.
• Need to analyze state of Q2 requirements

Jakub Skoczen

• sprint 82
• Platform Dev section: 
  • • in the current sprint two tickets are being investigated:

      • Jira Legacy
        server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-795

         (raised by Hongwei)

      • Jira Legacy
        server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-796

         (raised by Hongwei)
  • Limited capacity to address functionality related tickets – issues will be evaluated and priotized on a case-by-case basis, so far the following items are planned for Q1:

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-500

       – support for streaming "downloads" (note: bulk "imports" were added to Inventory instances/holdings/items by the team in Q4 and had good feedback from migrations), requested by Kruthi Vuppala (Concorde) for 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-196

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-499

       – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-647

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-435

       and 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-184

       – requested by BNCF for slow open loan queries, 

      https://folio-project.slack.com/archives/C9BBWRCNB/p1579860339261200

    • pending Q1 requests: 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2185

       (search by normalised call number)

• In addition, the following remaining DevOps tasks have/are being completed this sprint:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2386

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2426

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2427

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2428

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2401

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2336

Cate Boerema (Deactivated) - Repeating my update from last week because we didn't get to discuss it.

• Q1 planning finalized.  See dashboard.

• Q4 release closed.  
  • Statistics: Cross Release NotesStatistics
    • In the end, the amount of work completed in Q4 2019 was very comparable to Q3 2019
    • That said, we clearly over-committed compared with previous quarters.  We committed to almost twice what we completed, resulting in a high percentage of "spillover" features.  Potential reasons:
      • Failure to account for increased bug fixing given we now have a production user
      • UNAM team dropping out
      • Over-commitment by teams not using the cap plan for planning (e.g. @Cult, Course reserves)
      • Requirements not ready for Export 
      • Technical dependencies between teams
    • For Q1, we have taken measures to avoid this issue:
      • Accounting for more bug fixing in the cap plan
      • Being more careful about accounting for technical dependencies and requirements readiness in planning
      • Our baseline committed feature count (90 features) is much more in line with previous quarters.
• Other news:
  • Darcy Branchini taking over for Khalilah as lead PO for Vega
  • Core Functional putting 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-501

     on hold, as it is blocked by fee/fine work (

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2246

    )
  • To replace this work, Core Functional has begun development on 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-88

     which had previously been scheduled for Q2 
  • Discussing storage of 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-81

     data
    • In house use is looking like just a type of circulation data which ought to be captured in the circulation log (planned to leverage mod-audit)
    • While circ log was not deemed MVP, In house use was
    • This means we need to consider getting mod-audit fit for purpose.  See comment here, for Vince's thoughts on steps: 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-182

  • Anne-Marie is scheduling a knowledge sharing meeting on PubSub with from Core Functional, Thunderjet and Folijet to discuss what impact this may have in your apps.  Core Functional has a couple of bugs it has on hold awaiting a stable version of PubSub:

    • Jira Legacy
      server System

      Jira

      JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-378

    • Jira Legacy
      server System

      Jira

      JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-345

Jakub Skoczen

• combined sprint – 80 and 81
• Starting from sprint 80 the Platform team is being restructured:
• Platform Dev section: 
  • with the departure of EBSCO developers (Eric and Hongwei) Dev sub-team has been reduced to 2 devs: Adam (IndexData) and Julian (OLE/GBV)
  • Dev team will remain responsible for maintenance of Platform components – Okapi, RMB and authentication/authorization (mod-permissions/mod-authtoken/mod-login).
  • Performance optimisations remain a strong focus area:
    •  in Q4 2019 various inventory search/filtering and authentication/authorization perf improvements were delivered, many of which has had positive impact across the entire platform, including high-level circulation operations like check-in and check-out
    • in Q1 2020 the team will focus on generic solutions to improve business-logic layer (check-in/check-out/renewals but also other API operations, best combined with local optimisations in individual modules but capacity in the functional teams remains a challenge) and core infrastructure performance (Okapi/mod-authtoken/mod-permissions) plus any specific perf issues raised by the community.
    • in the current sprint two tickets are being investigated:

      • Jira Legacy
        server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-795

         (raised by Hongwei)

      • Jira Legacy
        server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-796

         (raised by Hongwei)
  • Limited capacity to address functionality related tickets – issues will be evaluated and priotized on a case-by-case basis, so far the following items are planned for Q1:

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-500

       – support for streaming "downloads" (note: bulk "imports" were added to Inventory instances/holdings/items by the team in Q4 and had good feedback from migrations), requested by Kruthi Vuppala (Concorde) for 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-196

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-499

       – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-647

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-435

       and 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-184

       – requested by BNCF for slow open loan queries, 

      https://folio-project.slack.com/archives/C9BBWRCNB/p1579860339261200

    • pending Q1 requests: 

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2185

       (search by normalised call number)
  • Limited capacity to keep maintaining orphaned and "no clear maintainer" modules, this includes:
    
    • mod-users
    • mod-users-bl
    • mod-user-import
    • mod-login-saml
    • mod-configuration
• Platform DevOps resources (Ian, John and David) are being consolidated with the IndexData DevOps team. Until the project finds replacements or additional resources, ID DevOps will provide ongoing, steady-state support for:
  • maintenance of reference environments: folio-snapshot, folio-snapsthot-stable, folio-testing,
  • maintenance of the CI and build infrastructure (Jenkins) — integration, builds and testing for FOLIO modules
  • maintenance of the FOLIO Kubernetes cluster and related environments (e.g continuous snapshot environment, migrations env, performance env)
  • help with design and tooling for production-ready FOLIO deployments (systems documentation and diagrams, examples)
  • supporting FOLIO Release Management -- Q1 2020
  • general infrastructure support for FOLIO developers

• In addition, the following remaining DevOps tasks have/are being completed this sprint:

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2386

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2426

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2427

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2428

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2401

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2336

Weekly status cancelled due to WOLFcon