Role-Based Onboarding Hub

Welcome to the coaching staff room for nbadb. Use this page to pick your role, run the opening drill, and get onto the right page before you burn time wandering the whole playbook.

Routes

contributor, analyst, operator, stakeholder

Warm-up lane

Browser first

open Playground when you want the lowest-friction start

Best first win

One useful artifact

leave with a query, command, diagram, or handoff page

Default move

Start by today

pick the role that matches the current job, not the org chart

Route board in one glance

Role today	Start here	First useful action	Leave with
Contributor	Installation	Run `uv sync --extra dev` so the local toolchain is real before you touch code or docs	A working dev environment and the right follow-up page
Analyst without local setup	SQL Playground	Run one sample query in the browser and change a filter, aggregate, or sort	A query shape you can port to live data
Analyst with live data	Analytics Quickstart	Connect to `nba.duckdb` and stop once `SHOW TABLES` confirms the floor	One working answer or reusable notebook cell
Operator	Daily Updates	Run `nbadb status --output-format json` so you know the current state before you choose `daily`, `monthly`, or `backfill run`	A clean run, a deliberate rerun, or an isolated failure lane
Stakeholder	Architecture	Run `nbadb schema` for the fastest public-model snapshot	A clear picture of what the dataset contains and how it moves

Quick route board

Build and docs lane

Contributor

First read: Installation.
First useful action: uv sync --extra dev.
Next stop: CLI Reference.

First-answer lane

Analyst

First read: SQL Playground for browser-only reps, or Analytics Quickstart for live data.

First useful action: run the Playground leaderboard example, or nbadb download if you are moving straight to the full dataset.

Next stop: Analytics Quickstart.

Run and recovery lane

Operator

First read: Daily Updates.
First useful action: nbadb status --output-format json, then nbadb daily when the recurring lane is clear.

Next stop: Troubleshooting Playbook .

Context lane

Stakeholder

First read: Architecture.
First useful action: nbadb schema.
Next stop: Schema Reference.

Low-friction lane

Browser warm-up

First read: SQL Playground.
First useful action: run one sample query and change one filter, sort, or aggregate.

Next stop: Analytics Quickstart.

Pick one lane, run one useful action, then branch. If you are not sure where to begin, choose the row that matches the job you need done today, not the title on your org chart. If you need the lowest-friction start possible, take the browser lane first and move to the local warehouse second.

Pick your lane

Each tab gives you the same scan path:

Run first to get moving
Open next so you land on the right follow-up page
Watch for so the common misses do not cost a second possession

Primary route: Installation → CLI Reference → Architecture

Run first

Repo-local environment

$ uv sync --extra dev

Keep the current command surface nearby in CLI Reference.
Read Architecture before changing pipeline flow, table families, or generated docs.

Open next

Schema Reference

Use Schema Reference to understand output naming and table families.

Open next

Data Lineage

Use Data Lineage to trace a transform back upstream.

Open next

Regenerate docs

Run uv run nbadb docs-autogen --docs-root docs/content/docs after schema changes so generator-owned docs stay in sync.

Watch for

Primary route: SQL Playground → Analytics Quickstart → DuckDB Query Examples

Run first

Seed a local dataset

$ nbadb download

If you want a no-install warm-up first, open SQL Playground and run the leaderboard example before you download anything.
Or use an existing nba.duckdb or Parquet export.
Start with analytics_* surfaces for the fastest first query.
Move into the table-level docs only after you know the question you want to answer.

Open next

SQL Playground

Use SQL Playground when you want one browser-only rehearsal before connecting to the real dataset.

Open next

DuckDB Query Examples

Use DuckDB Query Examples for a SQL-first scouting packet.

Open next

Player Comparison

Use Player Comparison for head-to-head analysis patterns.

Open next

Shot Chart Analysis

Use Shot Chart Analysis for court-map and zone work.

Open next

Parquet Usage

Use Parquet Usage for Polars, Pandas, and Arrow workflows.

