• Approach
  • happens on switcher rather than just date, such as internal contacts
  • using radio fields rather than FOLIO options (as we need to render a different one than a label)
  • is it time to make this a proper component?
  • refactor needed to 
    • remove relative-or-absolute component, including
    • replace with tokenised UUID picker and tokenised date picker
    • cleanup existing usages
• Components and Changes
  • Frontend: ui-dashboard relative-or-absolute component
  • Backend: none
• Tests / Data: new required
• Dependencies: none
• Known Unknowns: none
• QA: snapshot
• Development Estimate: 4d refactor + 2d tests

• Approach
  • simple frontend validation
• Components and Changes
  • Frontend: ui-agreements
  • Backend: none
• Tests / Data /  Dependencies / Known Unknown
• QA: snapshot 
• Development Estimate: deliver along with RTL Baskets

• Approach
  • looks like using an existing pattern for deletion: entitlement should be set to null
  • the lingering thing needs to be removed from entitlement line before rendering
• Components and Changes
  • Frontend: none
  • Backend: mod-agreements  
• Tests / Data: no change to entitlement log tests
• Dependencies: 
  • https://github.com/folio-org/stripes-components/pull/1674
• Known Unknowns:
  • does this need to be reflected in the similar original code within the export service?
• QA: snapshot 
• Development Estimate: 0.5d

• Approach
  • test whether api supports tertiary sort (on snapshot via postman)
  • if supported, change request in ui to add sort parameters
  • no requirement for adding UI to change sort options. No change to pagination.
• Components and Changes
  • Frontend: ui-agreements: AgreementViewRoute for agreement lines
  • Backend: web-toolkit-ce
• Tests / Data: na
• Dependencies
• Known Unknowns
  • is tertiary sort supported already in api?
  • does stripes-erm-components support more than two sort parameter values? (using generateQuery not getSas) ... not applicable
• QA: snapshot 
• Development Estimate

• Approach
  • ingest happens when mod-agreements launches and errors  are reported inside a job, appearing automatically when gokb harvest starts
  • remove the offending line
• Components and Changes
  • Frontend: none
  • Backend: mod-agreements
• Tests / Data / Dependencies
  • requires sample data and gokb synb
• Known Unknowns: none
• QA: snapshot 
• Development Estimate: <0.5d

• Approach
  • only applies to external resources
  • logic exists to work out whether an external resource
  • object should return whether it is selected
  • then extend label to show count
• Components and Changes
  • Frontend: ui-agreements, eresourceCount
  • Backend: none
• Tests / Data:
  • update RTL tests in eresourceCount
  • can delete the BigTests
• Dependencies / Known Unknowns
• QA: snapshot 
• Development Estimate: 0.5d

• Approach
  • use novalue component to handle aria labelling
  • if blank (null) then MCL and screenreaders should handle this
• Components and Changes
  • Frontend: ui-agreements, eresourceCount
  • Backend: none
• Tests / Data:
  • update RTL tests in eresourceCount
  • can delete the BigTests
• Dependencies / Known Unknowns
  • Gill to confirm UX consistency approach (- or null)
• QA: snapshot 
• Development Estimate: 0.5d

TODO

1. Ethan to comment with technical review / considerations
2. Gill to Review Reshare UI

• Approach
  • ReShare app settings already support configurations
  • Can display all settings dynamically or selectively build a  semi-dynamic or conditional settings page
  • Reshare UI is accepted to PO
  • Potentially add domain class to dynamically handle other app settings

Issue: 

• duplicate owner is added wrongly
• comma inserted in wrong place

Needs more triage - referring to Steve.

Use of owner with UUID is causing error 500, so should use owner.id.

Potentially a change to web-toolkit. 

Test Approach: 

• Source data has been fixed, so testing without faking the data is going to be problematic (faking or proxying)
• Set internal value to empty
• TODO: run integration tests
• QA: regression test 

Changes ready to go forward with existing indexes.

Delay is still around 7s.

PO concern: that a fix that would slow everything down might go in for an occasional or intermittent issue.

Affects any instance of repeated fields, where a package and resource are both attached to an agreement. 

TODO: 

• Ethan to get branch in good parked state
• Ethan to discuss with Ian about performance

Single line change (113) in ui-agreements.package.json

Verify with existing test suite, then raise 

See approach outlined in subtasks.

subtasks.

• Development work competed
• Initial regression testing setup to be started this sprint ...
• ... to enable frontend and regression testing in Sprint 129. 

Pending UX input