Enhance Tracker with algorithmic troubleshooting recommendations

[bthuronyi]

Based on our own understanding or ideally on analysis of previous debug steps, suggest concrete steps to users in Tracker for constructs that need troubleshooting, then rank troubleshooting jobs by complexity and validity of recommendations

[bthuronyi]

Case we've commonly encountered: assembly, 1 attempt, no colonies after transformation; one or more PCRs probably failed

• check QC on PCRs and set to high priority QC
• requeue whichever PCRs look like they failed, if one or more has evidence of failure
  • consider QC data and also "assembly success" flag on Status to discriminate
  • if the construct is Priority and there aren't too many PCRs, consider requeueing ones where there's no evidence yet either way, just in case they didn't work
  • if all but 1 or 2 PCRs has evidence of having worked, requeue the remaining 1-2 PCR(s) even without QC data
• formula should provide specific details about which identifiers to requeue and how to do so
• formula should provide automated debug text to copy and paste, if the user did exactly what was recommended

[bthuronyi]

We can consider supplying a new tab on the Tracker to provide debug advice, because it can be set up to accept a construct name and devote an entire tab -- with multiple rows/columns -- to giving recommendations for it. This can include presenting requeuing-related fields to copy/paste directly into CC!

[bthuronyi]

The Tracker can algorithmically incorporate the same outputs we currently generate manually using this accessory sheet: https://docs.google.com/spreadsheets/d/1I2RFVfZp7SELgt65I9a8CgkF15clonKvlFgq4ZidMbw/edit?gid=282150589#gid=282150589

Checking for track records of each dID to decide which are probably ok and which are suspicious

[bthuronyi]

Similar approach can use Golden Gate "whitelist" data as well as part track records to suggest changes