Controlled-Data Inventory

A small project-level record of data whose stewardship matters.

The future Hub should inventory project data whose stewardship matters, such as surveillance or case detections, field-collected data, genomic or sample data, facility or premises-level data, diagnostic data, partner-provided datasets, restricted extracts, and other controlled or governed data.

The inventory is a map, not a copy of the data. Do not store controlled data in GitHub. For each important data asset, record a stable ID, name and description, provider, project steward, authoritative storage location, access or restriction level, applicable agreement or limitation, relevant subprojects, and current status or notes.

Public analytical sources do not need to be cataloged exhaustively in the Hub. Sources such as ERA5, MODIS, administrative boundaries, census data, public host or livestock surfaces, roads, and night lights should normally be documented by the subproject repository that acquires or uses them.

Use the controlled-data inventory template for a minimal starting point. The project DMP explains how the project plans to manage data; the inventory records what is actually present.