Better support for multiple years

Right now we're throwing away everything from last year and starting fresh to set up the site for the next year. This seem inefficient, leads to filling up the hard drive and takes resources from the server and personnel to maintain.

We either need a way to archive old content, or tagging each year's records so we can switch between them

The issue mentions no files, tests, or entry points. Start by locating the current yearly reset and record-storage flow, then compare archiving old content with tagging records by year. Done should preserve prior years, allow switching between them, and avoid the current manual reset process.

Written by the indexing model from the issue text.