/
2023-03-01 ERM Weekly Delivery Update

2023-03-01 ERM Weekly Delivery Update

Mar 01, 2023

Meeting Details

Date

Mar 1, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-03-01 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Ethan Freestone

  • @Owen Stephens

  • @Monireh Rasouli

  • @Claudia Malzer  

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

  • Testrails Export

 

WIP 

  • ISSUE: 

    • Progress / Impediments: 

    • TODO: 

    • New unknowns: 

    • Help or input needed: 

    • ETA for review: 

  • What progress or impediment on previously stated actions?

  • What's left to do?

  • Any new unknowns?

  • What help or input is needed?

  • When expected to be ready for review?

In Progress

  • ERM-2645: Set up inital e2e test for LicensesClosed

    • Progress / Impediments: 

      • mostly done - draft PR raised

      • 60s test delay because of create-edit lag

      • name field resetting 

        • textField selector may be trying to grab an input and defaulting to first input to clear it

    • TODO: 

      • try implementing navList interactor

      • refactor updatedDate check

      • add `example` in code for future reference 

    • New unknowns: 

      • how to et the newly created license id 

    • Help or input needed: 

      • use force: true to get round menu not rendered? try navList interactor

      • cannot reset updatedDate constant?

        • use let  instead 

        • check updated <> created, no need to check for a specific date

    • ETA for review: today

  • ERM-2630: Add new endpoint for external KB "push" processClosed

    • Progress / Impediments: 

      • expecting some external service to use Gokb scrollAPI in chunks of 5000 packages (not content items), managing state and queue position

      • treating cursor/state as black box for now

      • should be able to use schemas/shapes mostly as-is

        • add package id to contentSchema

        • add comment t

      • will end up with 2 parallel ways to get data in

        • scheduled harvest for package ingest (current)

        • push service (this piece)

      • will need to refactor package ingest (harvest) service to separate out reusable ingest functionality

      • support either harvest or push (not both) for an ingest

      • external push service will use TIPPs to set up content items, linking them to known content rather than creating new ones

        • provides transactional redundancy

        • provides a restart point 

        • reduce performance burden on agreements

      • so far: 

        • 2 trivial endpoints set up under `erm/pushkb`

    • TODO: 

      • get endpoints accepting/logging out json input

      • dig into ingest process to plan refactoring

    • New unknowns: 

    • Help or input needed: 

    • ETA for review: 

  • ERM-2612: Add support for content type property on AgreementsClosed

    • Progress / Impediments: 

      • ready for code review

      • Jira issue

    • TODO: 

      • Ethan to stub new Jira for multiselect and delete ERM-2612

    • New unknowns / Help or input needed: NA

    • ETA for review: now

 

Pending

  • ISSUE

    • Blocking conditions

    • Action needed

  • Are the blocking conditions still relevant? 

  • What action is needed to unblock, and by whom?

 

  • ISSUE: 

    • Who / When: 

    • ETA Ready for Dev: 

  • Who needs to be involved in the elaboration process? 

  • What is the timeframe for getting input?

  • When is the issue expected to be ready for development?

 

 

  • Who is picking up what next?

  • When is next issue expected to start / complete?

  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • NA

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

Allocations

 

At Risk

  • What is now at risk of not being started this sprint?

  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

Sprint Backlog -  At Risk

Removed

  • NA

 

In Review

  • Any impediments to review or QA?

  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?

 

Code Review:

  • NA

QA / UAT 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

  • NA

Maintenance / Tasks

  • NA

Release Tasks

  • NA

Closed: Orchid R2023.1

Closed: Orchid R2023.1 Bugfix

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

Component Updates

  • NA

Release Planning

  • Orchid Bugfix tests to follow ERM-2643

Testing

  • describe permissions as part of test scenarios

Security

  • NA