ISISComputingGroup / ISISComputingGroup/DataStreaming
Data streaming: write journals
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Acceptance criteria
- Python or rust process implemented as a standalone python package (e.g. see packaging for `ibex_bluesky_core`/`genie`/`lewis` for how to do this) or rust project
* e.g. named `kafka_dae_journals`, to sit alongside `kafka_dae_control` and `kafka_dae_diagnostics`
- Listens to a kafka stream for run stop messages
- Update a `journal.xml` file with metadata from the run when a [`wrdn`](https://github.com/ess-dmsc/streaming-data-types/blob/master/schemas/wrdn_finished_writing.fbs) is published - this then needs to read the file and pull out the journal metadata.
- Format of written `journal.xml` should match existing `journal.xml` as closely as possible.
- Create a follow up ticket to test against Journal Viewer (currently some missing data)
### Notes
- Some metadata won't currently be available from kafka. Create new ticket(s) for these cases. For this ticket, write the data which is _currently_ available from kafka run start/stop messages and corresponds to a field in the `journal.xml`. Create follow up ticket(s) for data not currently available.
---
Discussed Planning 08/01/2026 14:30
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.