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
How to navigate to a specific workflow? Query param, or URL? #806
Comments
I don't think we need to do this for TESS because they only need one active workflow and the new one will be set as the default workflow. We'll still need to support workflow selection if a user hits a As an aside, moving to a regular URL means we can also cleanly support subject set selection this way too, |
|
I like the idea of redirecting so that volunteers can bookmark a specific workflow. This probably ties into our discussion the other day about how to deal with completed workflows too. The URLs should still work but maybe the classifier changes to indicate that the workflow is complete. |
The redirect could trickle down the selection priorities we have: UPP (if signed in), default, random active. If none work, then prompt the user with a 404 and ask them what to do by showing the available options for the current project or prompt to try another project. |
CSSI CitSci has a use case to allow volunteers to be able to load a specific subject by url to classify, so I think we can plan on supporting this similarly: |
Following the discussion in #1077 (comment), we need to ADR this up first. |
Currently, PFE derives the workflow from the URL query parameter. We've been talking about moving to a regular URL, something like
/owner/project/classify/workflow/[workflow_id]
instead.I prefer the latter - it's a static resource, which is what a URL is for.
We should to make a decision on this, since it has deployment implications for TESS.
cc @srallen @camallen @eatyourgreens
The text was updated successfully, but these errors were encountered: