Feat: Annotations tables for peer-review submissions and other annotations

name: Feature Request
about: Suggest a new feature or enhancement for the Corpus Collector Backend.
title: "[Feature]: New annotation model for the peer-review submissions and other task specific annotations"
labels: "feature"
assignees: ''

title: "feat(backend): "

🚀 Feature Request

Is your feature request related to a problem? Please describe.

For implementation of the peer-review infinity scroll and the task specific annotations (such as named entities and summary) we need a new table for storing these annotations. The annotation content can be stored in a jsonb in the tables so this can be utilized for multiple different annotation templates.

Describe the solution you'd like

annotation (

 uid UUID PRIMARY KEY DEFAULT gen_random_uuid(),

 record_id UUID NOT NULL REFERENCES record(uid) ON DELETE CASCADE,

 annotator_id UUID NOT NULL REFERENCES "user"(uid) ON DELETE SET NULL,

 annotation_type VARCHAR(50) NOT NULL,

 result JSONB NOT NULL,

 lead_time FLOAT CHECK (lead_time IS NULL OR lead_time \>= 0),

 confidence FLOAT CHECK (confidence IS NULL OR (confidence \>= 0 AND confidence \<= 1)),

 created_at TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP
)

Also a list of annotations in the record table

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

📌 Follow semantic issue titling convention: <type>(<scope>): <description> (e.g., feat(records): support video uploads or feat(auth): implement password reset).