How DBnomics helps researchers find and assess economic data

DBnomics brings economic series from different publishers into a shared research interface. For readers following Russia, its value is practical: it can shorten the path from a question about prices, output or trade to the underlying observations. It does not turn those observations into a verdict about the economy. Definitions, publication dates and gaps still need attention.

According to its website, the free platform aggregates publicly available data from statistical institutions, researchers and other providers. Its legal pages identify CEPREMAP with the project. Economists, students and journalists are among the audiences named in its documentation. The useful starting point is a specific research question, rather than the assumption that every Russian indicator will be available or comparable.

One interface, several kinds of evidence

The DBnomics economic data platform offers a website and a programming interface for retrieving series. Its documentation describes keyword searches, navigation through providers' datasets, charts, tables and downloads. Researchers working with Python or R can also use client libraries. A reader exploring a single indicator can start with the website without building a software workflow.

That common interface does not make the publishers interchangeable. A national statistical release, an international institution's estimate and a forecast answer different questions. Before using a number, identify who produced it and what it measures. Russia Economy's economic indicators dashboard provides a useful starting map of the questions, while a wider database can help investigate the series behind a comparison.

Consider an output comparison. A level in current prices is different from a volume measure adjusted for price changes. A quarterly observation is different from annual growth, and a forecast is different from a reported result. The platform can help locate material, but the analyst must still decide whether two series belong in the same comparison. Matching labels alone is insufficient.

Preserve the meaning behind the values

DBnomics says its core design preserves providers' numerical values, original series codes and missing observations while normalizing formats. It also retains providers' dataset structures. This is an access service, not a promise that every source has used the same statistical method. A common download format should not be mistaken for a common economic definition.

Inflation illustrates the distinction. A consumer price index, its monthly change and its change from a year earlier are related measures, not substitutes. Before using a series alongside Russia's inflation history, check the reference period, frequency and units. A rebased index can look different without implying that the underlying price experience has suddenly changed. Record the base and any transformation applied.

The same discipline applies to country coverage and seasonal adjustment. Keep the provider's methodological notes with the observations. If a territorial definition or classification changes, flag the break instead of drawing one uninterrupted story through it. If a value is absent, leave it absent unless the research explicitly calls for an estimate and explains how that estimate was made.

Revisions are part of the research

The platform's documentation describes automated collection and preservation of revisions fetched from providers. That feature matters when a researcher wants to distinguish what was known at a particular time from what a later release says. An updated historical value can change a comparison even when the period being studied has not changed.

A useful research record therefore includes the provider, dataset and series identifiers, the observation period, and the date of retrieval. Keep a copy of the data actually used. If the provider revises an earlier period, compare the two versions before explaining the difference. Do not assume that a chart viewed later will reproduce a previously downloaded calculation exactly.

Automated collection also requires a freshness check. A database update and a new observation are different events: a collection process can run without the original publisher releasing another figure. Check the last observation and the original release before calling a series current. The economic timeline can help frame events, but an event date is not evidence of when a statistical value became available.

Access and reuse need separate checks

DBnomics describes itself as free to access. Its legal terms nevertheless distinguish the aggregated database license from the rights attached to underlying source data. The aggregate is offered under the Open Database License, while original providers' terms still apply to their material. Free retrieval does not, by itself, settle every question about republishing a dataset in another product.

For a small project, start by locating the series in the browser and examining its metadata. Download a sample before automating retrieval. Check how missing values, dates and units arrive in the chosen file format. When a project grows, use stable identifiers and document transformations so another reader can understand how the final table was produced.

Teams should also decide who checks the source after an automated update. A script can retrieve a file successfully while the publisher has changed a definition or stopped a series. Retaining metadata and reviewing unusual gaps are part of research quality. They are not evidence that the platform has made an error, and they should not be presented as such without investigation.

What DBnomics cannot resolve

An aggregator cannot supply information that an original publisher has not released. Nor does placing sources together establish that their figures are independently verified, equally complete or suitable for every purpose. DBnomics' legal terms explicitly disclaim responsibility for the accuracy or continued availability of source data. Users still need to inspect the originating publication for consequential claims.

For Russia-focused work, the sensible test is narrow: does the platform provide the exact series, period and documentation needed for this question? If it does, the common interface may reduce retrieval work. If it does not, the missing item remains a research gap. Another country's figure or a differently defined proxy should not quietly be substituted for it.

The platform is therefore most useful as a route into evidence, with a record of how that evidence was obtained. Start with a defined question, keep the original source attached to the numbers and explain any transformation. That approach makes the final analysis easier to inspect, whether it supports a clear conclusion or shows why the available information cannot yet support one.

Partner content. This article is about DBnomics and is separate from Russia Economy's editorial coverage.