We want to use more automation and bulk options in Alma, as this has clear benefits and is one of the reasons we chose Alma for our library. But we are hindered by the current design for Alma to record outcomes as being made by “System”.

Issues with this include that:
• we cannot use the data to report on workflow efficiencies achieved by our staff in both Alma and Alma Analytics, which prevents using the data also for rostering and workload management both in the short term and long term trend analysis
• we cannot easily troubleshoot problems by immediately approaching the relevant staff for more information, which is extremely important to do quickly before memories fade, more data is overwritten, and logs are lost for case investigation

Examples of this, which are initiated by a user but recorded as “System”
• acquisition workflows such as packaging and sending POLs
• creating up to 99 items in bulk by use of a physical item template
• updating various records such as items by a job

Our argument that it is a staff member who initiates the action, and therefore the staff member should be recorded in the data.

It is requested that information such as “Created by”, “Modified by” and “Updated by” is always the Primary ID of the user account who initiated the action, whether by one-on-one or bulk automated workflows, not “System”.

Input is welcomed by comments of additional examples, for this pervasive problem in Alma.
Note: This submission is for the overall problem and should not be set to Completed only for individual examples shared.