Audit Trail User Story Summary

User Story Summaries are for capturing notes about broad user stories, or user story themes, related to a particular topic. These may be used as inspiration and source material for creating specific user stories, which may in turn be implemented in various system releases. Some of these broad stories, or themes, may not be implemented in the 1.0 release.

*Note: Additional work needs to be done around the definitions of who is allowed to do the following. Some institutions use an admin, others a database administrator.

Go to Audit Trail Functional Requirements Home

Audit trail viewing

Admin can search for all newly created/amended/deleted records

Admin can view/export contents of all deleted records (note: deleted records to be archived)

Admin can view/export all changes to a given record by procedure

Admin can view/export all user login/logout times over a specific period

Admin can view/export system use by user (what did person x do yesterday?)

Admin can view/export system use by function (all new object records created in August)

Admin can view/export system use by function & user (all new vocab terms created by person x)

Discussion questions

Which of the above functions are appropriate for a user w/permissions vs. an admin?

Where do each of these viewings occur? Should viewing all the changes to a record be available for viewing within the record itself?

Does the system have a "flush" mechanism? How much archived data is too much (e.g. how long is every change to every field maintained?) What is realistic/expected?

CollectionSpace

Audit Trail User Story Summary

Audit trail viewing

Archives

Discussion questions