• Approach

  • add to package schema
  • add fields to ingest 
  • update adaptor

• Components and Changes

  • Frontend: none

  • Backend: mod-agreements

• Tests / Data: packageViewSpec.groovy 

  • add to existing JSON object
  • add new test for fields/filters (on Set) 
  • add new test for update

• Dependencies: ERM-2288

• Known Unknowns: 

• QA: snapshot

• Development Estimate: Monday

• Approach

  • explicitly comment the behaviour /  business rule in the code
  • Add logic (if / elseif) inside adaptor

• Components and Changes

  • Frontend: none

  • Backend: mod-agreements (adaptor)

• Tests / Data: none

• Dependencies: ERM-2306

• Known Unknowns: none

• QA: snapshot

• Development Estimate: == ERM-2311

• Approach

  • explicitly comment the behaviour /  business rule in the code
  • Add logic (if / elseif) inside adaptor

• Components and Changes

  • Frontend: yes

  • Backend: none

• Tests / Data: none

• Dependencies:

  • ERM-2306

  • Gill to review frontend mockups based on ERM-2306 shape

• Known Unknowns: none

• QA: snapshot

• Development Estimate: == ERM-2311

• Approach

  • lookup the refdata
  • query refdata
  • filter on list
  • use selection rather than checkboxes doing lookup
  • publicationType is checkboxes - so, OR'd in filter, rather than AND
  • no default to be set 
  • no lookahead for now

• Components and Changes

  • Frontend: ui-agreement

  • Backend: none

• Tests / Data:

  • if we already have existing filter tests

• Dependencies: ERM-2306

• Known Unknowns

  • list size may encourage select rather than checkboxes
    • expecting to be in the order of 10s, rather than 100s

• QA: snapshot 

• Development Estimate: 1d

• Approach

  • add new logic to packageIngestService lines 212-218
  • ensure save after block
  • use existing patterns for updating PTI

• Components and Changes

  • Frontend: none

  • Backend: mod-agreements packageIngestService 

• Tests / Data: package test data

• Dependencies: no

• Known Unknowns: none

• QA: snapshot 

• Development Estimate: small

Approach:

• Can mock pluggable to check if plugin shows up
• Check if card is displayed

• Approach

• Components and Changes

  • Frontend

  • Backend

• Tests / Data

• Dependencies

• Known Unknowns

  • Sorting: not expected for volumes of users expected in list (~10)
  • Is name handed from Users as a single name, or first/last name?
    • To be consistent across FOLIO, we should keep separate
  • Out of scope: giving user list access to non-manager users
  • Does Users pre-filter out inactive users?

• QA: snapshot | local | testing | other

• Development Estimate

• Current State
  • No progress started
  • Previously rewritten to a single component
    • that may be covered for tests
• TODO
  • extend getResourceIdentifier() with a returnAll boolean parameter (stripes-erm-components)
  • tweak test for getResourceIdenitifier
  • update ui-agreements to apply logic
  • add tests to eResourceIdentifier to check multiple cases
• Development Estimate: <1d

• Approach

• Components and Changes

  • Frontend

  • Backend

• Tests / Data

  • No tests to be written

• Dependencies

  • Should amend the current behaviour to not create a new dashboard in the backend, so a user comes to a splash screen on first access
    • Ethan to stub an issue for Owen to review and prioritise after ERM-2314
    • Est: 0.5d to add a splash screen once 2314 is done

• Known Unknowns

  • How will the order weight interact? Requires API.

• QA: snapshot | local | testing | other

• Development Estimate