Registry maintains two types of records for history, support, and audit purposes.
History Records
History records are created at logical points during Registry operations, such as inviting a new person to the platform, or adding a person to a group. These records are stored in the table cm_history_records, and can be linked to a CO Person, a CO Person Role, and/or an Organizational Identity. For example, changing an Organizational Identity name will have a history record linked to that Organizational Identity only, whereas adding a CO Person to a CO will have a history record linked to both the Organizational Identity and the CO Person.
Additionally, administrators can manually add a history comment to either a CO Person or an Organizational Identity. To do so, retrieve the appropriate person or identity record, then click "View History", then click "Add".
Administrators can view History Records through the Registry web interface, however records are viewable according to certain rules:
History Record Applies To | Authorized Viewers |
---|---|
Organizational Identity | If Organizational Identities are pooled, any Administrator. |
CO Person | CO and COU Administrators within the CO. |
CO Person | CO Administrators within the CO, and COU Administrators for the COU of the CO Person Role. |
CO Person | CO Administrators within the CO, and COU Administrators for the COU of the CO Person Role. |
Changelogs
Database level transactions logs are not fully implemented, but are available for select attributes as of v0.9.4. (CO-95)
Changelogs are created on any change to a supported database table. Changelogs are stored in the active table itself. When a record is updated or deleted, the record is updated accordingly (a deleted flag is set in lieu of an actual delete), and the original record is copied-on-write to a new row in the database.
Currently, Administrators cannot view Changelogs except by directly examining the underlying database.
Additional technical information is available here.