ERM Sprint 146

Sprint Goal / Focus

  • Bugfix Deadline

Sprint Schedule

  • Sprint: 146
  • Release: 2022.2 Morning Glory  
    • Sprint 146: Bugfix Deadline (12 August 2022) [FOLREL-535]
  • Release: 2022.3 Nolana  
    • Sprint 6 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)
    • Sprint 151: Module Release Deadline [FOLREL-549]
      • Backend 26 Oct 2022
      • Frontend 28 Oct2022
    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]

Development Meetings

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Claudia: 8-12 Aug
  • Owen: 15 Aug - 2 Sep

Lead Roles:

QA Environment: folio-snapshot

Present

Planning Questions

  • Does the issue meet the criteria for Definition of Ready?
  • What front and back end components are affected?
  • What changes need to be made? (additions, removals or modifications)
  • What development tests need to be written?  
  • What data does the developer need to verify their work?
  • What are the known unknowns? 
  • What is needed to QA? (environment, data, scripts)

Navigation

 Sprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions





Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 


Planning Notes Template

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2133 - Getting issue details... STATUS

Claudia Malzer 


UXPROD-3754 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2306 - Getting issue details... STATUS

(tick)

Add sibling list property to availabilityScope

  • Approach

    • create as imported
    • store as refData (normalised objects, like packageContentType)
    • add refData to domain model
    • add refData to migrations
    • extend schema and ingest service
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data: none, use package tests

  • Dependencies

    • required for 2307, 2308, 2309
  • Known Unknowns: none 

  • QA: snapshot

  • Development Estimate: 2d

ERM-2307 - Getting issue details... STATUS

(question)
  • Approach

    • explicitly comment the behaviour /  business rule in the code
    • Add logic (if / elseif) inside adaptor
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements (adaptor)

  • Tests / Data: none

  • Dependencies: ERM-2306

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: == ERM-2311

ERM-2308 - Getting issue details... STATUS

(question)
  • Approach

    • render refdata label as bulleted list
    • use stripes-list component
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data:

    • adapt availability test using stripes-list interactors

  • Dependencies: ERM-2306

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: 0.5d

ERM-2309 - Getting issue details... STATUS

(question) 
  • Approach

    • lookup the refdata
    • query refdata
    • filter on list
    • use selection rather than checkboxes doing lookup
    • publicationType is checkboxes - so, OR'd in filter, rather than AND
    • no default to be set 
    • no lookahead for now
  • Components and Changes

    • Frontend: ui-agreement

    • Backend: none

  • Tests / Data:

    • if we already have existing filter tests

  • Dependencies: ERM-2306

  • Known Unknowns

    • list size may encourage select rather than checkboxes
      • expecting to be in the order of 10s, rather than 100s
  • QA: snapshot 

  • Development Estimate: 1d

ERM-2310 - Getting issue details... STATUS

(question)
  • Approach

    • add new logic to packageIngestService lines 212-218
    • ensure save after block
    • use existing patterns for updating PTI
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements packageIngestService 

  • Tests / Data: package test data

  • Dependencies: no

  • Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: small

ERM-2311 - Getting issue details... STATUS

  • Approach

    • add to package schema
    • update adaptor
    • add fields to ingest 
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data: 

    • check if there is an existing test
  • Dependencies: ERM-2288

  • Known Unknowns: 

  • QA: snapshot

  • Development Estimate: 

    • bigger than ERM-2288


UXPROD-3116 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2312 - Getting issue details... STATUS

Needs Elaboration 

  • Approach

    • implement backend model needs to be updated to support many-to-many user-dashboard relationships
      • change is to separate current direct link between user and dashboard, and add an intermediate link relationship
    • refactor dashboard domain model
    • add migration for existing dashboards
    • add new dashboard / user creation
    • rewrite front end queries as needed
      • query shape should probably be updated to reflect the new 
    • add dashboard access model (add, manage)
  • Components and Changes

    • Frontend: ui-dashboard

    • Backend: mod-serviceinteraction

  • Tests / Data: 

    • backend integration testing
    • new and updated tests needed for frontend
  • Dependencies: none

  • Known Unknowns

    • see discussion on ERM-2313 and ERM-2314
  • QA: local | testing | snapshot | other

  • Development Estimate

