Presented on different version history options.
Prefers the pop up version because the “changed from” and “changed to” are right next to each other.
The other version requires switching between versions to see changes that are marked with yellow highlighting.
Request to have a window that contains all changes, not just changes on a specific date.
Tenant level - Library can decide if they want a version history at all or for a certain period of time or unlimited time.
Libraries have the ability to anonymize the change source in the version history.
Libraries also have the ability to exclude various fields from the version history.
There’s an additional permission needed in order to view user permissions and reading room access - so that will need to be kept in mind in version history since user permissions and reading room access can be displayed.
Fees/fines and loans are excluded from version history because those changes are already recorded in the Circulation Log.
There was a question of whether we need User Permissions in the version history because a person can have hundreds of various permissions.
There’s potential to limit the version history by field but right now, the thought is that is not needed and will probably not be developed now.
If the record is updated through an API but no fields are changed, would a version history be created? - Will need to test
If you set a time frame in the version history, what is the expected outcome? Do we limit the data displayed - showing a change was made but not what change or do completely remove the data?
Amelia volunteered to help right tickets for this project.