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

1812 results found

  1. reminder

    I understand that there is an intention to add Reminders to the task widget. Since the reminder is at the bibliographic title level, would it be possible to add a "flag" that would display when retrieving records? This would provide a visual cue to staff that there is a reminder for this record, and they could investigate further if needed.

    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)
  2. Buffer periods for Last Interest Date for Borrowing Requests

    ISSUE: Quite a few of our borrowing requests are getting cancelled automatically by Alma, because people are setting a Last interest date of the same day or the next day. Unrealistic expectations are being created by the Last Interest Date. Yet, staff find it useful to know the Last Interest Date for borrowing requests where the patron indicates a date some time into the future.

    LOCATION: ILL request form, patron facing (e.g. in Primo VE).

    SOLUTION: Allow buffer periods to be implemented on the Last Interest Date. For example, a library may choose to create a 10 day buffer for…

    11 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. Display NZ activated Portfolios even if Related Records Services are enabled in an IZ

    In our consortial environement, we have activaded a number of portfolios on NZ level, which we would then expect to also be available in our IZs. Often this is not the case and instead of a specific article that is part of the portfolio, only the journal it belongs to is displayed under Services for Related Titles. As Ex Libris informed us, this is because Related Records Services are activated in our consortium, which leads the link resolver to display those related journals instead of checking if there is an NZ activated portfolio. Their solution to this would be to…

    73 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. Rename Fulfilment Request status "READY" to either "PENDING" or "INQUEUE"

    Currently Fulfilment request status READY - is misleading given its definition is
    "The request is still in the queue, not activated yet. Currently, there is no available item to fulfill the request."

    It does not even mean "ready to be requested" given the request has been made already.

    Note also "READY" is displayed in the User Request area in Alma, and this can be confusing to the client facing staff. They have to understand and be able to explain to clients that their requests are NOT READY yet despite the Alma labels says READY.

    See Case#10569064

    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)
  5. Alma - Standardize Cross-Field Validation Across Configuration Dialogs

    Request:
    Implement dynamic dependency handling within Alma "Add Row" dialog boxes to support Proactive Error Prevention.

    The interface should only present users with valid input field combinations, ensuring that logically impossible configurations cannot be constructed.

    While this request originated from a ticket regarding the Exclude Process Types from Publishing dialog, it identifies a broader need for platform-wide consistency in how Alma handles field relationships.

    Functional Gap:
    Currently, the "Exclude Process Types from Publishing" dialog treats [Process Type] and [In Process Type] as independent fields.

    • The Problem: Users can construct combinations that the system knows are invalid.

    • The Result: The user…

    2 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)
  6. Ability to create additional note fields in the physical item editor

    At the physical item Editor, we currently have access to one public note, one Fulfillment note, 3 internal notes and 3 statistics notes. We would need 3 additional public note fields visible to the user in Primo and 3 additional internal note fields.

    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)
  7. RS Pick Slip configuration

    Currently the FUL Incoming Slip Letter can only be configured to display the Library of Congress classification, and not the Item Permanent Call Number. This means the pick slip generated in the Resource Sharing lending workflow shows an incorrect call number.

    Please make the Item Permanent Call Number available as a configurable field in the FUL Incoming Letter, so that pick slips display the correct shelf location.

    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  ·  Resource Sharing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Request for Populating "Item Location" in Network Activity Loan List

    I am writing regarding the blank column in the Network Activity section.

    For institutions within a fulfillment network, loans belonging to another institution are visible in the Network Activity section. However, in the Loans list, the "Item Location" column is blank.

    If the “Item Location” column were also populated with the correct values, it would be much easier to manage differences in return policies that are dependent on the item's location.

    In addition, patrons sometimes claim to have already returned the item.
    If the "Item Location" column is displayed correctly, it will be able to ask the owning library to…

    12 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. Support "History" of "Interested User" in POL

    The "Interested Users" area of POLs in Alma currently doesn't have any "History" support; if an operator attempts to determine when or how changes were made to a POL's interested user or the notification settings for an interested user, there is no history to track changes to those fields. Having "History" support for this field would be helpful for maintaining consistency within the POL and for troubleshooting when unexpected changes are made.

    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)
  10. Display Open Access Indicator based on Setting at the Portfolio Level

    Currently, the Open Access (OA) indicator displays in Community Zone records when the record contains a 506 field with the following formatting:

    506 0_ $f Unrestricted online access $2 star

    Records in the Directory of Open Access Journals (DOAJ) collection are automatically enriched with this data, but not records in any other collection. The rationale is that the OA indicator may appear on records that are not available as OA in all collections, leading to a confusing display. However, this can lead to cases where institutions do have OA access, but cannot display the OA indicator.

    To avoid both of…

    196 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. ellipses in specific contexts(三点リーダー“…”)

    In Japan, we use ellipses in specific contexts.
    Please adjust both Cloud App and Alma so that typing three middle dots and converting them results in an ellipsis (“…”) with three dots centered.
    *Note: This is not three periods (“...”).

    I believe this issue is likely caused by the font type, language settings, or similar factors.
    Thank you for your cooperation.

    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)
  12. madelene.turnbull@otago.ac.nz

    Add ability to include or exclude specific location codes in the Retention / Deselection workflows

    Currently the retention and deselection workflows only allow selection for inclusion at the library level. It would be helpful to be able to include or exclude specific location codes within a library's collections, for example it would be helpful to be able to exclude from deselection recommendations all titles in our Special Collections location codes. Currently the only way to do this is to run the search, export results to excel then filter by collection code.

    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)
  13. DARA recommendations for autoholdings should ignore open access collections

    DARA recommends using autoholdings. However, it does so even when it really shouldn't recommend it. Situation: an institution has activated an open access collection, and doesn't subscribe to anything from that vendor, but DARA recommends using that vendor's autoholdings, which confuses librarians. The correct operation of the DARA recommendations would be to ignore open access collections.

    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)
  14. Shipping Cost Lender Rules - Partner Organization Type

    It would be great if ‘Partner Organization Type’ could be added as a parameter in the ‘Shipping Cost – Lender Rules.’ This would allow us to set the Partner Organization Type for new partners instead of having to select each new partner individually.

    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)
  15. Enhance Analytics Support for Authority Records (Additional MARC Fields)

    We would like to propose an enhancement to Alma Analytics for authority records.

    Currently, Alma Analytics provides limited support for authority fields, such as 1XX and 373. However, many other important MARC authority fields are not available for reporting and analysis.

    We recommend adding more authority fields to Analytics, including but not limited to:

    046 – Special coded dates (commonly used for birth and death dates of authors)
    372 – Field of activity
    374 – Occupation
    375 – Gender

    These fields are widely used in authority records and are highly valuable for data analysis, authority control, and research purposes.

    Providing…

    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)
  16. Allow for relative date searching on years in addition to days

    We have logical managed sets where we want to filter on publication year within the last two years and would like to be able to use a relative date search instead of having to adjust the year each year.

    10 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)
  17. Using License Terms and Display Logic Rules to hide certain collections

    Electronic Resources are not always available to all patrons at a subscribing institution, either due to region locking or prohibitive pricing for extending access to students at partner institutions/certain user groups. Currently in Alma/Primo VE there is no satisfactory way to stop these resources surfacing where a signed in user does not have access such as when Alumni or Walk In.

    The restricted user groups feature is overkill in this regard. We don't want to limit a user groups access to CDI or EBSCO content entirely, just select collections/databases based on the licence restrictions pertaining to their user group.

    What…

    29 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. Add full MARC records to CZ for Mohr Siebeck

    This collection of Mohr Siebeck eBooks contains many titles with metadata that are too poor and need to be enriched. Could you please follow up with Mohr Siebeck?
    MMS-ID: 9919375751300041
    Thank you for your intervention!
    Kind regards,

    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)
  19. Contribute URL Type (Override) to community-managed collections when contributing portfolio changes

    I locally changed the Free E- journals link for bioRxiv (PID: 53441287610000041) to a dynamic URL:

    IF(rft.doi)
    https://doi.org/openurl?url_ver=Z39.88-2004&rft_id=info:doi/{rft.doi}
    IF()
    https://www.biorxiv.org/

    This allows the links on all the bioRxiv CDI records to go directly to the article. However, I can't contribute this change to the community because the "URL type (override)" won't go with it. So, my idea is to include that setting with any portfolio changes contributed via community-managed collections. This will allow the community to write more dynamic URLs and perhaps get those Free E- Journals links to link directly to articles, rather than to the journal's homepage.

    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)
  20. Add purchase model to more auto-holdings.

    It is great to have purchase model added automatically for Ebook Central og JSTOR Books holdings, and it would be even better if we could get purchase model also when using auto-holdings for publishers such as Elsevier, Springer, Wiley, Taylor & Francis and de Gruyter. We have evidence based acquisition agreements with all of these publishers and it would be very helpful if we could see which titles were in the EBA corpus and which we have purchased, either through the EBA or by earlier collection purchases.

    108 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)
1 2 9 11 13 90 91
  • Don't see your idea?