Batch update of role expiry dates via the UI.

We have hundreds of student staff who have expiry dates on their roles (see attached for an example). Every semester, we have to manually edit each and every role for every student. This process would be so much easier if we could choose multiple roles and then batch update the expiry date.

Thank You! Lisa

Many of our students can't work out when their items are due, maybe due to the increasing use of the US dating format, so they don't know if 4/10/16 is the 4th of October or the 10th of April. Using the actual months would decrease the confusion.

Currently the only control on allowing patrons to update info via Primo is either on or off:
http://screencast.com/t/kcSIvkkR3g

Would like the ability to say for example only Visitors user group can update info via Primo.

Currently you can add roles to a set of users as per http://knowledge.exlibrisgroup.com/Alma/KnowledgeArticles/Howtoaddaroletoagroupofusers%3F. However, if you want to add multiple roles you have to run the job multiple times and potentially for different scopes each time.

It would useful to be able to apply role profiles to a set of users, as you can predefine many roles in a profile.

It would be helpful if Alma had an email letter that was linked to the user expiry date and could be sent to the client once their account is due to or has expired.

Currently the patron purge functionality works based on the purge date.

It would be nice if there was an option to choose to use the expiry date rather than the purge date - we find that staff often forget to change the purge date when they extend the expiry date for patrons so using the expiry date would be more reliable.

The field user title should be definable as free text field (min 100 characters long), so that various combinations of user titles can be imported from the campus information system. Now this is not possible, because titles (resp. combinations of titles) have to be defined BEFORE importing users via API.

As a system administrator I want any new statistical category codes used in the student file import to be added to the table as they appear in the file. Voyager previously added the code and then a system administrator could add the description to match.

There is no point in timing us out of our specific library. It is super annoying to come back to my desk and find that ALMA has kicked me out of my library and that I have to select it again---the only library in the list of options, btw, making it pointless for me to "choose a library" in the first place. There's only one! Please turn that off. It is a bug, not a feature of the program.

Currently the user update job can send emails to patrons. However due to the technical aspect of creating sets and running the job our user services librarians prefer to take the information out of a dashboard and widget and add them to a template email in outlook. It would be better if a schedule job could be created to send out user update emails to logical sets. Specifically for users that are about to expire - and have loans to return.

When running a borrowing activity letter job, it will send an e-mail to patrons with no loans. Only fees. That is not neccessary. Would be nice to have a possibility to exclude those customers.

When you are assigning any roles that require a circulation desk attached, you have us choose the desk, select it, and then attach it. Why can you not just use the one I select and remove the attach step?

Currently rejected records from the SIS batch upload process are only identified in the event log. It would be very useful if the rejected records were saved to a separate file in XML format. This would allow for easier re-load once the load error is resolved.

When a users account is made inactive/active it does not currently show in the history tab. I would be extremely useful to be able to view when a users account becomes inactive.

It would be great to have a role that could view all information related to electronic collections and portfolios but not edit them. This would be helpful for overlap analysis and viewing other details for individuals who should not be able to edit electronic inventory. One use case would be for network zone access for members of a consortium who access but do not maintain consortial resources.

It would be nice to be able to log in to a user's Library Card as that user for various reasons, mainly related to seeing what the patron can see (which letters they are selected to receive, which loans are present and which can be renewed by patron, etc.).

This has been an immensely helpful feature within ILLiad, and with the ability to integrate Alma and ILLiad and allow users "one" library account to manage rather than several, it would be very helpful in troubleshooting users' questions over the phone or via email.

Enable deletion of staff users from historical records

Based on strong laws for data protection in Germany and in order to avoid efficiency control of the employees we need the possibility to delete the staff user from historical records.

Kende

Allow relabeling of field tags, such as changing CHRON I to YEAR, and ENUM A to VOLUME. Let libraries have the flexability to use the terminalogy that they prefer.