Auditing Actions

[adambray]

It would be good to have an audit log of all important actions (reservations modification, equipment modification, checkin/checkout, and maybe more).

[kwabboateng]

Would https://github.com/collectiveidea/audited work for this issue?

[adambray]

Hmm, that might work, but I think we should compare this with paper_trail. paper_trail seems to do much the same (including diffing between versions), and has the advantage of being supported up to Rails 4, and better maintained.

(Audited was last released about a year ago).

[kwabboateng]

Sounds good!

[shippy]

Checking this out. Audited seems mostly unmaintained, whereas paper_trail has a pretty active repo. The main thing to investigate is how many paper_trail features are in the Rails 3 version.

Also, rather than sticking all Reservation, EquipmentModel, EquipmentItem with has_paper_trail, we should probably be selective/restrictive about which attributes to archive. I'll start with all and figure out which are necessary as I go (and before I file a pull request).

[orenyk]

Based on recent feedback from BMEC, we want to make sure that we can keep a consistent reservation history, whether that's through some sort of logging mechanism or by soft-deleting reservations (or both).

[shippy]

Installed paper_trail in 888ceb1; the broken tests were a result of not updating the test database. (Silly me.) Planning to create an interface to view all these, and possibly have a path to restore to a previous state.

Current testing suggests that the gem saves enough information about each object that hard-delete is not problematic, since the information is preserved.

[shippy]

Created basic index in 3464671; if you check out the branch, it is viewable at log/index. To do: create a view of the version mentioned in the log, possibly link past versions from the Reservation view?

[shippy]

(Writing down thoughts so I don't forget them before Monday: one way to display past-version status this is to reify the version in log#show, then pass it to the actual reservation view. Or the view of any other version-ed object, since we intend to use paper_trail on Equipment Models and Equipment Items, too.)

[shippy]

There is too much logic in the views to implement the vision from previous comment, so e4806a8 adds a very rough view of version properties.

To do:

• Prettify the view so that it is clear to layman
• Add a table of changes to just this item (with a form of diff, perhaps)