Should we let the workflow route reroute to different steps in the workflow?

[jabrah]

Currently, all of the steps of the deposit workflow are child routes of the submission.workflow route (submission/new in the URL). Imagine if we have a part of the Ember app intentionally transition to the submission.workflow parent route, instead of a specific workflow step. Would we want to give this parent route some logic to check a submission's state to infer which workflow step the user should be routed to?

Routing could be (but not limited to) data such as

• Presence of signed agreements
• Furthest step reached
• SubmissionActions for metadata and/or files

Currently, the submission's state data is completely undefined, so we have some freedom about what goes in there. Some information needed for this inspection could potentially exist in the state data, although I can see some potential information that would need to be taken into account that could not be in the submission state, such as curator reviews that require user input in the workflow metadata step

[htpvu]

are you asking if we'd want to let some actor jump back and forward in the workflow without going through the sequential step?

If that's the question, then i would say no.

If that's not the question, i'll have to catch up with you because i'm not sure I understand the question.