https://folio-org.atlassian.net/browse/UXPROD-2850

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

@Monireh Rasouli 

Set up dependencies / libraries for enabling RTL development on

• ERM Comparisons

• Plugin Repositories

  • Find License

  • Find Eresource

  • Find Agreement

• Local KB Admin

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

@Claudia Malzer 

• Approach

  • can derive link destination to use from titleList.class 

  • avoid hardcoding link in ERM comparison, and use registry instead

    • for example, ui-agreements index has eventHandler fired by dashboard (LOAD-STRIPES-REGISTRY) which then triggers setupRegistry

    • examples in OA and Dashboard

    • documentation: Registry

• Components and Changes

  • Frontend: ui-agreements

  • Backend: none

• QA: snapshot

• Development Estimate

https://folio-org.atlassian.net/browse/UXPROD-3335

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

Push back to Morning Glory release in favour of ERM-1800

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

@Monireh Rasouli 

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

@Monireh Rasouli 

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

@Peter Böhm 

• Approach

  • each app should do their own, so this would be a PR to ui-organizations

  • pattern in agreements to follow

    • reference to ui-stripes-handler-registry

    • function is setupRegistry

  • only need to submit a PR for the lookup link

• Components and Changes

  • Frontend: ui-organizations

  • Backend: none

• Dependencies

  • environment set up for dashboard and organizations

• Known Unknowns

  • is there a stripes back and forth?

  • check mod-agreements widget definition to get organization resource name to match

• QA: snapshot

• Development Estimate

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

@Ethan Freestone 

• Approach

  • set up a job

  • look for changed TI / PCI

  • treat matchkey schema as a title instance resolver

  • if potential TI differs, it is changed

  • if an ambiguous match, then log error

    • equivalent case to not ingesting on original load

    • user has option to resolve as they see fit

      • could be updated within ERM

      • more likely, would fix in original kb

• Components and Changes

  • Frontend: 

  • Backend: mod-agreements

• QA: snapshot

• Development Estimate

https://folio-org.atlassian.net/browse/UXPROD-3339

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

To follow ERM-1800

ERM-1987: @Gill Osguthorpe > @Monireh Rasouli  

ERM-1989: @Ethan Freestone 

• Approach

  • API to be developed in tandem with ERM-1800

  • UI

    • add actions button for modal

    • modal has two lookups

• Components and Changes

  • Frontend: ui-agreements

  • Backend: mod-agreements

• Dependencies: 

  • ERM-1980

  • UX Design 

• Known Unknowns

  • may not be existing patterns for moving in FOLIO

• QA: snapshot 

• Development Estimate

  • UI implementation: ~2d

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

@Owen Stephens 

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

@Owen Stephens

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

@Owen Stephens

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

@Owen Stephens

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

@Owen Stephens

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

@Owen Stephens

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

@Owen Stephens 

• All table rows are displayed

• Load More button is missing

• When it is displayed, clicking Load More does nothing

• Needs to be checked against earlier release (Kiwi)

May need to be targeted for Kiwi Hotfix Release on 3/4 March

2022-02-14: Regression from list sorting changes

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