The main thing I think the saved database object needs is metadata in the form of a title, eg. "April 2018 General Meeting". It could also have stuff like a boolean for whether someone's expected to be manning signin or not (#1).
And, of course, this also applies to the structure of the end-of-meeting metadata - indeed, a big part of this idea was having a facility through which the log would have "April 2018 General Meeting" attached to it (for filing purposes), and if someone tried to restart signin with the next month's database, it'd actively catch that they're doing the wrong thing and stop them.
The main thing I think the saved database object needs is metadata in the form of a title, eg. "April 2018 General Meeting". It could also have stuff like a boolean for whether someone's expected to be manning signin or not (#1).
And, of course, this also applies to the structure of the end-of-meeting metadata - indeed, a big part of this idea was having a facility through which the log would have "April 2018 General Meeting" attached to it (for filing purposes), and if someone tried to restart signin with the next month's database, it'd actively catch that they're doing the wrong thing and stop them.