Activity audit (knowing who's done what)
We expect a system to be accountable to an extent, and find it hard that there are no Aspire logs accessible. For instance, when a node has been deleted, there's no way of knowing who has deleted it (apparently our only method is to "ask around"). If lists are edited/deleted/archived, an administrator may well need to get the details of when this happened and who did it, if there are questions/audits/complaints/etc. Even if we are ourselves not able to do this, Support should be able to, so that we can get the information that we need. We cannot be fully satisfied with a system that appears to have been designed to allow actions to be untraceable.
We think this is a valuable idea and something we will wish to investigate in the future, however its not in our near term development focu so its on our longer term backlog
Catherine Riches commented
I'd really like to be able to track actions. It would also be good to be able to see 'recent changes' made to a draft list without first needing to publish the list.
James Winterman commented
This would make a huge difference if we could see who did what and when in a report. From a compliance perspective we need to know this information to prove lists are not being edited after the fact.
This is a basic functionality in any system so it seems odd that this has not been done before, or is not being treated as a priority.
Robin Farndon commented
We'd be very keen to see this functionality in Talis - while we've not had any issues as yet, several of our academics have expressed concern that they can't track who might make changes to their reading lists.
Jon Garner commented
We at Victoria University of Wellington would fully support this enhancement.
The original idea was proposed over 3 years ago, is there an update on whether it has been approved for development?
Susan Tegg commented
We are interested in this too. There are times when we need to know who did what. We are happy to log jobs to Talis or find it for ourselves but having no option is a disappointment. Keji - has it been added to the top of the list yet?
Georgina Parsons commented
Just to add other recent problems for examples: when a list is published, we need to be able to find out who published it. When a list is copied, we need to know what it was copied from and who copied it. When viewing recent changes for a list, we need to know who made those changes.