Bulk exclude backlogged reportbacks on node 362

[mikefantini]

FEATURE OVERVIEW

User Story

As an admin, I want all fids on node 362 with a quantity under 200 to be marked as excluded before it relaunches on Thursday.

Additional Information (optional)

Campaigns team was trying to go through the backlog and the number of reportbacks went from ~600 to ~1500. Got these numbers from Lizzy. 600 felt doable, 1500 seems unreasonable between now and then. Also a few reports of "Illegal choice detected" error when intern was running through things.

Why This Matters

Since campaign relaunches on Thursday and reportbacks are listed as oldest to newest the campaigns team won't realistically be able to get to current reportbacks without this being cleared out. Only other option I can think of is that we adjust the script to include only reportbacks that match one of the previous run ids which would buy us a little time I suppose and allow us to get the work done later this week.

@angaither let's chat about this in the AM

[chloealee]

@mikefantini I'm not sure what you mean by all "fids with a quantity under 200 to be marked as excluded" - isn't quantity attached to reportbacks, not reportback items?

Also, admins review these reportbacks at /node/362/rb?

[mikefantini]

@chloealee right sorry I guess the FIDs are what need to be marked as excluded and we should do that for any that are currently pending and associated with RBIDs with a quantity under 200

[namimody]

From what I understand, four things need to happen:

• all FIDs associated with a RB with a quantity under 200 get marked as "excluded"
• these photos no longer appear in the queue
• these RBIDs should have a status of 0 in the DB
• FIDs associated with RBIDs with a quantity 201 and over should still be pending and appear in the inbox with a status of NULL

Might also be worth checking if there are any RBIDs with some photos that have been reviewed and some still in the inbox so that this fix works for those edge cases.

[mikefantini]

@namimody @chloealee one caveat to the above, we only want FIDs that are currently pending and quantity under 200 to be marked as excluded.

i.e. if an FID is already approved, we don't want it to change to be excluded.

[mikefantini]

Also if the RBID is already 1 we don't it to change to 0.

[namimody]

Thanks @mikefantini! So then this work should only touch RBIDs with status NULL? cc @chloealee

[chloealee]

@mikefantini @namimody should this be ONLY for node 362 or for all campaign nodes?

[namimody]

Only 362 @chloealee!

[chloealee]

cool, thanks @namimody !

[mikefantini]

@namimody I'm pretty sure that flagged status can stay 0 or 1 for a file that is pending. Consider if it's a second file on an existing reportback that had a file that was previously reviewed.

i.e. fid 1 is approved and rbid flagged status is now 0. fid 2 (2nd file on the same reportback) is pending but rbid flagged status is still 0. So I'm pretty sure you need to look for all files with status pending regardless of whether flagged status is 0, 1, or NULL @chloealee

[namimody]

Ohh now I follow @mikefantini -- so even if we make mark files of partially reviewed reportbacks as excluded, their RBID status will stay 0 or 1. Therefore, I think should be comprehensive?

• all not yet reviewed FIDs associated with a RB with a quantity under 200 get marked as "excluded"
• these photos should no longer appear in the queue
• these RBIDs should have a status of 0 or 1 in the DB (depending on if other assoicated FIDs have been reviewed and been marked as approved/excluded/promoted or flagged previously)
• unreviewed FIDs associated with RBIDs with a quantity 201 and over should still be pending and appear in the inbox

cc @chloealee