User Stories — Cloud Sync (Processor)¶

Service: Processor (Cloud-Sync-Worker) · Tier: 1

US-U01: Automatically back up recordings to the cloud ☁️¶

As a researcher I want my recordings to be automatically uploaded to a remote storage (e.g., Nextcloud, S3), so that my data is safe even in case of device loss, theft, or hardware failure.

Acceptance Criteria¶

[x] New recordings are automatically detected and uploaded to the cloud — without manual intervention.
[x] Before upload, files are losslessly compressed (FLAC) to save bandwidth (~50% smaller).
[x] After confirmed upload to the configured remote target, the file is marked as "uploaded" in the database (uploaded=true).
[x] The device also works without an internet connection — recordings are stored locally and caught up upon connection (Store & Forward).

References¶

US-U02: Record indefinitely ♾️¶

As a user I want to ensure that uploaded recordings may be automatically deleted from local storage, so that the station can record continuously for months or years without manual intervention.

Acceptance Criteria¶

[x] After confirmed upload to the configured remote target, the system marks the file as backed up (uploaded=true).
[x] The storage cleanup service (Janitor) may only delete files marked as "uploaded" (→ US-P02).
[x] The interaction of upload and cleanup permanently keeps local storage below critical thresholds.
[x] In case of a permanent lack of internet connection, the Janitor still intervenes — recording always takes precedence over archiving.

References¶

US-U04: Adjust upload settings via web interface 🎛️¶

As a user I want to be able to change upload settings (bandwidth, time window, storage targets) via the web interface, so that I adjust the upload to my network situation and needs — without SSH or config files.

Acceptance Criteria¶

[ ] Bandwidth limit is adjustable (e.g., "max 1 MB/s") to avoid overloading the internet connection.
[ ] A time window for uploads can be defined (e.g., only at night from 22:00–06:00) to save bandwidth during the day. Default Bandwidth limit off!
[ ] A storage target can be configured via the web interface.
[ ] Changes are automatically applied — the upload service restarts if necessary.

References¶

US-U05: Upload progress and status in dashboard 📊¶

As a user I want to see in the dashboard how many recordings still need to be uploaded and whether there are problems, so that I can assess the cloud sync state of my station at any time.

Acceptance Criteria¶

[ ] The dashboard shows: number of pending uploads, current upload speed, and last successful upload time.
[ ] A warning is shown for failed uploads (e.g., "Connection to Nextcloud failed for 2 hours").
[ ] Status can be viewed for the configured remote target.
[ ] The upload service reports its status periodically to the web interface.

References¶

US-U06: Seamless upload tracking 📋¶

As a researcher I want to be able to trace at any time which recordings were uploaded when and where, so that I am certain no data was lost on the way.

Acceptance Criteria¶

[x] Every upload attempt is logged — success, failure, file size, duration, and target.
[ ] The upload log is viewable via the web interface.
[x] Failed uploads are automatically retried.
[ ] Persistently failed uploads are shown as a warning in the dashboard (→ US-U05).

References¶

Processor Service Docs

[!NOTE] Recording Protection: This service must not impair the ongoing recording. Resource limits, QoS prioritization, and file isolation are managed centrally by the Controller (→ US-C04, US-R02).