Unique, normalized, name of dataset.

Unique data file of dataset page.

Score for how easy it is to work with the data. Determined by portion of meaningful column names, column(s) contain constant values.

Explanation of known issues for usability dimension.

Score for how complete metadata fields are (Description, Limitations, Topics, Contact Email) are, Higher scores mean more metadata fields filled.

Explanation of known issues for metadata dimension.

Score for how up to date the data is. The smaller the duration gaps between stated refresh rate and time last refresh, the higher the score.

Explanation of known issues for freshness dimension.

Score for how much of the data is missing. Determined by if more than half of the values in this dataset is missing.

Explanation of known issues for completeness dimension.

Score for the degree to which data is easy to access. Determined by if the data can be accessed directly via API, any tags/keywords on the dataset, any automated data pipeline set up with open data.

Explanation of known issues for accessibility dimension.

Data file resource is stored as ckan datastore or filestore.

Data publisher division

Summary of accessibility, completeness, freshness, metadata, and usability scores into a single score. Weights determined via rank weighting.

Bronze, Silver, Gold badge using the score column.

Timestamp the dataset was scored.