Skip to content

Commit the 16 recovered Google Sheet tabs as a static, non-build archive #599

Description

@turbomam

The 16 recovered sheet tabs exist only as local files. They should be committed so the content stops depending on Drive revision retention or one laptop.

Proposal. Commit the 16 extracted TSVs under a clearly non-build path, for example data/sheet-archive/, one file per tab, verbatim. Add a README recording the source spreadsheet ID, the Drive revision (7622, 2026-06-04 19:40 UTC), and the extraction date.

Constraints.

  • Not a build input. Nothing in src/ontology/metpo.Makefile or the root Makefile should read these files. They are a historical record.
  • Verbatim. No normalization, no header cleanup, no de-duplication. Whatever review happens later works from the untouched copy.
  • classes and properties are included for completeness even though live equivalents exist in src/templates/, so the archive is a coherent snapshot of the workbook rather than a partial one.

Open question. Whether to also commit the source xlsx (366397 bytes). It is the single-file master and guarantees the TSV extraction can be redone, but it is a binary blob in a repo that is otherwise text.

Not in scope. Merging any archived content into classes or properties. That review is tracked in #526 Salvage then retire the two Google Sheet tabs with unique content and, for the five recovered Sheet38 classes, in #245 pathogenicity by host lifecycle.

Depends on #598 Record: all 16 Google Sheet tabs recovered from Drive revision 7622 after the 2026-07-31 deletion. Related: #433 Umbrella: switch SoT to repo OWL, narrow scope, add maintenance guardrails, #380 Remove machinery for fetching non-core sheets and BioPortal submissions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions