New approach to Processe and Process Template management
In Goobi, 'process' defines a digitization project for a single master document (or artwork). Processes are created regularly and often share a lot of specifics. Therefore some processes serve as 'templates' for process creation (cloning). However, this leads to confusion, as those templates implement process behaviour as well (are called processes, have a state, can be worked on).
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This is particularly important for automation and should implement the following behaviour:
• Open automated steps of processes should be immediately executed by the system while open automated steps of process templates should never start working, not even if open.
• Setting an automated step of a process to „open“ state should trigger its execution [again] while not doing so for templates.
• An open automated step of a template should be cloned upon process creation and then immediately be executed for the newly created process after its successful creation.
-- Matthias Ronge, Zeutschel, 2013-03-14
