Option for time-stamp in scenario object (i.e. versioning as metadata)

[adamkucharski]

This package is going to be very useful for managing prospective scenario modelling (i.e. 'what if?' questions about future dynamics), especially as there can be a lot of iteration involved in analysis (e.g. early COVID scenarios for UK and subsequent variant and roadmap scenarios).

Had a couple of questions from a design perspective. Historically, scenario assumptions are often recorded in ad-hoc wrappers, and versions tracked via commits or ad-hoc versioning (if at all). So as this package takes shape, wondered if useful to have this as metadata (perhaps with a stamp in the object as simple first pass, if it's structured this way)?

There's also the related issue of scenario versions passed between models, e.g. the branching process transmission step in ringbp (used for early COVID contact tracing analysis) was later used to form the transmission process in the covidhm model (used for community network analysis) with subsequent version used in event outbreak analysis. Feels like this package would be nice way to pass shared modularised assumptions between models (if feasible)?