https://folio-org.atlassian.net/browse/ERM-2133

@Claudia Malzer 

https://folio-org.atlassian.net/browse/ERM-2306

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

https://folio-org.atlassian.net/browse/ERM-2307

• 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

https://folio-org.atlassian.net/browse/ERM-2308

• 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

https://folio-org.atlassian.net/browse/ERM-2309

• 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

https://folio-org.atlassian.net/browse/ERM-2310

• 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

https://folio-org.atlassian.net/browse/ERM-2311

@Peter Böhm 

• 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

https://folio-org.atlassian.net/browse/ERM-2312

@Ethan Freestone 

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

https://folio-org.atlassian.net/browse/ERM-2313

@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

https://folio-org.atlassian.net/browse/ERM-2314

Gill to develop mockups for review in Sprint 147

https://folio-org.atlassian.net/browse/ERM-2304

@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

https://folio-org.atlassian.net/browse/ERM-2305

@Ethan Freestone 

• 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

https://folio-org.atlassian.net/browse/ERM-2315

@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

https://folio-org.atlassian.net/browse/ERM-2317

For ERM-2305