Grouper Developers Forum

["Tom Zeller" <>]

In related projects we've approached the "logical description of each completed transaction" be either storing all changed attribute names or changed attribute names and values; this of course considers all data|objects to be sets of multi-valued attributes (rather ldap-y).

We've also attempted to track 'atomic' and effective changes (add memberA then remove memberA yields no effective change but 2 'atomic' changes), with significant resulting confusion in code but greater ease of use by applications.

As for storage, we've used growing log files which are both machine readable and (reasonably) human readable.

Simplistic: the history-of-changes table(s) could be comprised of generic change objects which consist of an (subject) identifier and a set of (multi-valued) attributes ?

TomZ

On Wed, May 28, 2008 at 5:10 AM, GW Brown, Information Systems and Computing <> wrote:

We need to flesh out exactly what the audit requirements are - doesn't mean we implement everything yet but I know they are considered very important for a lot of sites.

Gary