|
All content with label workflow.
Related Labels:
groups, requirements, osp, specifications
Assignment Workflow
(Contrib: Assignments2)
Draft in progress With the exception of the initial authoring of an assignment description, the submission workflow is an exchange between the submitter and reviewer. From the varieties of assignment object and user interaction arise four main workflow stages, with perspectives varying by user: (A) Submitter's ...
Other labels:
specifications
|
Group Assignments
(Contrib: Assignments2)
Group assignments take one submission object from each group, and this can be managed by either specifying which group member will make the submission on behalf of the group, or allowing anyone in the group to make a submission on the group's behalf. Group assignments often ...
Other labels:
groups
|
Workflow
(DG: Development (a.k.a. sakai-dev))
Motivation Bringing in a thirdparty workflow engine would allow us to: better support workflowlike activities with a mature standard minimize the quantity of siloed Sakai code which seeks to handle workflowlike activities in each particular case There is not a wealth of complex workflows ...
|
Workflow Breakout Group
(Project: Portfolio)
High level requirements Time Driven Goal Driven Iterative Intuitive central location Guided Supports Cross Site integration Supports Artifact Persistence over Time spans terms, years, etc Includes Time and Activity Based Notification ...
Other labels:
osp, requirements
|
Workflow Use Cases
(Contrib: Assignments2)
legacy assignments tool assumes a very straightforward submissionfeedback workflow. A number of pedagogies chafe against these shackles, and it's worth laying out some alternative workflow use cases. Greater flexibility in review workflows also increases the value of an "assignments ...
|
|
|
Label: workflow