homelab/stack
1
0
Fork 0
Code Issues 79 Pull Requests 1 Actions 1 Packages Projects 1 Releases Wiki Activity

bib: place() + Zotero child link attachments (linkMode=3) for cited FR paragraphs #637

New Issue
Closed
opened 2026-08-17 18:18:07 +00:00 by kert · 0 comments
kert commented 2026-08-17 18:18:07 +00:00
Owner
Copy Link

bib.frlink.place(store, ref, label='') — resolve then upsert an fr_links row (the curated cited subset; never bulk-place all ~5k anchors, per design review). bib/sync.py gains _sync_fr_links beside _sync_attachments: each fr_links row becomes a Zotero child link attachment — linkMode=3 (linked_url), contentType text/html, itemData url + title = label — idempotent by existing child URL on the parent. CLI: stack bib fr-jump REF [--key K] [--md] [--place [--label L]].

Tests: tmp bib + tmp zotero db (existing test_sync fixture pattern): linkMode=3 child created once, second sync no-ops; fr-jump CLI happy path.

Depends on #634, #635. Spec: docs/superpowers/specs/2026-08-17-fr-jump-links-design.md.

`bib.frlink.place(store, ref, label='')` — resolve then upsert an `fr_links` row (the curated cited subset; never bulk-place all ~5k anchors, per design review). `bib/sync.py` gains `_sync_fr_links` beside `_sync_attachments`: each `fr_links` row becomes a Zotero **child link attachment** — `linkMode=3` (linked_url), `contentType text/html`, itemData `url` + `title` = label — idempotent by existing child URL on the parent. CLI: `stack bib fr-jump REF [--key K] [--md] [--place [--label L]]`. Tests: tmp bib + tmp zotero db (existing test_sync fixture pattern): linkMode=3 child created once, second sync no-ops; fr-jump CLI happy path. Depends on #634, #635. Spec: docs/superpowers/specs/2026-08-17-fr-jump-links-design.md.
kert added this to the P40: FR Jump Links — page/paragraph deep links for every FR citation milestone 2026-08-17 18:18:07 +00:00
kert added the databib labels 2026-08-17 18:18:07 +00:00
kert closed this issue 2026-08-17 18:44:54 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label bib data
Milestone
No items
No Milestone P40: FR Jump Links — page/paragraph deep links for every FR citation
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#637
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?