Watch for

Primary route: Daily Updates → CLI Reference → Troubleshooting Playbook

Run first

Check current pipeline state

$ nbadb status --output-format json

If the state looks clean and you are on the recurring cadence, run nbadb daily next.
Review what each run mode actually does: daily, monthly, backfill run, status, scan.
Confirm your data directory and output expectations.
Keep the latest health artifacts in view:
- artifacts/health/daily/dependency-inventory.json
- artifacts/health/daily/data-quality-report.json
- artifacts/endpoint-coverage/*

Open next

Troubleshooting Playbook

Use Troubleshooting Playbook the moment a run leaves you with a failing artifact, a broken command, or a recovery question.

Open next

Pipeline Flow

Use Pipeline Flow to share a stage map quickly.

Open next

Architecture

Use Architecture to review validation tiers, internal state, and run-mode boundaries.

Open next

Kaggle Setup

Use Kaggle Setup for dataset handoff and publish flow.

Watch for

Primary route: Architecture → Schema Reference → ER Diagram

Run first

Fastest schema snapshot

$ nbadb schema

Read Architecture for the source-to-export story.
Scan Schema Reference to understand what the public dataset actually contains.
Review Kaggle Setup when the conversation shifts to distribution and delivery.

Open next

ER Diagram

Use ER Diagram for a fast visual schema read.

Open next

Endpoint Map

Use Endpoint Map for source-coverage conversations.

Open next

Strategic Shift Rollout

Use Strategic Shift Rollout for planned migration sequencing.

Watch for

Role-Based Onboarding Hub

Welcome to the coaching staff room for nbadb. Use this page to pick your role, run the opening drill, and get onto the right page before you burn time wandering the whole playbook.

Routes

contributor, analyst, operator, stakeholder

Warm-up lane

Browser first

open Playground when you want the lowest-friction start

Best first win

One useful artifact

leave with a query, command, diagram, or handoff page

Default move

Start by today

pick the role that matches the current job, not the org chart

Route board in one glance

Role today	Start here	First useful action	Leave with
Contributor	Installation	Run `uv sync --extra dev` so the local toolchain is real before you touch code or docs	A working dev environment and the right follow-up page
Analyst without local setup	SQL Playground	Run one sample query in the browser and change a filter, aggregate, or sort	A query shape you can port to live data
Analyst with live data	Analytics Quickstart	Connect to `nba.duckdb` and stop once `SHOW TABLES` confirms the floor	One working answer or reusable notebook cell
Operator	Daily Updates	Run `nbadb status --output-format json` so you know the current state before you choose `daily`, `monthly`, or `backfill run`	A clean run, a deliberate rerun, or an isolated failure lane
Stakeholder	Architecture	Run `nbadb schema` for the fastest public-model snapshot	A clear picture of what the dataset contains and how it moves

Quick route board

Build and docs lane

Contributor

First read: Installation.
First useful action: uv sync --extra dev.
Next stop: CLI Reference.

First-answer lane

Analyst

First read: SQL Playground for browser-only reps, or Analytics Quickstart for live data.

First useful action: run the Playground leaderboard example, or nbadb download if you are moving straight to the full dataset.

Next stop: Analytics Quickstart.

Run and recovery lane

Operator

First read: Daily Updates.
First useful action: nbadb status --output-format json, then nbadb daily when the recurring lane is clear.

Next stop: Troubleshooting Playbook .

Context lane

Stakeholder

First read: Architecture.
First useful action: nbadb schema.
Next stop: Schema Reference.

Low-friction lane

Browser warm-up

First read: SQL Playground.
First useful action: run one sample query and change one filter, sort, or aggregate.

Next stop: Analytics Quickstart.

Pick your lane

Each tab gives you the same scan path:

Run first to get moving

Open next so you land on the right follow-up page

Watch for so the common misses do not cost a second possession

Primary route: Installation → CLI Reference → Architecture

Run first

Repo-local environment

$ uv sync --extra dev

Keep the current command surface nearby in CLI Reference.
Read Architecture before changing pipeline flow, table families, or generated docs.

Open next

Schema Reference

Use Schema Reference to understand output naming and table families.

Open next

Data Lineage

Use Data Lineage to trace a transform back upstream.

Open next

Regenerate docs

Run uv run nbadb docs-autogen --docs-root docs/content/docs after schema changes so generator-owned docs stay in sync.

Watch for

Primary route: SQL Playground → Analytics Quickstart → DuckDB Query Examples

Run first

Seed a local dataset

$ nbadb download

If you want a no-install warm-up first, open SQL Playground and run the leaderboard example before you download anything.
Or use an existing nba.duckdb or Parquet export.
Start with analytics_* surfaces for the fastest first query.
Move into the table-level docs only after you know the question you want to answer.

Open next

SQL Playground

Use SQL Playground when you want one browser-only rehearsal before connecting to the real dataset.

Open next

DuckDB Query Examples

Use DuckDB Query Examples for a SQL-first scouting packet.

Open next

Player Comparison

Use Player Comparison for head-to-head analysis patterns.

Open next

Shot Chart Analysis

Use Shot Chart Analysis for court-map and zone work.

Open next

Parquet Usage

Use Parquet Usage for Polars, Pandas, and Arrow workflows.

Watch for

Primary route: Daily Updates → CLI Reference → Troubleshooting Playbook

Run first

Check current pipeline state

$ nbadb status --output-format json

If the state looks clean and you are on the recurring cadence, run nbadb daily next.
Review what each run mode actually does: daily, monthly, backfill run, status, scan.
Confirm your data directory and output expectations.
Keep the latest health artifacts in view:
- artifacts/health/daily/dependency-inventory.json
- artifacts/health/daily/data-quality-report.json
- artifacts/endpoint-coverage/*

Open next

Troubleshooting Playbook

Use Troubleshooting Playbook the moment a run leaves you with a failing artifact, a broken command, or a recovery question.

Open next

Pipeline Flow

Use Pipeline Flow to share a stage map quickly.

Open next

Architecture

Use Architecture to review validation tiers, internal state, and run-mode boundaries.

Open next

Kaggle Setup

Use Kaggle Setup for dataset handoff and publish flow.

Watch for

Primary route: Architecture → Schema Reference → ER Diagram

Run first

Fastest schema snapshot

$ nbadb schema

Read Architecture for the source-to-export story.
Scan Schema Reference to understand what the public dataset actually contains.
Review Kaggle Setup when the conversation shifts to distribution and delivery.

Open next

ER Diagram

Use ER Diagram for a fast visual schema read.

Open next

Endpoint Map

Use Endpoint Map for source-coverage conversations.

Open next

Strategic Shift Rollout

Use Strategic Shift Rollout for planned migration sequencing.

Role-Based Onboarding Hub

Contributor

Analyst

Operator

Stakeholder

Browser warm-up

Schema Reference

Data Lineage

Regenerate docs

SQL Playground

DuckDB Query Examples

Player Comparison

Shot Chart Analysis

Parquet Usage

Troubleshooting Playbook

Pipeline Flow

Architecture

Kaggle Setup

ER Diagram

Endpoint Map

Strategic Shift Rollout

Stay in the same possession

Analytics Quickstart

SQL Playground

DuckDB Query Examples

On this page

Role-Based Onboarding Hub

Contributor

Analyst

Operator

Stakeholder

Browser warm-up

Schema Reference

Data Lineage

Regenerate docs

SQL Playground

DuckDB Query Examples

Player Comparison

Shot Chart Analysis

Parquet Usage

Troubleshooting Playbook

Pipeline Flow

Architecture

Kaggle Setup

ER Diagram

Endpoint Map

Strategic Shift Rollout

Stay in the same possession

Analytics Quickstart

SQL Playground

DuckDB Query Examples

On this page