• Approach

• • need to include a header from FOLIO
  • can grab tenant from, eg, mod-service-interactor

• Components and Changes

  • Frontend: NA

  • Backend: mod-agreements or web-toolkit

• Tests / Data / Dependencies

• Known Unknowns

  • where to add the header

• QA: snapshot 

• Release Target: Quesnelia 

• Development Estimate: <1d

17 Jan:

• descope version
• logging

Triage

• • NamedThreadFactory is used in string templating service
  • out of end-of-life support, so should find a  way to upgrade/remove
• Approach
  • need to review any documented upgrade path - is there a straightforward path to go from 2 to 3
  • are we vulnerable to the jetty-io vulnerabilty?
    • influences backport requirements (esp Orchid which is on Grails 4)

• Components and Changes

  • Frontend: NA

  • Backend: 

• Tests / Data / Dependencies

• Known Unknowns

  • whether we are affected by virtue of using netty

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

Current: 

• upgrade path documentation doesn't help
• looks like (via grep) this is the only use of ehcache

TODO

• need to decide whether to bail ehcache to use another NamedFactory provider
• potentially could do this internally, without another dependency
• run gradle clean  and check dependencies to see if ehcache/jetty-io are brought in transitively

• Triage

• Approach

• Components and Changes

  • Frontend

  • Backend

• Tests / Data / Dependencies

• Known Unknowns

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

• Triage

• Approach
  • Should be able to just turn off autofocus on the end-date
  • However, this is handled by inputRef being on both start and end date, so just get rid of the inputRed on end-date (line 136)

• Components and Changes

  • Frontend: ui-agreemeents

  • Backend: NA

• Tests / Data / Dependencies

• Known Unknowns

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

• Triage

  • fetch of loadMore is causing cache of what's opened to refresh
  • which may be because of batch fetching PO lines 
  • redraw closes and remounts 
• Approach
  • needs investigation to understand chain of events leading to invalidation or refresh - what's the trigger
  • then need to decide what's desirable behaviour - do we need to retain the user's view or reset it post-redraw?
    • if we don't then any data changes won't be reflected
  • Owen to revisit whether this is an issue in current versions 

• Components and Changes

  • Frontend

  • Backend

• Tests / Data / Dependencies

• Known Unknowns

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

• Triage

  • previously created new Grails 6 project and incrementally added components
  • once pitfalls identified, each module took very little time
• Approach
  • will starting up a new grails project with the CLI even work?

• Components and Changes

  • Frontend

  • Backend

• Tests / Data / Dependencies

  • gradle upgrade is necessary

• Known Unknowns

  • will starting up a new grails project with the CLI even work?

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

• Current:
  • grails and gradle versions determined
  • web-toolkit passing tests
  • smoother process than 4 to 5, but integration is inevitably 
• TODO
  • service-interaction failing
  • need to build into okapi environment
    • may need to rebuild rancher, which could be risky at the moment
  • review migrations, but difficult to triage atm

• Triage

  • need to revisit what choice we made for Poppy
• Approach
  • need to check whether Orchid/Poppy have the same vulnerability to determine backport requirement
  • otherwise to be dealt with (for Quesnalia) by Grails 6 upgrade

• Components and Changes

  • Frontend

  • Backend

• Tests / Data / Dependencies

• Known Unknowns

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

Needs Triage to review whether changes made by Ian will resolve.

Example: ui-orders

Approach: 

1. investigate whether native stripes component integrates cleanly and easily with ERM applications
2. apply stripes or bespoke component to selected MCLs

In Code Review

• Current State
  • being tested by Jack 
• TODO
• Development Estimate

• Approach

• • set up new open source project in K-Int gitlab
  • new micronaut service required (not using okapi or grails)
  • set up a test instance
  • will need a different dev workflow (probably using local copy of service)
  • working title: pushkb
  • avoid storing caches of transient data

• Components and Changes

  • Frontend: na

  • Backend: new

• Tests / Data / Dependencies

  • Align to when GBV start testing and using pushkb endpoint
  • ERM-3048 Possible package schema changes  with endpoint changes

• Known Unknowns

  • should be (but not clear yet) about TitleInstance Resolver
  • packageSchemaUpdater: potential conflicts when there are multiple copies of schemas in play where backwards compatibility is broken

• QA: snapshot | local | testing | other

• Release Target:  Quesnalia

• Development Estimate

• Current State
  • pushKb can make a scheduled call (1s, 1h) to Gokb
  • will fetch roughly ~700k TIPPS 
  • Stores these in a local postgres db
  • proteus json transform implemented with proof of concept schema
• TODO
  • scaling
  • extensive transformation testing
  • write fetch chunks and push to FOLIO,
    • implementing algorithm to ensure no data gaps 
    • deciding what to do with the data volume (700k feels beyond FOLIO's performance capability)
    • at a minimum: need to move the FOLIO side to being not an open http request per chunk (would be killed by  okapi), by, eg, 
      • small batch sizes? would take full day for initial ingest
      • speeding up FOLIO? (not clear how this could be done)
      • move pushKb to background thread (like jobs, but on a much smaller scale)? 
• Constraints
  • want to avoid jobs being badly interrupted by a docker container being restarted
  • tradeoff is that we have a slower but more stable process 
• Development Estimate

• Current State
  • code changes done
  • waiting on grails-okapi
  • effectively waiting on SI-38 being releaseable
• TODO
  • nothing
• Development Estimate

• Current State
  • created lookup from view pane
  • issue when updating data source and not being updated to view pane
    • should be a case of getting a fetch working and validating that
  • wll also affect ERM-2792
• TODO
  • Fix tests for external data sources
  • Write new tests
• Development Estimate

• Current State: done pending changes to ERM-2792
• TODO
  • Apply changes from ERM-2793
• Development Estimate

• Current State: 
  • licenses done
  • unable to test alternate names
• TODO
  • revisit licenses based on revised understanding of how versioning should work
  • need to clean environment to test out agreements
    
    • likely build gradle mismatch
  • revisit alternate names
  • review versioning in GORM practice
• Development Estimate

17 Jan: 

• where to set enforceVersionCheck ? gradle.properties or application.yaml
• can we default this to true?
  • if so, probably breaking change
  • check with SO
• confirmation that
  • no change to be finalised as part of spike
  • Owen to follow up with user feedback once options determined

• Needs input/action from Steve

• Blocking SI-34 and ERM-3089