[Scrum] - SUSI Interpretation Project - 20260729

[Eshaan Walia]

1. What did I do yesterday?

• (eventyay-interpretation) - Updated PR (#48) - Redesign commons interpretation dashboard UI (PR 5/5)

• Rebased onto email-password; inherits fix via forms.py

• (eventyay-interpretation) - Updated PR (#46) - Add email/password login to connect events to SUSI

• Added a URL guard in run_test_action to prevent SusiClient with a blank URL.

• Added a test to verify a blank URL shows an error and doesn't create a client.

• Ensured settings.flush() is called in save tests to verify persisted settings.

• (eventyay-interpretation) - Updated PR (#44) - refactor: store SUSI connection in per-event settings

• Update

1. Updated dashboard tests for the new event settings API.

2. Added validation and settings tests.

3. Updated test payloads to use interpretation_* fields.

4. Fixed CI issues (Ruff, formatting, imports).

• Bug Fix

1. Fixed "Save & Test" crashing when no URL was provided.

2. Added validation to show a proper error instead of a 500.

3. Added a regression test for this case.

• (eventyay-interpretation) - Updated PR (#41) - feat: add interpretation models and connection dashboard scaffold

• Added dashboard POST tests for the new models dashboard scaffold.

• Added shared test fixtures for users, events, dashboard client, and interpretation plugin.

• Added tests for:

1. Save settings successfully.

2. Save & Test with a valid connection.

3. Save & Test with an invalid token (shows warning while still saving settings).

2. What do I plan to do today?

Prepare for merge:

• https://github.com/fossasia/eventyay-interpretation/pull/44

• https://github.com/fossasia/eventyay-interpretation/pull/46

• https://github.com/fossasia/eventyay-interpretation/pull/48

Test voxbento locally, familiarise
Add voxbento in the interpretation plugin with susi in a multimodal approach

PR-s summary: Parent Issue #17: Merge order: 1 → 2 → 3 → 4 → 5.
  PR 1 : m1-susi-client (merged #40)

  HTTP client for SUSI API: login, verify token, create session.

  PR 2 : m1-models-dashboard-scaffold (merged #41)

  SusiConnection model + commons dashboard to save URL/JWT and test connection.

  PR 3 : m1-event-settings (open #44)

  Drop SusiConnection table; store URL/token/enabled in per-event settings instead.

  PR 4 : m1-email-password-connect (open #46)

  Replace JWT paste with SUSI email/password login; connect, disconnect, test buttons.

  PR 5 : m1-dashboard-redesign (open#48)

  Redesign entire interpretation commons dashboard UI/UX (layout, CSS, provider picker).

3. What is blocking me from making progress?

No Blocker at the moment