Public data engineering resources.
Technical notes for developers, analysts and data teams working with difficult public-source records.
How to parse SEC Form 4 XML
Issuer, reporting-owner and transaction fields for structured insider datasets.
Read guide →SEC Company Facts for financial data
Taxonomy, units, periods and missing-fact challenges in financial normalization.
Read guide →USAspending award transactions
Award histories, obligations, deduplication and reconciliation for federal procurement data.
Read guide →Practical guides for public data pipelines
Working with public financial and procurement records requires more than downloading a source file. Identifiers, reporting periods, amendments, missing fields and publication delays all affect the meaning of a dataset. These guides explain the engineering decisions that matter when converting source disclosures into structured records for analysis and integration.
SEC insider ownership filings
The Form 4 XML guide describes how to separate issuer details from reporting-owner identities, interpret transaction codes and retain filing provenance. It also covers derivative transactions, footnotes and amendments that complicate otherwise simple transaction tables.
Company financial statements
The SEC Company Facts guide examines taxonomy mappings, units, instant versus duration periods and competing observations across filings. These distinctions are essential for producing consistent financial metrics without confusing missing facts with reported zeros.
Federal contract history
The USAspending transactions guide explains the difference between award identities and action histories, including obligations, modifications, deduplication and reconciliation. It helps analysts avoid counting multiple actions as independent awards.
From reference material to integration
Each guide focuses on source semantics and validation principles. For DModify's available dataset products, visit the data portfolio. To assess sample records, schemas, provenance and access options, follow the evaluation guide and developer documentation. Published guides are educational references; product-specific coverage and access terms should be checked against the corresponding product page.