🔵 fedregister¶
U.S. Federal Register documents from govinfo.gov bulk XML archives. Covers final rules, proposed rules, notices, and presidential documents (executive orders, proclamations, memoranda), partitioned by publication year and month from 2010 to present by default (start year configurable via GOVDATA_START_YEAR). Key cross-reference fields: cfr_references (links to affected CFR titles/parts by industry), rin (Regulatory Identifier Number — tracks rulemaking lifecycle from NPRM to final rule), docket_ids (links to regulations.gov comment dockets). Two tables in this schema: fr_documents (full document metadata from govinfo.gov bulk XML) and fr_significance (OIRA EO 12866 economic-significance flag per document, sourced directly from the Federal Register API's own JSON field — join to fr_documents on document_number). See each table for its full column list.
3 datasets · 15 columns
fr_documents · table¶
All Federal Register documents partitioned by publication year and month. RULE=final rules (binding, amend CFR), PRORULE=proposed rules (open for comment), NOTICE=agency announcements/meetings/grants, PRESDOC=executive orders/proclamations. Key analytical fields: rin (tracks NPRM→final rule lifecycle via RIN cross-reference), cfr_references (JSON: affected CFR titles and parts → maps to regulated industry), docket_ids (JSON: links to regulations.gov for comment letter intelligence).
| Column | Type | Null | Description |
|---|---|---|---|
document_ |
string | yes | Federal Register document number (e.g., 2026-07234) |
title |
string | yes | Document title |
doc_ |
string | no | Document type (RULE, PRORULE, NOTICE, PRESDOC) |
publication_ |
string | no | Publication date (YYYY-MM-DD) |
effective_ |
string | yes | Effective date of the rule (YYYY-MM-DD) |
action |
string | yes | Rule action description (e.g., 'Final rule', 'Proposed rule') |
agency_ |
string | yes | Comma-separated issuing agency names (denormalized for easy SQL filtering) |
cfr_ |
string | yes | JSON array of CFR references [{title:N, part:N}] — maps to regulated industry |
rin |
string | yes | Primary Regulatory Identifier Number (links NPRM to final rule lifecycle) |
docket_ |
string | yes | JSON array of docket identifiers (links to regulations.gov comment dockets) |
signing_ |
string | yes | Presidential document signing date (YYYY-MM-DD) |
fr_significance · table¶
OIRA EO 12866 economic-significance determination per Federal Register document, sourced directly from the Federal Register API's own significant JSON field (https://www.federalregister.gov/api/v1/documents.json) — not present in fr_documents' govinfo.gov bulk-XML source. true = economically significant under EO 12866 (subject to OMB/OIRA regulatory review), false = not significant. NULL is overwhelmingly "significance does not apply to this document type" (confirmed live: 817 of 818 Notices in a March 2026 sample are NULL, since EO 12866 review applies only to Rules) rather than "not yet classified" — filter to type='Rule' or 'Proposed Rule' before treating a NULL as meaningful. Join to fr_documents on document_number to filter significant vs. routine rules.
| Column | Type | Null | Description |
|---|---|---|---|
document_ |
string | yes | Federal Register document number (e.g., 2026-07234); joins to fr_documents.document_number |
publication_ |
string | yes | Publication date (YYYY-MM-DD) |
significant |
boolean | yes | OIRA EO 12866 economic-significance flag (true/false/null — see table comment) |
type |
string | yes | Federal Register document type (Rule, Proposed Rule, Notice, Presidential Document). EO 12866 significance review applies only to Rule/Proposed Rule — filter to those before aggregating significant or NULL from every non-rule Notice swamps the count. |
fr_documents_significance · view¶
fr_documents enriched with the OIRA EO 12866 significance flag from fr_significance (D-052), joined on document_number. LEFT JOIN so documents not yet classified by the Federal Register API (or not yet ingested into fr_significance) still appear, with significant = NULL.
View — columns are resolved by the query engine at runtime.