coyote3

Navigation and Pages

This chapter defines the primary navigation model of Coyote3 and explains what each major page is responsible for.

Coyote3 is organized around a single operational spine:

  1. Start in Samples.
  2. Open a case into DNA or RNA workflow.
  3. Review, classify, and comment.
  4. Preview and save report artifacts.
  5. Re-open from reported history when needed.

Main entry points

Navbar discovery tools:

Detailed tool guide:

Samples worklist

Supported routes:

Primary user actions:

Live and done semantics

The worklist state is driven by samples.report_num.

Operational effect:

Opening a case

From /samples:

sample_id accepts the sample name used by the worklist.

Sample settings workspace

Route:

Purpose:

Supporting route handlers used by the page:

DNA workspace

Primary route:

Navigation from DNA list:

RNA workspace

Primary route:

Navigation from RNA list:

Report retrieval

Saved reports are opened through sample-scoped routes:

If filepath is absent in report metadata, the app reconstructs path from configured report base and assay report folder.

Search and historical review

Interpretation history routes:

These routes are designed for cross-sample context and report-time traceability.

For complete usage patterns, see:

Administration navigation

Administration root:

Managed domains:

Administration pages govern system behavior; they are not part of day-to-day interpretation workflow.