This should encompass the re-write of the duplicate chron job following the steps here
Get all duplicate keys from the view.
Go through the above response and filter it into two groups, one with unique IDs only and one with repeats (where the same group matches both email and name/dob).
Go through each group and see if a flagged set exists.
Add applications an open listing. Preferably with an assortment of applications that would cause several flagged sets.
Easiest way to check the duplicates is to wait for the job to run (currently set to the 40 minute mark of every hour but I can increase the frequency if need be)
Blocked by this
This should encompass the re-write of the duplicate chron job following the steps here
Notes:
TDD here