How GeoEpi Organizes Work
GeoEpi organizes work as a network rather than a single directory. The lab-level Hub provides the project portfolio and shared context. Each coherent analytical workstream has a canonical subproject repository. Computation and large data live in the appropriate computational environment, and accepted outputs move into project synthesis and dissemination systems.
The vocabulary
| Term | Meaning |
|---|---|
| GeoEpi Hub | The future single lab-level project-management and portfolio repository in the GeoEpi GitHub organization. It holds project context and coordination. |
| Project | A broad scientific or operational objective with people, data, analytical workstreams, and products. |
| Subproject | One independently understandable and executable analytical, software, data-acquisition, modeling, genomic, dashboard, or related workstream. |
| Repository | The canonical Git repository for a subproject’s scientific implementation. |
| Run | One computational execution and its parameters, environment, inputs, logs, outputs, and validation details. |
| Product | A manuscript, report, dashboard, released dataset, operational output, or other accepted scientific result. |
The hierarchy is GeoEpi Hub → Project → Subproject → Run. Products may integrate results from one or more subprojects.
An individual folder in the GeoEpi Hub is a project entry. The Hub is the portfolio and shared context; a project entry is one project within it.
Read the GeoEpi Hub architecture, project and subproject guidance, and repository guidance for practical decisions.
The Hub is planned for a future phase. This refactor documents the architecture and provides templates; it does not create the Hub or implement cross-repository automation.