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

bib: adopt Bluebook Law Review CSL style for all regulatory citations #300

New Issue
Closed
opened 2026-03-27 04:46:56 +00:00 by kert · 0 comments
kert commented 2026-03-27 04:46:56 +00:00
Owner
Copy Link

Replace hardcoded format.py formatters with proper CSL processing using the Bluebook Law Review style (Tierney 2026, QPPJ8LXZ in Zotero).

Current state: format.py has 5 hardcoded formatters that approximate APA/Bluebook but miss:

  • Proper FR citation format (Volume FR Page)
  • Small caps for institutional authors
  • Correct short-form (id., supra) generation
  • Pinpoint locator positioning per source type
  • Session law format (Pub. L. No.)

The Tierney paper documents the exact CSL field mappings for:

  • Statute → nameOfAct, codeSection, dateEnacted
  • CFR → same Statute type with C.F.R. in nameOfAct
  • FR rules → proper Volume FR Page format
  • Session laws → Bill type with Pub. L. No.
  • Manuscripts → constitutional provisions, procedural rules

Approach: either integrate citeproc-js via PyV8/duktape, or rewrite format.py to follow the CSL field mapping conventions documented in the paper.

Replace hardcoded format.py formatters with proper CSL processing using the Bluebook Law Review style (Tierney 2026, QPPJ8LXZ in Zotero). Current state: format.py has 5 hardcoded formatters that approximate APA/Bluebook but miss: - Proper FR citation format (Volume FR Page) - Small caps for institutional authors - Correct short-form (id., supra) generation - Pinpoint locator positioning per source type - Session law format (Pub. L. No.) The Tierney paper documents the exact CSL field mappings for: - Statute → nameOfAct, codeSection, dateEnacted - CFR → same Statute type with C.F.R. in nameOfAct - FR rules → proper Volume FR Page format - Session laws → Bill type with Pub. L. No. - Manuscripts → constitutional provisions, procedural rules Approach: either integrate citeproc-js via PyV8/duktape, or rewrite format.py to follow the CSL field mapping conventions documented in the paper.
kert added this to the P32: CMS Manual Library — benefits, fraud, and program integrity references milestone 2026-03-27 04:46:56 +00:00
kert closed this issue 2026-03-27 05:24:38 +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
Milestone
No items
No Milestone P32: CMS Manual Library — benefits, fraud, and program integrity references
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#300
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?