Skip to content

Alma

Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

145 results found

  1. Death of a patron - Need to immediately and permanently cease sending all letters

    In the unfortunate event that we learn that a patron passes away, we need a quick, clear, and finite procedure to immediately and permanently cease/stop any and all IZ and NZ notifications to the patron's email account, especially those that are tied to a SIS load (Example: Banner). College administration directs the library to ensure no emails are sent to the deceased's email account. We need to be able to definitively state to college administrators "Absolutely zero communications, automated or manually generated, will be sent regarding the deceased patron's library account from the IZ or NZ."

    Existing work-arounds include toggling…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Create role profile from specific user roles.

    Once we have assigned roles to a certain user, and we see that the functionality is correct, it would be interesting to be able to create a profile directly with the roles of this user.
    In this way, we can assign the same roles to another user.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Batch upload (from template) of internal users

    We do not use external SIS upload. However, it would be fantastic to be able to batch upload internal users from a template, like we can do with portfolios. At the start of each school year, we could use the list of incoming students very easily.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Generate PIN as an option in the Update/Notify user job.

    Please add "generate PIN" as an option in the "Update/Notify user job".

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Dynamically create statistical category and type specified in the user xml notice imported from SIS

    The user.xsd xml shema contains statistical category an type description.

    <user_statistics>
    <user_statistic segment_type="External">
    <statistic_category desc="STAPS">
    4200013
    </statistic_category>
    <category_type desc="Code SISE">
    BSISE
    </category_type>
    </user_statistic>

    However, when imported from SIS, il the category and type in a user.xml file imported from SIS does not already exist in Alma configuration tables, it is not imported in the statitistical type specified.

    In the example below, category 4200013 and its description STAPS, type BSISE and its description Code SISE required to have been already created in Alma configuration tables.

    If its not the case, the category 420003 is imported with NO type
    and no description.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. add course name to the course tab on the user profile

    At the moment the only columns available in the Course tab on the user profile is course code and section.

    Course codes will often consist of a line of numbers so the option to add course name as a column would add great value.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Change role attributes via SIS batch load

    I would like to be able to change user role information (roles status, expiration date, delete or add a role) via the Student Information System external integration batch uploads. Currently, user roles can only be modified manually in the UI or with an API call.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Allow replies to emails sent to users to be received in Alma

    When the system sends an email to users, it should be possible to for the user to reply to that email and the response to appear in Alma in the appropriate place (prob along with a notification so staff can see that there is a reply for them). This would avoid having to manage email conversations outside of Alma. Not only would this be of benefit to Alma, but it could benefit other Platform products such as Esploro and potentially Leganto.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow for including a block note when batch adding blocks through run a job

    Blocks can currently be added to a set of users through the Update/Notify User job; however, a note cannot be included. When placing holds manually, the option exists to include a note. When the note is essential to the block, we currently have to enter each block manually instead of using the job. Including the ability to enter a note in the batch job would save an immense amount of staff time.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. User action history report

    Our institution's security protocols require systems that handle confidential patron/student data have the ability to log backend staff user actions. After inquiring to ExL, the only way to know what a staff member has done in the system is to go through their individual history tab. However, this data is incomplete and doesn't give a full scope of what actions they took. In Analytics, the options provided are not useful and do not give us any useful information.

    We'd like to track things like:
    - When roles were issued
    - Who issued roles
    - Changes in configuration and who made…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Password reset

    It would be beneficial to all users to have a "Forgot your password?" link on the login page to get a reminder via e-mail, or be able to reset your password. This current system of having it completely controlled by the administrator is antiquated and needs to be replaced.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Have option to set Expiration and Purge Date to "Current Date"

    It would be useful to have a button that says "Today" or "Current Date" when changing either the Expiration date or the Purge date. We often have to update records for staff and faculty who terminate and having that button would save a lot of time.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Customize Patron Registration Form with more identifier field

    We would like to to have more than one instance of the drop-down menu (identifier1 field) and input field so we can fill in more than one identity type in the registration form for a quick registration of the patron.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. User update notification with loan information

    We would like to send out an email to users, who's account are about to expire. However, we want to have the users current loans added to the email as a table (like the borrowing activity email). The user and librarian can then see what they need to return before their account expires.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Users remove blocks

    It would be usefull for an operator to delete selected blocks in the tab block of an user card in the same way of fines/fees, marking them and delete them in one go.
    This idea because the operators can't run the job "Users - Remove Blocks".

    We think especially at those libraries where users are not always on time to return books and deleting them individually it's a waste of time.
    it is not nice to delete blocks one by one.
    It would be better if the operator could mark blocks and delete them in one go.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add 'Assigned date' to user roles

    We often need to know the date that a role was first added to a user's account. The status date is not static and because we use the API for updates from our SIS the status date often gets updated with random dates. The API updates also make the history tab difficult to use to track down role additions versus changes.

    We should be able to easily see a column that includes the date a role was initially assigned/added in the context of all of their roles in the General Information tab.

    We also need the date a role was…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Permit only public notes in patron files

    According to Swiss Data Protection Laws, all notes in a patron file have to be viewable by the patron.

    As consequence, we want either:
    - Only have public notes in the patron file. Non public notes do not exist. This may be an option that can be activated or deactivated by administrators.
    Or:
    - The User Viewable attribute is ticked by default. Again, this may be activated or deactivated by administrators.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Add option for patron name suffixes like Jr., Sr., or III

    Name searches in Alma for names containing suffixes like Jr., Sr., or III yield strange results.

    Example: Someone named Joe Johnson Jr. will have first name "Joe" and last name as "Johnson Jr." When performing searches in Alma for "Joe Johnson", "Joe Johnson*", or "Joe *Jr." will not yield any results.

    Alma looks for "Jr." as a last name rather than the person's surname. This isn't helpful when SIS has the suffix but the patron may not use the suffix all the time in their everyday life.

    Creating the option for a patron name suffix or updating the search for…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Login via code in addition to the link for the E-Mail Authentication

    Today the E-Mail Authentication only has the option of logging the user in via a link in the E-Mail. This restricts the user to logging in on a computer where they have an e-mail client of which excludes most kiosk solutions and makes it a hassle if the user usually uses their e-mail on for example their phone but uses Primo on another computer.

    Adding the option of logging in via a code (in the same e-mail) which the user can enter on the device where the user initiated the login process rather than the device where the user read…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base