also see show history of inclusions and forms

---

I think we are getting to the point that this should be done soon. In the long run, we want a deeper refactor of revisions, but at a minimun we need to add a) type and name changes to revision history, and b) grouping changes in revisions to a single model event. All we really need here is a field with the revision_id of the 'head' change of the event (event_id maybe?) and then do the revision search/list per each event_id which could have many revision_ids. It may also be useful to be able to join several model level events to the same event_id based on being close in time and from the same user/session.

---

can you connect this argument to a biz/community rationale? I really want this, but it's not a priority I'm hearing from clients / users.