Skip to content

[SimEdit]: Allow editing uploaded simulations from the Simulation Details page #70

@tomvothecoder

Description

@tomvothecoder

Problem

Simulation Details page already has partial edit placeholders, but SimBoard still has no working way to persist metadata edits for an existing simulation. We need a narrow v1 edit flow that matches the current codebase and avoids mixing in broader editing work that has different data-model and authorization concerns.

Scope for this issue

  • Add a working edit flow on the Simulation Details page for authenticated users
  • Pre-populate editable fields from the existing simulation record
  • Add a backend update endpoint for existing simulations (PATCH/partial update)
  • Persist changes without creating a new simulation record
  • Update last_updated_by / updated_at when edits succeed
  • Reuse existing backend field validation/types where possible

Editable fields in v1

Keep this issue scoped to simulation metadata/provenance fields only:

  • Description
  • Campaign
  • Experiment Type
  • Compiler
  • HPC Username
  • Key Features
  • Known Issues
  • Notes Markdown
  • Git Repository URL
  • Git Branch
  • Git Tag
  • Git Commit Hash

Additional work:

Explicitly out of scope for this issue

These need separate follow-up issues because they have different UX/data-model implications:

  • Case-level editing (shared case fields / case reassignment)
  • Timeline and setup field editing
  • Artifact and external link editing
  • Comment system work
  • Ownership- or org-based authorization rules
  • GitHub-org-restricted login or GitHub-org-restricted edit privileges
  • Key Features, Known Issues, and Notes Markdown should have a text editor capability similar to Confluence and GitHub. Ideally, it should support tables and embedding images.

Authorization note

For this issue, assume authenticated users can edit. The existing data model does not currently provide a reliable way to map archive uploader ownership or hpc_username to a GitHub OAuth identity.

A stricter authorization model should be designed separately.

Success criteria

  • A logged-in user can edit the scoped metadata fields from the Simulation Details page
  • A logged-out user remains read-only
  • Edits persist after refresh
  • Save/cancel behavior is clear and does not affect read-only fields
  • Validation errors are surfaced without corrupting the existing record

Follow-up work

See follow-up issues for:

  • Case editing
  • Timeline/setup editing
  • Artifact/link editing
  • Auth/authorization policy for edit access

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions