⚠️ This site and its services are in early development. Expect partial content, changes, and preview features. ⚠️

HVDNet API

Our API is central to all our services.

Its core objective is to streamline dataset discovery, access, and use through standards-based metadata, ensuring full alignment with FAIR principles and related best practices. It achieves this by applying a crucial standardization layer on top of existing APIs from various platforms and public services,

A range of useful utility services are also being implemented to support the creation and use of machine actionable data and metadata.

You can use our Playground web application to explore/experiment with the API.

Consult the documentation below for more information:

Resource Identifiers

Uniquely identifying resources is always a challenge. While these may in some cases exists (e.g. DOI), this is not generally available for most high-value datasets and related entities.

For the HVDNet API, we are using the following platform/service dependent schemes to identify servers, catalogs, and datasets:

Platform Scheme Examples
MTNA RDS mtnards:<server_id>:<catalog_id>:<dataset_id> mtnards:rds.highvaluedata.net:us_anes:anes1948
Socrata socrata:<server_id>:<dataset_id> socrata:data.calgary.ca:iahh-g8bj
U.S. Census Bureau uscensus:api.census.gov:<dataset_id> uscensus:api.census.gov:<dataset_id>

Datasets services

The /datasets endpoints generates standardized metadata based on the information available from the back-end platforms. This is not always ideal as metadata exposed by the is typically proprietary and sparse. Future versions will add knowledge inference services that will generate new metadata from the data and available documentation. The current implementation is experimental, particularly for new or emerging specifications such as DDI-CDI and Croissant.

In addition, the dataset services include a data-centric Postman Collection generator, which is used to populate public workspaces for various data publishers.

A markdown generator is also included to produce both human and AI friendly documentation.

At this time, these features are being implemented for the following platforms and public API:

The Playground web application to explore these services and their outputs.