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

1695 results found

  1. Link from POL to Full Record

    Provide a Link from POL to its corresponding Full Record.

    It would be helpful to be able to click on a link that takes the user into the full (i.e., main) record - including access to holding and item records.

    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)
  2. 3BK Luxury Flat In Noida

    Discover your dream home in Noida with a 3BHK luxury flat that combines elegance, comfort, and modern amenities. These premium residential hubs offer state-of-the-art facilities, 24/7 security, modern elevators, power backup, and ample parking. Located in prime areas, they offer easy access to schools, hospitals, shopping, and entertainment.call 7983028075 or 9711298311.

    1 vote
    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. add "Return Selected" to actions currently available for moving items checked out

    Along with "Renew Selected" in the patron loan page, add "Return Selected" to enable a single or global return of a loan or loans.

    1 vote
    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. When creating a new local portfolio generates a new bib record, the portfolio's material type should determine the bib's material type.

    ExL documentation states, "When creating a new bibliographic record, the portfolio material is not taken into account. Thus, when you add a local portfolio and set a specific electronic material type, a bibliographic record is also created, but with 'Book' as the material, regardless of the portfolio's material. When adding ISSN, the material remains to be 'Book'. "

    This is imprecise and creates issues for discovery: when I create a new portfolio for a Kanopy video and select Electronic Material Type=Streaming Video, the bib record is encoded for a book. So in Primo, the video's Resource Type shows as book,…

    46 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. Advances search für PO Lines - searching for "empty" categories

    In the advanced search for catalog data, it is also possible to search for content that is "not" included ("not contains...", "is empty", etc.).

    This is not possible in the advanced search for order lines, but in my opinion it would be useful to search for incorrect entries.
    I propose an extension in the advances search for order lines.

    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)
  6. Add "PO Line Owner" as an input parameter for Purchase/Invoice Review Rules

    Adding "PO Line Owner" as a parameter for Purchase/Invoice Review Rules would allow differentiation by location. Our main library uses student workers for ordering, and I want to be able to have review rules in place to catch potential mistakes. Our satellite location has one staff person doing all the acquisitions. These same review rules will be cumbersome for their workflow. Having separate rules allows each location to operate most efficiently.

    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)
  7. Improve job "Requests - Handle Expiration steps"

    The job "Requests - Handle Expiration Jobs" updates requests and at present, the output of the job informs only on the number of outputs. The job can block on a request-ID which then must be manually handled.
    In order to save time and better inform the lending libraries, it would be helpful to have at least an information on any Error-causing request, with it's request-ID. Ideally it would be great to also have an output of successfully handled requests in form of a list, which can be exported to Excel.

    Improve the job "Requests - Handle Expiration Jobs" with output…

    20 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. Additional "Suppress from FRBR/dedup" option and display

    When viewing a bib record, the pop-out information to the side of the screen lists whether or not the bib is suppressed from discovery and suppressed from search. It would be helpful if this info also contained whether the bib was suppressed from FRBR/dedup.

    Additionally, when you edit a bib record, you can select "Suppress from Discovery" and "Suppress from External Search" under the Record Actions dropdown menu. It would be helpful if there was also a "Suppress from FRBR/dedup" here.

    58 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. Mass deletion of purchase requests

    Purchase requests can be mass rejected but cannot be mass deleted after that, so they need to be deleted individually, which is frustrating and time-consuming.

    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)
  10. Duplicate "Discovery Interface Display Logic" functionality to Configuration > Discovery

    Many libraries have staff structures where discovery and fulfillment configuration are handled by different staff (who may be in different departments.) Having the "Discovery Interface Display Logic" menu in Configuration > Fulfillment means that discovery administrators must be granted fulfillment administrator roles to configure those aspects. In a "least risk" permission model, it would be much more preferable for those options to be on the Discovery Administrator menu - instead of fulfillment, or at the very least in addition to fulfillment, so that the extra role does not have to be granted.

    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)
  11. Update Email Records Letter XML to use tags instead of metadata

    Currently, the EmailRecordsLetter.xsl file has to use the <metadata> tag in EmailRecordsLetter XML. This prevents libraries from being able to customize the display of the emailed record.

    EmailRecordsLetter XML should have tags similar to other letters, like <title> and <mms_id>. This would enable libraries to customize and create a professional, modern email.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Ability to make bulk bookings in Excel and import (similar to updating calendars in Excel)

    We use the booking feature for student study rooms, but occasionally some (though not all) of these rooms need to be booked off for special events, i.e., convocation, reserving time for reference interviews, etc.

    Our library could benefit from the ability to create these bulk bookings in Excel (copying/duplicating rows) as we would when updating our hours of operation.

    Excel columns might include the barcode for the room, the barcode for the special patron account we use to block off rooms as needed, dates, start/end times, and a yes/no for whether the booking may override normal booking rules/restrictions.

    1 vote
    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. Ability to report on the source of a MARC record

    It would be useful to be able to report on the source of a MARC record in Alma Analytics. This should be part of the 'Titles' Subject Area, providing information on whether the record was created using a record from a Z39.50 query or via a scheduled or manual import job.

    If the record is imported via a Z39.50 query, the source bibliographic knowledgebase should be reportable (e.g. OCLC WorldCat, Jisc Library Hub etc.).

    If the record was created via an import job, the name of the import profile should be reportable.

    This would help libraries to better maintain statistics…

    3 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)
  14. Add "Rule details", "Terms of use", and "Fulfillment Policy" as shared descriptive dimensions with Fulfillment subject area

    We would find it very useful to be able to report on fulfillment activity as tied to configuration. For example, we'd like to be able to report on items that allow unlimited renewals versus items that allow renews but limit the time frame.

    From what I can tell, only the loan length is included in the Fulfillment subject area, but the terms of use information is in the Configurations (Limited) subject area. But, we cannot do a multiple subject report without them being shared dimensions in Fulfillment. It would be very helpful if they could be added.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 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)
  15. Request limit

    It will be useful to limit the number of request for a specific library. Likewise for loan limits.
    If an institution has more than one library then it may want, for example, to allow a patron to borrow from several of them. Then the order limit should be correspondingly larger. However, if the loan limit is larger than the request limit, this situation can be confusing for the user. For example - a patron has a request limit of 10, and loan limit 5 in Library A and 5 in Library B. However, for the moment he can request 10…

    19 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. Include MARC leader in General Electronic Services Bib Fields Enrichment

    The addition of bib fields enrichment for general electronic services has been helpful in creating service availability rules for GESes, but there is no way to configure enrichment based upon content in the MARC record leader. This is where primary resource aspects are noted, such as record type, bibliographic level, and whether a resource is under archival control. Being able to use this criteria when displaying or hiding a service would be much easier than the convoluted and imperfect workarounds we've resorted to.

    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)
  17. Expand webhook monitoring to all record types in Alma

    Libraries utilize the webhook tool in Alma to be notified when some events occur, and includes information on the results or status of that event. Unfortunately, the tool does not include all record types in Alma. For example, portfolio and representation records, though mentioned in Ex Libris webhook documentation ( https://developers.exlibrisgroup.com/wp-content/uploads/alma/xsd/webhook.xsd ), are not actually monitored by the tool. In August 2024, this was communicated to Ex Libris for these two specific record types, and a “planned for future release” clause was added to their page, but with no timeline. Ex Libris recommended submitting an enhancement. Please expand webhook monitoring…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Expand API access to all record fields across all record types

    Libraries frequently use API access to Alma records to complete a variety of tasks, provide services, and support special projects. Currently, the types of records and fields that are accessible via APIs are limited. For example, in bibliographic records, the 024 (UPC) field data is inaccessible via the API. Please Expand API access to all record fields across all record types.

    8 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. Allowing the relink of a holding from a bib record to another maintaining the call number even if the location is the same.

    Now in Alma if you try to relink a holding with the same location (ex.: ABC) and call number 123 (1) from a record to another that have already a holding with the same location (ABC) and call number 123 (2), the holding with location ABC and call number 123 (1) disappear and everything is under the location ABC and call number 123 (2),.
    This happens with a relink of a POL or an item.
    We want to maintain the call number 123 (1).
    If it is not possible to do it automatically at least a pop up message that…

    81 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. Allowing the Bulk Scan In App to Export List of Items Scanned

    When using the bulk scan in app, you get a list of items that have been scanned in and those that have errors. Currently there is no way to export this list into excel to be able to keep track of the errors. If you click off the app to check a barcode with an error, the information disappears and you have to rerun the bulk scan in again. It would be great if you could export the whole list at once to excel to have a good record of the those that were successful and those that had errors.

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
    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