Purpose

A living reference hub for papers, datasets, and tools aligned to the technical track.

Technical scope

The atlas is curated for operational use, not just bibliography. Each entry should support one or more concrete tasks in the connectomics workflow and include enough metadata to assess applicability, maturity, and reproducibility.

Scope

• Organize references by workflow stage and evidence type.
• Maintain provenance fields (year, species, modality, scale, access).
• Link every reference family back to at least one track unit.

Planned structure

• Imaging and acquisition references
• Reconstruction and segmentation references
• Analysis and NeuroAI references
• Dataset and benchmark references

Visual context set (draft)

Attribution: module14 lesson3 and neuroAI source decks (historical/context visuals).

Required metadata schema (minimum)

• citation: standardized citation string.
• workflow_stage: acquisition, reconstruction, proofreading, analysis, or cross-cutting.
• species and brain_region.
• modality and effective_resolution.
• dataset_or_code_access: URL plus access constraints.
• maturity: concept, validated prototype, production-validated.
• known_limits: concise statement of technical boundaries.
• mapped_units: links to technical-training unit slugs.

Curation policy

1. Add only resources with clear technical contribution or benchmark value.
2. Mark historical methods as historical when superseded, but keep if pedagogically useful.
3. Prefer references with reproducible artifacts (data, code, or explicit protocol).
4. Re-review entries on schedule and retire stale links.

Quality-control checks

• Link health check for every external URL.
• Metadata completeness validation against required schema.
• Duplicate detection (same method presented across multiple venues).
• Coverage audit to avoid over-weighting one workflow stage.

Course links

• Return to Technical Training hub

Practical workflow

1. Start from a workflow stage (imaging, reconstruction, proofreading, analysis).
2. Select core references and datasets for that stage.
3. Cross-link chosen references to relevant technical-track units.
4. Record update date and curator for each entry group.

Discussion prompts

• Which references are foundational versus context-only for current learners?
• What deprecation criteria should remove outdated resources from the atlas?

Mini-lab

Curate one new atlas entry and include:

1. Complete metadata schema fields.
2. One sentence on technical contribution.
3. One sentence on limitation or failure context.
4. One linked unit in this technical-training track.

Related resources

• Journal club list: Technical Track Journal Club
• Shared vocabulary: Connectomics Dictionary

Quick activity

Select one reference from each workflow stage and explain in one sentence how each supports a different unit in the track.

Draft lecture deck

• Slide draft page: Atlas Connectomics Reference deck draft