• Approach

  • Add a new synchronous endpoint to receive list of TIPP data
  • Add service logic to handle endpoint
  • TIPP-based, so supports limited number
  • Retry if not returned OK
  • Package reconciliation

• Components and Changes

  • Frontend

  • Backend: mod-agreements

• Tests / Data / Dependencies

• Known Unknowns

  • what is a good limit? start with 5000, but depends on performance, esp
    • http request rate limits
    • okapi handling
  • will this go outside of the existing job process? 
    • yes
    • will be slower, but won't need a reset cursor
  • Storing title/package data to reconcile
  • what is the shape of data to ingest

• QA: snapshot | local | testing | other

• Release Target: Poppy

• Development Estimate:  6 sprints

• Triage

• Approach

• Components and Changes

  • Frontend

  • Backend

• Tests / Data / Dependencies

• Known Unknowns

  • Should this use scrolling api or OAI-PMH?

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

• Triage

  • Multiple possible alternative names, so behaviour may still return matches when attempting negation matching, which is consistent with hibernate behaviour
    • uses ALL rather than ANY negative matching
• Approach
  • likely to be a new operator and widget type (SimpleSearch 1.1)

• Components and Changes

  • Frontend: ui-dashboard

  • Backend: kint-toolkit, mod-service-interaction, mod-agreements

• Tests / Data / Dependencies

• Known Unknowns

• QA: snapshot | local | testing | other

• Release Target: 

• Development Estimate

• Triage

  • Only one description field, so should be same as filter by Agreement
• Approach
  • copy-paste from widget definition 
  • bump version of widget definition not widget type
  • see https://github.com/folio-org/mod-agreements/pull/495

• Components and Changes

  • Frontend: NA

  • Backend: mod-agreements

• Tests / Data / Dependencies

• Known Unknowns

• QA: snapshot 

• Release Target: Poppy

• Development Estimate: 1d

• Approach

  • Follow pattern as for ERM-2624 and ERM-2625

• Components and Changes

  • Frontend: ui-local-kb-admin, stripes-erm-components

  • Backend: NA

• Tests / Data / Dependencies

  • No stripes-kint-components changes expected
  • ERM-2624

• Known Unknowns: 

  • May need okapi refresh to flush a permission cache?

• QA: snapshot

• Release Target: Poppy

• Development Estimate: 1d

• Approach

  • Implement icon button with copy functionality
  • Add toast notification
  • Alternative: ClipCopy from stripes-components as per POLine

• Components and Changes

  • Frontend: ui-agreements, ui-licenses

  • Backend: na

• Tests / Data / Dependencies

  • NA: react-copy-to-clipboard 
  • Not to use pattern for copy button found in other parts of folio (eg, Inventory) – react-copy-to-clipboard

• Known Unknowns: NA

• QA: snapshot 

• Release Target: Orchid

• Development Estimate: 1d

1. Set up Jira issue
2. Set up cypress end-to-end test for agreements (Ethan)
   1. check it exists in navbar, and that it shows up 
   2. work out how to run it
   3. use as template for extending within agreements
3. Export Testrails list (Owen)
4. Review for e2e conversion (team)
5. Get Testrails logins (Jag)

Development Estimate: 2d

• Approach

  • specify limit as 1000
  • make consistent use of ==
  • refactor query parameterisation to use string rather than array, to ensure consistent component types

• Components and Changes

  • Frontend: stripes-erm-components

  • Backend: NA

• Tests / Data / Dependencies: NA

• Known Unknowns: NA

• QA: snapshot | local | testing | other

• Release Target: Orchid

• Development Estimate: <1d

• 
  

• Release Target: Orchid

• Triage

  • Can fetch all and sort in the frontend, which would preclude Load More (eg, if more than 100)
• Approach
  • Sort from linked licenses return
  • Use lodash (cleaner for multiple sort parameters) or at root (from fetch)

• Components and Changes

  • Frontend: ui-agreements

  • Backend: NA

• Tests / Data / Dependencies: NA, potentially integration based on Testrails

• Known Unknowns

  • refdata is an example of frontend sorting pattern (.sort or loadash.orderBy)

• QA: snapshot 

• Release Target: Poppy

• Development Estimate: 2d

Needs fixing in grails-okapi to prevent dashboard failure when other modules crash.

• Release Target: Poppy

• Release Target: Orchid

• Approach: https://folio-project.slack.com/archives/CAYCU07SN/p1676895466929459
• Release Target: PoppyOrchid Bugfix

• Current State
  • Reviewed, pending merge
• TODO
  • Merge if subpermissions can be changed
• Development Estimate: <0.5d

• Current State
  • Reviewed, pending merge
• TODO
  • Merge if subpermissions can be changed
• Development Estimate: <0.5d

• Current State
• TODO
• Development Estimate

• Current State
  • requires changes to stripes-components
  • cannot progress until stripes is extended (John Malconian is dealing with this)
• TODO
  • Add an on-add prop to stripes-components
  • Use addition in stripes-components in agreements 
• Development Estimate: TBA

• No blockers

• No blockers

• No blockers