ERM-2313 - Getting issue details... STATUS

(question)

Gill Osguthorpe 

Monireh Rasouli (afk for 3 weeks until  

  • Approach

    • add Manage Dashboard navigation
    • display list of known users with access
    • add users via existing user lookup plugin, as-is
    • take user access list for processing access changes
    • add support for maintainers to remove access
    • ensure users cannot modify their own access
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

    • new frontend tests
  • Dependencies

    • wireframes
      • view dashboard user list
      • change dashboard users
    • add user notifications and callouts
  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: 1w-2w

ERM-2314 - Getting issue details... STATUS

(error)

Gill to develop mockups for review in Sprint 147

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2304 - Getting issue details... STATUS

Peter Böhm 
  • Approach

    • triage:
      • check flow that leads to availabilityScope vs lifecycleStatus
      • check that / why lifecycleStatus maps from status
    • replace unused status field with new lifecycleStatus field (line 130)
    • in ingest, read from lifecycleStatus rather than status
  • Components and Changes

    • Frontend: none

    • Backend: GokbAdaptorGroovy, GokbOAIAdaptor

  • Tests / Data: json file in issue

  • Dependencies

  • Known Unknowns

    • why is it described as status rather than lifecycleStatus?
    • is it from Gokb?
  • QA: snapshot

  • Development Estimate: 0.5d

ERM-2305 - Getting issue details... STATUS

  • Approach

    • similar issue of missing comma with duplicate json key
    • check view files for double expansions
  • Components and Changes

    • Frontend: NA

    • Backend: mod-agreements

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate: 2d triage + fix

ERM-2315 - Getting issue details... STATUS

Monireh Rasouli 
  • Approach

    • Create columns to display multiple identifiers
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data: update existing

  • Dependencies: none 

  • Known Unknowns

  • QA: snapshot

  • Development Estimate: 1d

Release Tasks (Morning Glory Bug Fix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2317 - Getting issue details... STATUS

(tick)For ERM-2305


Brought In

Issue ID

Sprint Backlog?

Notes / Estimates / Action

ERM-2317 - Getting issue details... STATUS

(tick)For ERM-2305
ERM-2258 - Getting issue details... STATUS Claudia Malzer 

Removed

Issue ID

Deferred to

Notes / Estimates / Actions

ERM-2314 - Getting issue details... STATUS

Sprint 147Removed pending designs and elaboration




Planning Notes Template

  • Current State
  • TODO
  • Development Estimate

Rolled Over From Previous Sprint

Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2290 - Getting issue details... STATUS

Current State:

  • PR in place, needs merging
  • See Slack

TODO:

  • Ethan to follow up with John Coburn to 
  • Config changes to follow

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions

STRIPES-675 - Getting issue details... STATUS

ERM-2152 - Getting issue details... STATUS

  • Current State: partially started
  • TODO: 
    • run through tests
  • Development Estimate: 0.5d

UXPROD-3754 - Getting issue details... STATUS

ERM-2288 - Getting issue details... STATUS

  • Current State
    • development work done, 
    • local testing begun
  • TODO
    • refdata fields not working yet
    • test related / altNames / contentTypes
    • include dataTypes
    • packageDescriptionUrls could be implemented but not tested
      • relates to ERM-2311 - Getting issue details... STATUS
      • but also not in schema at the moment (for accepting in Gokb harvest)
      • descoping and moving into ERM-2311
  • Development Estimate
    • Wed 10

UXPROD-3756 - Getting issue details... STATUS

ERM-2289 - Getting issue details... STATUS

  • Current State
    • working on agreement lines
  • TODO
    • add PO lines and tabs
    • tests
  • Development Estimate
    • Tue 09


For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3591 - Getting issue details... STATUS

ERM-2076 - Getting issue details... STATUS


ERM-1343 - Getting issue details... STATUS

ERM-2234 - Getting issue details... STATUS

UXPROD-3591 - Getting issue details... STATUS

ERM-2093 - Getting issue details... STATUS



ERM-2214 - Getting issue details... STATUS