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

1728 results found

  1. Open / Closed Stacks Request Possibilities Priority

    Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.

    In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.

    We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item…

    65 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. Add 245 subfield n to the letter XML node for title

    Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.

    We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
    245 10 |a Prisma Physik |n 1
    245 10 |a Deutsch |n Drei
    245 00 |a Prisma |n 1
    245 10 |a <<Die>> Sprachstarken |n 2 |b…

    65 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. Ability to use import profiles on OCLC Connexion exported records

    Currently import profiles can applied to Marc files that are uploaded into Alma. One can use the import profile to specify match methods, tell Alma how to deal with matches of existing and incoming records (overlay, merge, or use NZ record), and also specify inventory info to map the Marc 949 field to holdings and item records. Although the OCLC Connexion integration profile deals with importing records it lacks the features described in the previous sentence. Please see screenshot of settings in Oclc integration profile versus in an import profile.

    Basically we would like the ability to specify an import…

    64 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. Colour/shade gradients to tell the different between license statuses (Active, Retired, Deleted)

    In the list of licenses it would be useful to have a colour/shading gradient difference between active and inactive licenses.
    For example, when you delete a license it still remains in Alma, it is just given the status deleted. This is fine as it provides a history, however, as the deleted licenses in the list look exactly the same as active licenses, apart from the status note it can often be difficult to tell the active and deleted licences apart, especially at a glance.

    It would be useful to change the colouring/shading gradient, for example, grey out the text, for…

    64 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. Display logic rules should work on Primo users NOT logged in

    Display logic rules currently only work if a user logs in Primo. Also, the rules only work to hide a service (not show a service). Also, Primo New UI does not allow forcing users to log in.

    So, we have a scenario where we want CCC Get It Now articles to display only for our Faculty user group. However, the article links are displaying to everyone (guest) - until the user logs in and then the links are hidden for everyone except our faculty. Because everyone starts out in Primo as guest, this defeats the purpose of the rule.

    Another…

    64 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. Vendor Interface > Contact Information > Email addresses

    The default display for Vendor Interface > Contact Information > Email addresses, does not include an option to display the "description" field on the main page. The fields available for display are: Preferred, email address, created by, creation date, and type.

    Since most correspondence with vendors and sales representatives happen by email now, it would be useful to be able to see the description on the main page without having to click on .... and Edit for each email listed to see who is the correct contact.
    Some email addresses do not contain the person's full name, and if you…

    64 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. Update 863/864/865 when items are withdrawn

    There is a crucial step missing in the Automatic Generation of the Summary Holdings Statement Based on Items process. The process is documented here:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/020Navigating_the_MD_Editor_Page?uxp=true#Automatic_Generation_of_the_Summary_Holdings_Statement_Based_on_Items

    When items which are linked to the Holdings record are withdrawn, there is no process to update the Holdings record 863/864/865 fields to create an updated 866/867/868 field. When items are withdrawn, the user has to manually edit the Holdings records.

    Since the creation of the 863/864/865 field is now automated based on received items being linked to the holdings record, there is a need for the 863/864/865 to be automatically re-created when the linked…

    64 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. Mechanism to validate binary MARC record structure

    There is currently no mechanism within Alma to ensure that exported or published binary MARC records have valid record structures. Even though Alma uses MARCXML and is not impacted internally by invalid binary MARC, libraries must still provide binary MARC records to external entities in the course of regular business (vendors, outsourcers, agencies, other stakeholders).

    Structurally invalid binary MARC records significantly hamper data sharing for libraries. A third party application, MarcEdit, can be used to validate MARC record structure, but since our data is stored in Alma, there should be a mechanism native to Alma that validates binary MARC structure…

    64 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 Alma users to choose the match routine when using the ‘Link to Community’ tool to link portfolios to a community zone collection.

    The ‘Link to Community’ match routine for matching local portfolios to the CZ is too restrictive. We would like to be able to use our local bibliographic records and have them link to portfolios in the CZ, however, the match rate is dependent on what metadata is available in the CZ records, which are often brief and do not contain the ISSN/ISBN match point that Ex Libris has selected for that collection in the CZ.
    Alma users should be able to choose the match routine when using the ‘Link to Community’ tool, similar to how we can choose the match…

    64 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. The line separator in Analytics outputs is normally a semicolon, but should not be ambiguous

    In various exports from Analytics, it was noticed that the characters present in Alma are output as follows:

    • sharp bracket < present in Alma is put out by Analytics as & l t ;
    • sharp bracket > in the Alma (bibliographic data) material is put out by Analytics as & g t ;
    • ampersand & as & a m p ;

    This is likely due to HTML being used as the export format in Analytics. However, for the further processing of large amounts of data, it is disruptive that a semicolon is used for coding here. The semicolon appears both…

    64 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add "Managed By Library" facet in "Monitor Requests & Item Processes"

    There's a need to check the list in transit from a library to another library.
    In "Monitor Requests & Item Processes" menu, there are 'Pick up location' or ' 'Owning Library' facets.
    But there's no facet to check destination of the item.

    It will be very helpful, if the facet is given by Alma.

    63 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. Make it possible to change the bib reference on orders with a CKB ID

    Currently, it is not possible to change the bib reference (relink a bib) on orders which have a CKB ID, only those which have an MMS ID. I think it should be possible to change the bib reference on all orders.

    63 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. Set the sender address to the address of the staff that made the PO and automatically forward the mail to the said staff.

    With multiple librarians handling PO, this can help us keep better track of PO details and increase process efficiency.

    63 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. Hide ‘edit’ option from My Library Card > Personal Details for specific user groups only

    In Alma you can choose to hide the "Edit" option from the 'Personal Details' under 'My Library Card' for ALL your users by changing the parameter key 'primopatroninfo_updatable' to N

    This works fine if all your users are set up as external users who automatically gets their contact information updated from a system outside Alma. But if you set up your students as external users and public users as internal users you will have to choose between letting the students update contact information that will be wiped out next time data is loaded in to Alma or not…

    63 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. A "kill switch" for General System Administrators to immediately disconnect individual Alma users

    Use case: A library employee (student or staff) responds to a phishing text message by providing their Single Sign-On (SSO) credentials; SSO is used on our campus for Alma authentication. I want to (1) disable all the roles on the library employee's account except for Patron; (2) disconnect the employee if he/she/they/* has an active session in Alma; and (3) be notified with the IP address of the originating computer if he/she/they/* attempts to log in again. I would like to accomplish both #1 and #2 by checking a box ("Disable roles") and moving a slider ("Disconnect user"), WITHOUT having…

    63 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. Retain Data in Interface Records

    We really like the multiple tabs on interface records that allow us to record different admin logins and statistical information.
    Publisher and vendor changes happen pretty frequently in our environment and we foresee needing to move interfaces from one vendor to another on occasion.
    We just found out the hard way that when an interface is deleted from a vendor record and then added to another vendor record all the information that was in the various interface tabs gets wiped out. Can something be done to preserve the information that was hand keyed into the interface tabs?”

    62 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. Under Electronic Service Editor to have the ability to remove portfolios in bulk.

    In the electronic service editor you have the ability to deleted all the selected portfolios. I would like the ability to simply remove the portfolios in bulk from the collection.

    62 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)
    Dana Moshkovits responded

    Clarification was provided regarding the functionality requested – which is not to delete portfolios but rather detaching portfolios from the collection and setting them as standalone portfolios.
    Re-opening the idea.

  18. Analytics - Last Return Date

    It would be extremely useful to be able to report on the Last Return Date; this should be added to the Physical Items subject area alongside the Last Loan Date parameter

    62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Changing Holdings or Relinking Item is Possible Only in User Role Scope for SOURCE library

    At present staff can move items from a library they don’t have a user role for, to a library they do have a user role for. For example, staff could move an item from the Rare Book Collection holding in one library to a Withdrawn holding in another library if they have the user role for the latter.

    In the May 2021 release changing holdings for an item or relinking an item to a bibliographic record required the TARGET library to be within the scope of the user role. This prevents moving item or changing holdings for an item if…

    62 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. The Lost item process fee (aka Lost item fine) should be automatically removed when an item is found.

    The Lost item process fee (aka Lost item fine) should be refunded when an item is found. Currently, only the Lost Item Replacement Fee is refunded. This requires staff intervention, having to manually waive the fine. This is not always caught when books are returned through the drop slot, for example. It causes confusion for both patrons and staff when a fine remains on a patron's account for an item that has been found.

    62 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