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:
/samples/dashboard//admin//public/.../handbook/Navbar discovery tools:
/assay-catalog-matrix/assay-catalog/search/tiered_variantsDetailed tool guide:
Supported routes:
/samples/samples/live/samples/done/samples/<panel_type>/<panel_tech>/<assay_group>/samples/<panel_type>/<panel_tech>/<assay_group>/<status>Primary user actions:
The worklist state is driven by samples.report_num.
report_num missing or 0.report_num > 0.Operational effect:
From /samples:
/dna/sample/<sample_id>/rna/sample/<sample_id>K=sample_id accepts the sample name used by the worklist.
Route:
/samples/<sample_id>/editPurpose:
Supporting route handlers used by the page:
GET /samples/<sample_id>/isglsPOST /samples/<sample_id>/genes/apply-isglPOST /samples/<sample_id>/adhoc_genesPOST /samples/<sample_id>/adhoc_genes/clearGET /samples/<sample_id>/effective-genes/allPrimary route:
/dna/sample/<sample_id>Navigation from DNA list:
/dna/<sample_id>/var/<var_id>/dna/<sample_id>/cnv/<cnv_id>/dna/<sample_id>/transloc/<transloc_id>/dna/sample/<sample_id>/preview_report/dna/sample/<sample_id>/report/savePrimary route:
/rna/sample/<sample_id>K=Navigation from RNA list:
/rna/fusion/<fusion_id>/rna/sample/preview_report/<sample_id>/rna/sample/report/pdf/<sample_id>Saved reports are opened through sample-scoped routes:
/samples/<sample_id>/reports/<report_id>/samples/<sample_id>/reports/<report_id>/downloadIf filepath is absent in report metadata, the app reconstructs path from configured report base and assay report folder.
Interpretation history routes:
/search/tiered_variants/reported_variants/variant/<variant_id>/<tier>These routes are designed for cross-sample context and report-time traceability.
For complete usage patterns, see:
Administration root:
/admin/Managed domains:
Administration pages govern system behavior; they are not part of day-to-day interpretation workflow.