Closed shaunanoordin closed 1 month ago
Looking good! I'm able to follow all of the testing steps above at the preview link: https://pr-7079.pfe-preview.zooniverse.org/lab/1982/workflows/editor/3711?env=staging (note that your Testing Steps section links to an older PR's staging, but I figured it out!)
A couple of questions for clarification:
While all of the conditions listed in the Testing Steps work in the UI, what is the reasoning behind disallowing the combo of Single Answer Question + more tasks in the same step? I understand the logic behind disabling buttons when branching is involved, but I want to make sure I understand why only "a" is disallowed in the following step scenarios:
I'm willing to bet ya'll discussed the decision at length during Pages Editor meetings, so I apologize for asking for receipts π but please point me to documentation if it already exists.
When I add only one task (and therefore only one step) to a workflow, the dropdown below the step or the dropdown below each answer includes T0
. Project teams should not be able to recursively select T0
when there's only one task, is that correct?
Revisiting my comment above because we talked through the reasoning behind "each single answer question gets its own page" during the weekly call. It was initially implemented this way to accommodate the fact that Single Answer Question tasks can branch, but Multiple Answer Question tasks cannot.
@shaunanoordin do you plan to update this PR with different rules for adding question tasks to their own page, or should I go ahead with review as is?
@goplayoutside3 Thanks Delilah! π
re: "each single answer question gets its own page", your assessment is on point. π
re: "should a Page's/Answer's Next Page be able loop back to itself?" (i.e. can T0 go to T0?) That's a good question. Currently, the PFE/FEM Lab Project Builder does allow a Task T0 to set its next task as Task T0. This is true whether it's a branching/single-type Task or a non-branching Task. Does it make sense? Not really. I'll add this to the list of questions to ask, but once we get confirmation, implementing a "you can't loop back in on yourself" rule is fairly trivial.
Caveat: while a one-step loop of T0->T0 doesn't make sense, there is a case for a two-or-more-steps loop of T0->T1->T0. e.g. T0:"Do you see any more colours that haven't been identified?" Yes=> go to T1, No => submit
and T1: "Type in the name of the colour you see" => go to T0
Next Steps:
Re. tasks linking to themselves, check out:
if a Step already has at least one task, any added Question task must be a Multiple Answer Question Task.
Sorry, just a question out of curiosity but does this stop you from building transcription workflows, which combine a drawing task and a yes/no question into a single step?
Sorry, just a question out of curiosity but does this stop you from building transcription workflows, which combine a drawing task and a yes/no question into a single step?
Transcription Tasks are whole different kettle of fish: they fall into something called "Pre-defined Pages" which is something we're planning for phase 2.
PR Overview
Part of: Pages Editor MVP project and FEM Lab super-project Follows #7075 Staging branch URL: https://pr-7079.pfe-preview.zooniverse.org/lab/1982/workflows/editor/3711?env=staging
This PR adds special rules for the "Add Task to Page" functionality. (See #7065)
The overall rule is this: a Step can only have 1 branching task (single answer question task)
(New behaviour) The specific sub-rules are:
if a Step has a branching task, it can't have any other tasks. Screenshot: The "Add New Task to Page" button is disabled when (and only when) there's a branching ('Single'-type) Task.
if a Step already has at least one task, any added Question task must be a Multiple Answer Question Task. Screenshot: no visible changes, but clicking 'Question' will add a 'Multiple'-type Task, instead of a 'Single'-type Task
if a Step already has many tasks, any Multiple Answer Question Task can't be transformed into a Single Answer Question Task. Screenshot: 'Allow multiple' checkboxes are disabled for all Question tasks on pages with > 1 tasks.
Other changes in this PR:
FAQ
Q: how do I visually tell the difference between a Single Answer Question Task (aka "Single"-type Task) and a Multiple Answer Question Task (aka "Multiple"-type Task) on the Pages Editor? A: check whether the "Allow Multiple" checkbox is ticked. Also, "Single"-type Tasks allows you to choose the next page for each answer, not for the whole page.
"Single"-type Task:
![image](https://github.com/zooniverse/Panoptes-Front-End/assets/13952701/771fa051-2df6-4ed6-ac89-93171ce57696)
"Multiple"-type Task:
![image](https://github.com/zooniverse/Panoptes-Front-End/assets/13952701/4044129f-cba0-48d8-b5ab-c716aeb1849b)
Testing Steps
It's also worth running some quick basic tests to make sure the refactor works as expected:
Status
Ready for review. π
EDIT: ready to review from a functional standpoint Improvements I could/should add to this PR: