WebUI

Architecture

• The User Interface talks to the Backend via API. See API Documentation
• The Web Ui is build with Sveltekit ⧉

graph TB
    subgraph Webplatform
    direction TB
        A[Political Debates Backend]
        B[Political Debates UI]
        C[(Political Debates MongoDB)]
        D[(Political Debates Solr)]
        E[(Political Debates S3)]
        A -- annotate --> C
        A -- search --> D
        A -- signed urls --> E
        B -- api --> A
    end

User Roles

Currently the User interface has no Authentication added. In a Server installation we installed two password protected users: (see nginx folder)

• reader: can only view the page
• editor: can add annotation on the media player page

You also have these roles in other installation mode, by just going on the routes:

• /edit: is the route for the editor role
• /: switches to the reader role.

Homepage Editor

Homepage of the Editor User available at /edit

Homepage Reader

Homepage of the Reader User available at /

Search Page

Search interface to make speaker statements searchable available at /search

Mediaplayer Page as Editor

Media player detail page for the reader user to compare transcripts and translations

Mediaplayer Page as Reader

Media player detail page for the Editor user: the editor user can correct the transcripts and translations and add speaker name and Role