Feat 120 assigment dashboard

[karimouf]

Main Description

Implemented an Assignment Dashboard flow that shifts submission handling from admin-only/manual import to assignment-based self-service uploads, enabling both admins and users to manage submissions and revision workflows.

---

User Features

• Create assignments and assign to roles
• Edit / Copy / Delete / Close assignments
• View submissions per assignment
• Submit multiple revisions
• Replace/Delete submissions (if not used in a study)
• View and manage assignment-bound submissions
• Submission metadata support (description)
• Study usage tracking via studyUsageCount
• Assignment-specific views for submissions
• Max revisions slider (including unlimited option)

---

System Features

• Assignment Data Model

  • title, description, public
  • studyId, workflowId, userId
  • start, end, closed
  • validationConfigurationId
  • assignedRoleIds
  • parentAssignmentId, previousSubmissionAssignmentId
  • allowReUpload, maxRevisions
  • deleted, deletedAt, createdAt, updatedAt

• Submission Model Updates

  • name, description (metadata)
  • assignmentId (linkage)

• Access Control

  • Own + public visibility
  • Admin: full access
  • Owner-only actions (Edit/Delete/Share)

• Submission Pipeline

  • Assignment-based uploads
  • Revision chain enforcement

• Validation & Rules

  • Validation before persistence
  • Upload only when open (admin override)
  • Re-upload controlled via configuration

• Revision Control

  • Max revision limits
  • Standard naming (revision X)

• Study Protection

  • Prevents unsafe replace/delete using studyUsageCount

---

Known Limitations

• User assignment view still missing some features (pending alignment/decision)

[dennis-zyska]

Thank you, nice and fast implementation, I made some comments for improvements. Note that I didn't run the branch yet, so the feedback is only on the code. There are also some merge conflicts.

[dennis-zyska]

Can't we add this in the assignment creation migration? As long it is not merged to dev, I think it would be fine to do so. I'm also thinking, maybe it directly make sense here to adapt it also with an additional table instead of an array. Arrays in db tables are always a bad idea (also see https://en.wikipedia.org/wiki/Database_normalization)

[dennis-zyska]

both