Offline fixtures / Local processing
Research data contract lab
Load a synthetic provider-shaped response, validate and normalize it, then inspect what survives a date cutoff.
No live provider calls. The lab loads static synthetic fixtures from this publication. Pasted/imported JSON stays in page memory. Do not paste credentials or confidential records. Provider formats have deliberately narrow supported fields; the lab is not a production feed connector.
01 / Select the contract
FRED realtime dates and SEC filing dates have day precision. World Bank examples use retrieval-time availability. Annual periods map to a December 31 sort key while retaining the original year and period kind; this is not a measurement timestamp.
02 / Inspect and validate the payload
03 / Read the normalized record
Selected records
Input versions
Explicit missing values
Availability basis:
| Series | Source period | Value | Unit | Available date | Period kind |
|---|
Inspect complete output and provenance
04 / Simulate a bounded retry decision
This deterministic policy example makes no HTTP calls and performs no real waits. Only 429 and 503 are retryable here. A requested delay above 60 seconds stops the plan; it is never shortened. Maximum attempts are bounded at three. Real HTTP-date Retry-After values require additional parsing.
Read retry and checkpoint reasoningKeep the temporal meaning.
| Field | Meaning |
|---|---|
| observation_date | A normalized source date or annual period sort key; never assumed to be publication time |
| observation_period / period_kind | Original period and date/annual/instant interpretation |
| available_date / availability_basis | Declared date boundary and why it was chosen |
| retrieved_at | Explicit retrieval metadata supplied with the fixture or input |
| revision_key / source_record | Version identity and source record/accession provenance |