Database backed logbook

Registered by Joshua Harlow on 2013-06-06

In order to provide persistence of tasks and there results (and stages) we need to be able to keep the records of the tasks in a persistent storage (which may vary per logbook type, via the catalog mechanism). This will allow for workflows which fail (say by having a machine crash) be able to be resumed by restarting that workflow elsewhere (and referring to the logbook to know what stage/workflow/task was left off at).

Blueprint information

Status:
Complete
Approver:
Joshua Harlow
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
Joshua Harlow
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Joshua Harlow on 2013-06-06
Completed by
Joshua Harlow on 2013-08-24

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.