Pending UAT on ERM-1938 (Agreements and AWS)

• Approach
  • match key doesn't cover anything existing
    • to be addressed later
  • Work on ERM-1986/ERM-1988 API to be progressed alongside this
• Components and Changes
  • Frontend: 
  • Backend: mod-agreements
• QA: snapshot
• Development Estimate
  • 5d including API design from ERM-198

To follow ERM-1800?

• Approach
  • API to be developed in tandem with ERM-1800
• Components and Changes
  • Frontend: ui-agreements
  • Backend: mod-agreementsDependenciesagreements
• Dependencies: 
  • ERM-1980
  • UX Design 
• Known Unknowns
  • may not be existing patterns for moving in FOLIO
• QA: snapshot 
• Development Estimate
  • UI implementation: ~2d

2022-01-31:

• Done
  • JSON handling set up
  • TitleIdentifier job / queue implemented
• TODO: 
  • Final tests then push to QA (expected ready 1 Feb)

• 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

• 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

May have (but unlikely to be) something to do with virtualising the script

2022-01-31: still using BigTest tests, which is problematic and potentially causing further failure.

TODO: 

TODO:

• Reach out to Acquisitions team to see whether they have mitigations or solutions
• Timebox further effort: 1 day

Some adjustments expected for alternative approach to updating matched keys over time.

• Some investigation to work out where to step in to process the changes
• Dev Estimate: 2d

2022-01-31 Returning from QA:

• Same internal contacts render component used that has pattern to be used. 
• Simpler than internal contacts (no roles, no links) 

Expected to not be able to host concurrent database sessions.