Skip to end of banner
Go to start of banner

Q1 2020 Overall Status Update (History)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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



FunctionalNFR
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:
        • OKAPI-795 - Getting issue details... STATUS  (raised by Hongwei)
        • OKAPI-796 - Getting issue details... STATUS  (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:
      • RMB-500 - Getting issue details... STATUS  – 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  MODINV-196 - Getting issue details... STATUS
      • RMB-499 - Getting issue details... STATUS  – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for  UIIN-647 - Getting issue details... STATUS
      • MODINVSTOR-435 - Getting issue details... STATUS  and  CIRCSTORE-184 - Getting issue details... STATUS  – requested by BNCF for slow open loan queries, 

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

      • pending Q1 requests:  UXPROD-2185 - Getting issue details... STATUS  (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:


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  UXPROD-501 - Getting issue details... STATUS  on hold, as it is blocked by fee/fine work ( UXPROD-2246 - Getting issue details... STATUS )
    • To replace this work, Core Functional has begun development on  UXPROD-88 - Getting issue details... STATUS  which had previously been scheduled for Q2 
    • Discussing storage of  UXPROD-81 - Getting issue details... STATUS  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:  CIRCSTORE-182 - Getting issue details... STATUS
    • 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:

Getting issues...

Getting issues...

2020-01-21

Weekly status cancelled due to WOLFcon

Getting issues...

Getting issues...





  • No labels