Additional datafile filters

[ADPennington]

Description:
To further specify which files need to be re-parsed, sys admins need more granular control.

Acceptance Criteria:
Create a list of functional outcomes that must be achieved to complete this issue

• Datafiles DAC page has granular options for narrowing/expanding datafile search per Notes
• Testing Checklist has been run and all tests pass
• README is updated, if necessary

Tasks:

• Enable stacking/OR-ing of multiple filters of same type (e.g., I want all datafiles from Florida or Georgia in my query) Implemented via multi-select Integrate multi-select filtering with Django 508 query string mechanism #3183
• New Datafile filter for type (state, tribe, territory)
• New Datafile filter for region -- likely same cross-link of datafile and STT objects as above
• New Datafile filter for "latest" -- must be combined with other filter(s). We don't want to re-parse v1,v2,...,v35 of a file so the latest filter would be after the other filters return a queryset of datafiles, only cherry-pick the highest version of each.
• New Datafile filter for program type (we currently have section (SSP Active))
• New Datafile filter for section (piggybacks on above task)
• Run Testing Checklist and confirm all tests pass

Notes:

• Current filtering is "AND" logic which will provide a non-intuitive interface. The first task for stacking/OR-ing conditions is paramount to success.

• _Requested filters:

  • file id (e.g. 2053, lst)
  • STT (e.g. Alabama, lst)
  • STT type (e.g. tribe, lst)
  • region ( i.e. a set of STTs in a particular region)
  • program type (e.g. TANF)
  • most recent file version (e.g. latest)
  • processing status (e.g. pending)
  • section (e.g. Active Case Data)

Supporting Documentation:

• Please see MVP impl. via PR Re-parse Command #3041

Open Questions:

• how best to handle the scenario where parameters passed are in conflict (e.g. STT type = tribal and region = 1 (has no tribes)?
  • Utilize confirmation dialog from Re-Parse Django Action  #3106
  • Can we safely rely on a downstream system to handle contradictory parameters as suggested? If using DRF filtering, we could just end up with 0 files and say nothing to do.
  • Should we have an Ansible-like "preview" function?
    • To be encoded as part of Re-Parse Django Action  #3106

[andrew-jameson]

'Latest' being implemented in #3139