Shared QR and label printing for pathway nodes #310

New issue

Open

opened 2026-07-27 14:01:46 +00:00 by AI · 0 comments

AI commented

2026-07-27 14:01:46 +00:00

Collaborator

Context

#261 (QR per node) and #263 (physical stickers) are the same feature at two fidelities. Materials already do this end-to-end: util/qr.py, generate_material_label_png, and util/label_printer.py. Tools also deferred QR/labels into the same gap.

Proposal

Generalise the Materials pattern rather than a Pathways-only printer:

Stable short URL for a node (slug or shortcode → member pathway view focused on that node), using base_url_short where configured.
generate_pathway_node_label_png (or a shared label helper parameterised by title + QR target) mirroring material labels: QR + node title (+ optional pathway/parent crumb).
Committee actions on a node: preview QR image, download PNG, print via existing label printer host.
Sticker / batch print for a subtree or selection (the "stickers" ask) — same PNG pipeline, multi-print like material bulk labels.

Do not invent a second print stack. Prefer extracting shared bits from Materials if Pathways would otherwise copy-paste.

Acceptance criteria

Each published node has a scannable URL that opens the pathway graph on that node
Committee can preview, download, and print a node label
Batch print for multiple nodes works on the space Brother printer
#261 and #263 closed; note for Tools that the shared printer path is the intended home for tool QR/labels later

#261 Generate QR for node
#263 Pathway stickers
Materials: util/materials.py (generate_material_label_png), util/label_printer.py

## Context #261 (QR per node) and #263 (physical stickers) are the same feature at two fidelities. Materials already do this end-to-end: `util/qr.py`, `generate_material_label_png`, and `util/label_printer.py`. Tools also deferred QR/labels into the same gap. ## Proposal Generalise the Materials pattern rather than a Pathways-only printer: 1. **Stable short URL** for a node (slug or shortcode → member pathway view focused on that node), using `base_url_short` where configured. 2. **`generate_pathway_node_label_png`** (or a shared label helper parameterised by title + QR target) mirroring material labels: QR + node title (+ optional pathway/parent crumb). 3. **Committee actions** on a node: preview QR image, download PNG, print via existing label printer host. 4. **Sticker / batch print** for a subtree or selection (the "stickers" ask) — same PNG pipeline, multi-print like material bulk labels. Do not invent a second print stack. Prefer extracting shared bits from Materials if Pathways would otherwise copy-paste. ## Acceptance criteria - [ ] Each published node has a scannable URL that opens the pathway graph on that node - [ ] Committee can preview, download, and print a node label - [ ] Batch print for multiple nodes works on the space Brother printer - [ ] #261 and #263 closed; note for Tools that the shared printer path is the intended home for tool QR/labels later ## Related - #261 Generate QR for node - #263 Pathway stickers - Materials: `util/materials.py` (`generate_material_label_png`), `util/label_printer.py`

AI added this to the Project Pathways milestone

2026-07-27 14:01:46 +00:00

AI added the

enhancement

label

2026-07-27 14:01:46 +00:00

AI referenced this issue

2026-07-27 14:04:30 +00:00

Pathway stickers #263

AI referenced this issue

2026-07-27 14:04:31 +00:00

Generate QR for node #261