Versions Compared

Old Version 1

changes.mady.by.user Jag Goraya

Saved on

compared with

New Version 2

changes.mady.by.user Jag Goraya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-03-01 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-2645

    • Owen to test using Cypress
    • Needs non-prod environment to run Cypress on against these tests

WIP 

Expand
titleIn Progress
  • 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

  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-2630
    • 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
        • started
        • not wired through okapi as shape uincertain
        • can hit locally, passsing list of packages and log them out to a package schema
        • therefore package schema is accepting this approach
        • split schema to interdependently (1) expect and (2) not expect ...
      • wire schema into ingest process
      • dig into ingest process to plan refactoring
    • New unknowns: 
    • Help or input needed: 
      • Input needed from Ian to understand legacy technical decisions around, eg, remote kb, source/ref push/pull
      • To follow up on Thursday with Ian re domain model and shape of future shape/behaviour of external service
    • ETA for review: 
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-2612
    • Progress / Impediments: 
      • ready for passed to code reviewJira issue
      • needs test data to be relocated to central file
    • TODO: 
      • Ethan to stub new Jira for multiselect and delete ERM-2612
        • New unknowns / Help or input needed: NA
        • ETA for review: now
        • Progress / Impediments: 
          • used a popular 3rd party library 
          • to create and use  a sanitised link - didn't work
        • TODO: 
          • check whether href accepts object or string only
          • need to remove the js from the href element to avoid 
          • check for other uri sanity packages
          • check with Hongwei/Julian on potential solution/package
        • New unknowns: 
            • Jira Legacy
              serverSystem Jira
              serverId01505d01-b853-3c2e-90f1-ee9b165564fc
              key
    		SI-12
    ERM-2664
  • New unknowns / Help or input needed:  NA
  • ETA for review:  now

    • Pending

    Expand
    titleBlocked
    • ISSUE
      • Blocking conditions
      • Action needed
    • Are the blocking conditions still relevant? 
    • What action is needed to unblock, and by whom?


    Expand
    titleNeeds Elaboration
    • 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?


    Expand
    titleSprint Backlog


    • 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

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2645
      • OS to ask Khalilah and hosted-ref-environments

    Needs Elaboration / Triage

    • NA

    Sprint Backlog - Next Up

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2643

    Allocations

    • Claudia: 
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-17952643
    • Ethan: 
      • Release Tasks
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyERM-
        2643
        • 2640
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyERM-2648
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyERM-2649
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-26402643
    • Monireh: 
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-2612

    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
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2633
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2612
      • refdata for tests need to be removed from test resources and added to central test data file
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2624
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2625
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keySI-12
      • found it requires opening in a new window
      • pushed to QA

    QA / UAT 

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2506

    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

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2626

    Closed: Orchid R2023.1 Bugfix

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2642

    Closed (No ERM Release)

    • <10 mins

    AOB


    New Issues

    • New unexpected Proxy Settings behaviour
      • If no proxy setting set, prompts for unsaved changes when navigating away
      • handleCancel → onDelete → onDelete
        • needs logic to reset form if field length < 1
        • remove onDelete call from handleCancel
      • However, better to rewrite away from Card to MCL
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyERM
      -2646
      • Have we got another grails-okapi issue in play or pending?
        • -2793
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyERM-2792

    Added to sprint

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2647
      /
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keySI-12
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1795

    Not added to sprint

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2644
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2792
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-2793

    Other

    • Owen and Gill to review potential UX consistency issues to bring into release cycle

    Component Updates

    • NA

    Release Planning

    • Orchid Bugfix tests to follow ERM-2643

    Testing

    • describe permissions as part of test scenarios

    Security

    • NA