This is the design documentation for autonomous components that trigger on non-newspaper batches
The concept of a Batch is anything kind of object, which tracks events and which autonomous components can trigger on. The Newspaper Batch is a kind of object having these properties as representing a package of scanned newspapers.
Each Batch must have an EVENTS datastream.
In the SBOI Index, these fields will be indexed for each Batch
| Name | Description |
|---|---|
| id | The id of the batch, ie. B44000..-RT2 or edition name |
| doms_uuid | The doms pid of the corresponding record |
| success_event | repeatable. The successful events in the history of this batch |
| fail_event | repeatable. The failed events in the history of this batch |
| initial_date | The creation timestamp of this batch. |
| last_modified | The timestamp of the last modification, however you define this, of this batch |
| timestampFor<eventName> | The (latest) timestamp for the event of the given name |