Skip to content

Add separate epi_archive constructor based on a "iterator"/list/df of snapshots #173

Open
@brookslogan

Description

@brookslogan

See #172 for background. This would work around some of the caveats noted there by:

  • Detecting row deletions, probably just representing them as an update row with all non-key columns NA.
  • For each explicit version, check whether a snapshot of next_after(version) was provided. If not, insert a snapshot revising all observations to NA with this version tag (next_after(version)). ---- This is pretty inefficient space-wise. Maybe we would want to do something with the design of epi_archive to make more efficient options available.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1medium priorityenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions