Set up dependencies / libraries to for

• ERM Comparisons
• Plugin Repositories
  • Find License
  • Find Eresource
  • Find Agreement
• Local KB Admin

• 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

• 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
• Components and Changes
  • Frontend: 
  • Backend: mod-agreements
• QA: snapshot
• Development Estimate

• Approach
  • API to be developed in tandem with ERM-1800
• 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