Page Comparison

This page contains historical data from the Overall Status Update table on the FOLIO Q1 2020 (Fameflower) Weekly Status Report

...

Report Date

...

Overall Status Update

...

Q1 Feature Count on Report Date

...

This page contains historical data from the Overall Status Update table on the FOLIO Q1 2020 (Fameflower) Weekly Status Report

Report Date

Overall Status Update

Q1 Feature Count on Report Date

Functional

NFR

2020-02-18

Jakub Skoczen

Platform Development in Sprint 82:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key RMB-559
  – streaming utility for RMB, requested by Kruthi Vuppala (Concorde) for
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINV-196
- Jira Legacy
  server System Jira
  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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIIN-647
- Okapi bug reports:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-795
    (raised by Hongwei)
  - Jira Legacy
    server System Jira
    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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIIN-985
  
  Jira Legacy
  server System Jira
  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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIIN-985
  but not all scenarios (
  Jira Legacy
  server System Jira
  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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key OKAPI-767
- Medium: header injection. Fixed in RMB in Q4
  Jira Legacy
  server System Jira
  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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-1233
  severity is low due to
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODAT-56
  :

FOLIO DevOps:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2427
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2428
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2401
- Jira Legacy
  server System Jira
  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

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q1 2020" ON (2020-02-18) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-18) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2020-02-11

Cate Boerema (Deactivated)

Discussion of how to store
Jira Legacy
server System Jira
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 Jira
  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
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIREQ-378
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIREQ-345
Core Functional is picking up
Jira Legacy
server System Jira
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 Jira
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 Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key OKAPI-795
      (raised by Hongwei)
    - Jira Legacy
      server System Jira
      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 Jira
    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 Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINV-196
  - Jira Legacy
    server System Jira
    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 Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-435
    and
    Jira Legacy
    server System Jira
    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 Jira
    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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2386
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2426
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2427
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2428
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2401
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2336

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q1 2020" ON (2020-02-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2020-02-04

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: Release Notes
  - 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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-501
  on hold, as it is blocked by fee/fine work (
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-2246
  )
- To replace this work, Core Functional has begun development on
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-88
  which had previously been scheduled for Q2
- Discussing storage of
  Jira Legacy
  server System Jira
  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 Jira
    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
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIREQ-378
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIREQ-345

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q1 2020" ON (2020-02-04) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-04) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2020-01-29

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 Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key OKAPI-795
      (raised by Hongwei)
    - Jira Legacy
      server System Jira
      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 Jira
    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 Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINV-196
  - Jira Legacy
    server System Jira
    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 Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-435
    and
    Jira Legacy
    server System Jira
    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 Jira
    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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2386
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2426
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2427
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2428
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2401
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2336

Cate Boerema (Deactivated)

Q1 planning finalized. See dashboard.
Q4 release closed.
- Statistics: Release Notes
  - 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 Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-501
  on hold, as it is blocked by fee/fine work (
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-2246
  )
- To replace this work, Core Functional has begun development on
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-88
  which had previously been scheduled for Q2
- Discussing storage of
  Jira Legacy
  server System Jira
  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 Jira
    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
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIREQ-378
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIREQ-345

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q1 2020" ON (2020-01-29) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-01-29) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2020-01-21

Weekly status cancelled due to WOLFcon

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q1 2020" ON (2020-01-21) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-01-21) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

...

Versions Compared

Old Version 3

New Version 4

Key