Stealth: Tasks Page

[cookiengineer]

Stealth needs a new stealth:tasks Page that shows the overview of scheduled tasks that are regularly run, and a manual tasks overview. A task is a new data structure that also should be integrated as a Task Service, and should also be able to be delegated via trusted Peers.

A task probably will consist of the following properties:

• date (DATETIME compatible network date)
• time (DATETIME compatible network time)
• interval (DATETIME compatible network time)
• type (browse, download, extract)
• url (URL link)
• beacon (select a beacon by url pattern, allow to search for it)
• export (CSV path, JSON path, default: null -> cache)

The stealth:tasks Page should at least contain these features:

• Create Interface for a new Task (to add it to the todo list)
• Overview of Manual Tasks (as a todo list)
• Overview of scheduled Tasks and their time/date properties

[cookiengineer]

Additionally, scheduled tasks need support to follow links given a specific URL pattern. This specifically results in a UX problem, where it's currently unsure how to integrate the following of links without a guidance in the form of an assistive sidebar that lets the user select specific URLs by examples (e.g. by selecting them via the mouse or via touch).

The question is now whether or not the beacon sidebar can handle this. If a beacon can extract links on an index/overview page, a task could be automated via delegation of the extracted links with another step; but how would this data be stored or transferred from one task to another?

It might be necessary to integrate a special pursue (or follow?) type task for this that allows to select URLs for other tasks automatically via a specified Beacon. If this beacon extracts a list of URLs, then the other tasks are executed directly after it was finished.

In order to implement this workflow automation, it might make sense to implement a stealth.Task that's reusable in a similar manner to a stealth.Request, but focusses on potential endless loops and quirks; and is implemented in an evented manner so that it can prevent those edge cases.