-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pages Editor: UI tweaks, improved Workflow Settings #7093
Conversation
PR Update
|
619bc83
to
16b0df0
Compare
68740ea
to
a197faf
Compare
|
||
return ( | ||
<div className="workflow-version"> | ||
V. {workflow.version} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I moved tasks around and changed settings, the version does update 👍 Do you know off the top of your head, is this versioning only used by the classifier to check if it should re-render? Do project teams actually track version number for any other reason?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, this is a good one. OK, so, workflow versions:
The workflow version is intended for the project owners, AFAIK. Project owners are supposed to keep track of the version numbers, so they can match it to answers/classifications from the volunteers.
Example: v8.1 of a workflow has Task T1: "Do you see a cat?". Researcher then changes it to T1: "Do you see a feline of any sort?", which updates the workflow to v8.2. If it matters to the researcher which variant of the question the volunteer is asking, they can filter between the responses by checking classification.metadata.workflow_version
in the classifications export.
As far as I can tell:
- Workflow version is in the format of
major_number.minor_number
- The major version is increased when: (i) a task is added, (ii) a task is deleted, (iii) the "next task" of a task is changed, (iv) the "next task" of a question tasks' answer is changed, (v) the workflow.first_task is changed.
- The minor version is increased when: (i) a task is edited (any attribute such as 'task.question' is changed, asides from 'task.next' or 'questionTask.answer[x].next')
- i.e. major versions when the overall structure/flow of Tasks are changed, minor versions when any one Task is modified.
- ❗ NO version changes occur when steps/pages are changed. 🤨 (Wait, hang on... what?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now an issue for discussion on Panoptes: zooniverse/panoptes#4340
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! I really like that I can drag tasks and the order is sorted linearly for me. I used https://pr-7093.pfe-preview.zooniverse.org/lab/1982/workflows/editor/3711?env=staging to review the UX, and have a few non-blocking UX things to double check with you:
-
I can use
tab=settings
in the url to immediately show the Workflow Settings tab on load. However, once I click the Tasks tab, the param remains unchanged in the url. If thetab
param influences the UI, do you want the UI to influence thetab
param too? -
In the Workflow Settings tab, when I load the above workflow in the classic
femLab
, the "show separate frames as" radio button for single column is selected, which I believe is the default.
However, in this PR branch there's no selection in that setting for the same workflow:
Once I clicked an option, now the workflow shows a selection in the Pages Editor, but the Pages Editor UI should show the default separate frames orientation selection on workflow creation. -
In the above screenshot of separate frames options in the Workflow Settings, the description of each option is using 10px font. That's smaller than PFE and Sean's Figma design shows 16px for the descriptions. I'd err on the side of Sean's design for readability.
…xperimental tool now resets workflow.configuration as well.
a197faf
to
4bac969
Compare
Thanks Delilah! 👍 Updates & responses: Item 1: should the Item 2: when "Separate Frames" options are enabled, the "single column" layout should be the default. In practice (and following PFE logic) this means that, if Item 3: the small help text in the "Separate Frames Item 4: how do workflow versions work in regards to workflow.steps? |
PR Overview
Part of: Pages Editor MVP project and FEM Lab super-project
Follows #7088
Staging branch URL: https://pr-7093.pfe-preview.zooniverse.org/lab/1982/workflows/editor/3711?env=staging
This PR combines a number of UI tweaks and updates to the Workflow Settings. The UI changes makes the visual presentation closer to Sean's intended design, while the Workflow Settings changes make that tab ⭐ on par with the Project Builder FEM Lab's functionality. (comparative link)
Part 1: UI changes
➡️
➡️
Part 2: Workflow Settings Tab
?tab=settings
to the URL?tab=settings&showRemovedOptions=true?tab=settings&advanced=true
to the URLMisc Changes
status
value changes. This wasn't tracked previously!workflow.configuration
Update 1 (link)
?advanced=true
. (Use this to enable manual/non-linear workflows, and the Experimental Panel)Testing
No specific tests recommended. Just check that general functionality is maintained, and the code makes sense.
Status
Ready for review. 👌
Requires 7088 to be merged first before this can be merged.