Add way to signify a new year's worth of data

[liam-middlebrook]

This is relatively low-priority, but we need to create an endpoint for the evals director that will change the active tag in all applicable db entries to false.

[mbillow]

I don't think an active field is what we want. That allows history to blur together in one large "inactive" pool. Instead, I think we would just have a "eval_year" field that we store with each record and then in settings have a "current_year" value that the eval director can change.

[liam-middlebrook]

There is a date and active field on most tables already.

[liam-middlebrook]

Would it make sense to make this a button for the evaluations director to activate at the end of the standard operating session? Or should this be just automated to happen every June 1st? (with the exception of conditionals that have not expire)

[gambogi]

The way we approached this in the csh-eval data model was to create an evaluations table which had start and end date entries per member, as well as evaluation type (i.e. freshman or membership), and then query for active evaluations based on the date. Projects, seminars, and attendances in that range counted toward that evaluation.

[liam-middlebrook]

Interesting. We already have our models with structures in place to do something like this, so the implementation as far as that goes isn't much of a concern. This is really targeting the way for an evals director to signify the change between operating sessions and rather or not it should be automated.