Page History

...

The following tables have been added to the DSpace database. All tables are prefixed with 'xmlwfcwf_' to avoid any confusion with the existing workflow related database tables:

...

cwf_workflowitem

The xmlwfcwf_workflowitem table contains the different workflowitems in the workflow. This table has the following columns:

• workflowitem_id: The identifier of the workflowitem and primary key of this table
• item_id: The identifier of the DSpace item to which this workflowitem refers.
• collection_id: The collection to which this workflowitem is submitted.
• multiple_titles: Specifies whether the submission has multiple titles (important for submission steps)
• published_before: Specifies whether the submission has been published before (important for submission steps)
• multiple_files: Specifies whether the submission has multiple files attached (important for submission steps)

...

cwf_collectionrole

The xmlwfcwf_collectionrole table represents a workflow role for one collection. This type of role is the same as the roles that existed in the original workflow meaning that for each collection a separate group is defined to described the role. The xmlwfcwf_collectionrole table has the following columns:

• collectionrol_id: The identifier of the collectionrole and the primaty key of this table
• role_id: The identifier/name used by the workflow configuration to refer to the collectionrole
• collection_id: The collection identifier for which this collectionrole has been defined
• group_id: The group identifier of the group that defines the collection role

...

cwf_workflowitemrole

The xmlwfcwf_workflowitemrole table represents roles that are defined at the level of an item. These roles are temporary roles and only exist during the execution of the workflow for that specific item. Once the item is archived, the workflowitemrole is deleted. Multiple rows can exist for one workflowitem with e.g. one row containing a group and a few containing epersons. All these rows together make up the workflowitemrole The xmlwfcwf_workflowitemrole table has the following columns:

• workflowitemrole_id: The identifier of the workflowitemrole and the primaty key of this table
• role_id: The identifier/name used by the workflow configuration to refer to the workflowitemrole
• workflowitem_id: The xmlwfcwf_workflowitem identifier for which this workflowitemrole has been defined
• group_id: The group identifier of the group that defines the workflowitemrole role
• eperson_id: The eperson identifier of the eperson that defines the workflowitemrole role

...

cwf_pooltask

The xmlwfcwf_pooltask table represents the different task pools that exist for a workflowitem. These task pools can be available at the beginning of a step and contain all the users that are allowed to claim a task in this step. Multiple rows can exist for one task pool containing multiple groups and epersons. The xmlwfcwf_pooltask table has the following columns:

• pooltask_id: The identifier of the pooltask and the primaty key of this table
• workflowitem_id: The identifier of the workflowitem for which this task pool exists
• workflow_id: The identifier of the workflow configuration used for this workflowitem
• step_id: The identifier of the step for which this task pool was created
• action_id: The identifier of the action that needs to be displayed/executed when the user selects the task from the task pool
• eperson_id: The identifier of an eperson that is part of the task pool
• group_id: The identifier of a group that is part of the task pool

...

cwf_claimtask

The xmlwfcwf_claimtask table represents a task that has been claimed by a user. Claimed tasks can be assigned to users or can be the result of a claim from the task pool. Because a step can contain multiple actions, the claimed task defines the action at which the user has arrived in a particular step. This makes it possible to stop working halfway the step and continue later. The xmlwfcwf_claimtask table contains the following columns:

• claimtask_id: The identifier of the claimtask and the primary key of this table
• workflowitem_id: The identifier of the workflowitem for which this task exists
• workflow_id: The id of the workflow configuration that was used for this workflowitem
• step_id: The step that is currenlty processing the workflowitem
• action_id: The action that should be executed by the owner of this claimtask
• owner_id: References the eperson that is responsible for the execution of this task

...

cwf_in_progress_user

The xmlwfcwf_in_progess_user table keeps track of the different users that are performing a certain step. This table is used because some steps might require multiple users to perform the step before the workflowitem can proceed. The xmlwfcwf_in_progress_user table contains the following columns:

...

Additional workflow steps/actions and features

...

Optional workflow: Select single reviewer workflow

In this workflow a single user is assigned to review an item and consists of 2 steps.

• AssignStep: During the assignstep, a user has the ability to select a responsible user to review the workflowitem. This means that for each workflowitem, a different user can be selected. Because a user is assigned, the task pool is no longer required.
• ReviewStep: The start of the reviewstep is different than the typical task pool. Instead of having a task pool, the user will be automatically assigned to the task. The user has however the option to reject the task (in case he is not responsible for the assigned task) or review the item. In case the user rejects the task, the workflowitem will be sent back to the AssignStep allowing the responsible to select another user for the review.

Optional workflow: Score review workflow

The score review system consists of the following 2 steps.

• ScoreReviewStep: A group of responsible users for the score reviewing will be able to claim the task from the taskpool. Based on the config, a different number of users can be required to execute the task. This means that the task will be available in the task pool until the required number of users has at least claimed the task. Once everyone of them has finished the task, the next (automatic) processing step is activated
• EvaluationStep: During the evaluationstep, no user interface is required. It will be an automatic step executed by the system that evaluates the different scores. In case the score is more than 50%, the item is approved, otherwise it is rejected.

Workflow overview features

...