• Triage

• Approach
  • Use has  and has not  instead of 1 or 0, etc
  • use default logic of AND taking precedence over OR
  • preserve filter state in url
    • AND/OR filter options cannot be added until validated
  • no ux for non-valid filters in ERM
    • Use apply button to trigger validation only if needed. 
    • Clear invalid filters 
  • May need arrayMutators in a form for field arrays

• Components and Changes

  • Frontend: ui-agreements, may need changes to SKC

  • Backend: NA

• Tests / Data / Dependencies

  • add unit test on new filter component
  • interactors for future integration tests

• Known Unknowns:

  • final-form or form: if ff, will need state arrays

• QA: snapshot 

• Release Target: Poppy

• Development Estimate

• Approach

  • parallel batch fetch users (and user names), using component from stripes-erm-component
  • pagination is complicated for users as user fetching is an upfront check for permission verification - fetch 100 at a time, without max limit (ie, use default of infinity)

• Components and Changes

  • Frontend: ui-dashboard

  • Backend: none

• Tests / Data / Dependencies: NA

• Known Unknowns: NA

• QA: snapshot 

• Release Target: Poppy

• Development Estimate: 

This would enable pushKb testing against Gokb data sources, independent of FOLIO release cycles

• Triage

  • migration - what to do with existing titles
  • ingest from multiple sources: preventing title duplication
  • currently don't save gokb uuid
  • would be three cycles before using id 
  • class 1 namespaces are not checked in any breaking/switching order, so title would have to be promoted as first match check (though that would remove then re-add titles) 

More discussion needed to thrash out consequences.

May not be technically feasible. Needs investigation to determine approach. 

• relationshipTypes will need to become frontend translations
• Cannot currently be omitted/suppressed from picklist dropdowns (as this is dynamically generated)
• Not expecting these to be user editable
• In the future (so out of scope now), instead of using as refdata, should use domain class that uses refdata for the relationship types. 

Initial testing worked so far - successfully pushed package info.

TODO: Add test plan info to issue (started)