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

1888 results found

  1. Update All Relevant Indicators When Correcting Preferred Terms Linked via Cross-References

    The recent enhancement to Preferred Term Correction correctly updates bibliographic headings when the preferred and non-preferred terms are in different authority fields (for example, 410 → 130), and changes the bibliographic field tag accordingly (e.g., 610 → 630).
    However, the current implementation does not fully synchronize MARC indicators between authority and bibliographic records.

    The enhancement documentation states:
    "When a bibliographic field is updated to an X30 field, the non-filing indicators in the bibliographic record will be adjusted based on the linked authority record. According to MARC21 standards, the 1st indicator of authority field 130 (Nonfiling characters) will be copied to…

    66 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. Ebooks on order in Alma should display in Primo like print books do

    There is a discrepancy between purchased ebooks and print book visibility in Primo when on order.

    E-resources (Portfolios) which are on order - but not activated (still only "in order") - are not seen in discovery (Primo VE).
    Whereas physical items that are on order and didn't arrive yet - are seen in discovery (Primo VE) as "on order".

    The lack of visibility in Primo of ebooks currently on order can lead to duplication of orders and therefore a waste of money, or extra admin to cancel erroneous duplicate orders.

    The option to make ordered content visible or not in…

    24 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. Please add more "View only" roles to Alma

    Alma already offers some "View only" roles:
    - Fund-Ledger Viewer
    - License Viewer
    - Course Reserves Viewer
    but there is still a need for more.

    Please add the following:
    - Invoice Viewer
    - Purchasing Viewer
    - Physical Inventory Viewer

    Thanks!

    135 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. Invoicing from file: add a "Line exclusive" option for VAT type and add a value at invoice line level for invoicing state (fully/partially)

    Hello, good morning!
    As I am developing an app that transforms an XML "FACe" invoice (the Spanish standard for electronic invoicing) to an Excel file that can be uploaded into Alma, I have find out that the current Excel template which is published by Ex Libris lacks some fields or options that I think should be taken into consideration. Alma lets upload some XML invoces, but not the ones that follow the Spanish standard.
    Previously, I opened a case in Support Center requesting some info about this topic, and the answer is that the options I am about to indicate…

    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)
  5. Linking Funds to Location Codes so the Funds allocation can be calculated by the ordered copies for the Location Codes

    My library recently moved to Alma, but we found that the location codes were not linked to the Funds. It is a big problem for us as we ordered more than 30 copies for 30 locations spending on 7 Funds, while the Funds calculation had to be done by excel table and inputted the amount manually. We have to spend an hour for one order eventually.

    What we expected (and suggested here is), just like our old library system, is when entering the Ordered Items part with location and ordered copies, the Funds with respective distributions shall be generated rather…

    98 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. Apply Automatic Convert to RS TOU when marking an item missing

    When requested items are marked Missing, there are no more copies of that title, and there is a TOU term for the patron/item that allows Automatic Convert to Resource Sharing, the request should automatically convert to RS.

    Currently, there is a TOU term of "Automatically convert to resource sharing," but this functionality is very limited to the use case of an expired pick from shelf item. ExL's documentation indicates this should be possible, but it is not -- when an item is marked missing, the request is automatically canceled, so any job that runs will not catch that the request…

    37 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. Add IZ-level option to hide the "Order It" plugin in the navigation bar

    In our Institution Zone, we discovered that the "Order It" plugin is not limited to Amazon websites, despite what the Ex Libris documentation currently states under "Supported Platforms". Ex Libris has since clarified that, although the original development focused on identifying Amazon fields, the feature can in principle work with any website that uses the same field identifiers in its HTML.

    At the same time, we learned that there is currently no option to hide the plugin from the navigation bar. In our tests, the feature produced extremely rudimentary bibliographic records, which might be more difficult to manage and could…

    40 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. COUNTER metric PR_P1 or DR_D1 Searches platform to calculate Total Usage in Analytics databases cost per use reports

    We request that the Total Usage field used in constructing the databases cost per use report utilize the COUNTER PRP1 Searches platform or DRD1 Searches platform metric.

    Within the group of university libraries that are part of REBIUN (https://www.rebiun.org/), we have agreed to use the PRP1 metric, or alternatively DRD1 Searches platform, to calculate the cost per use of databases.

    However, when configuring the report in Analytics, we encountered the problem that Alma uses the DR – Unique Title Requests metric. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/Alma_Analytics_Subject_Areas/E-Inventory#Cost_Usage

    Therefore, even if we build a cost per use report, it would…

    92 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 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)
  9. Keep deleted Alma objects in Analytics

    When I delete Alma objects such as PO lines, Purchase orders, course requests, invoices, purchase requests, they are deleted in Analytics as well. On the contrary, even if deleted in Alma, objects like bibliographic records or physical items are still accessible in Analytics.
    It would be great if other Alma objects were also accessible in Analytics even if deleted.

    20 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  ·  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)
  10. All NZ cataloger activities must be collected in Alma Analytics

    The Cataloger activity report in Alma Analytics displays only partial activity when catalogers work in the Network Zone. For example, it may display a delete action but omit record modifications, leading to incomplete tracking of cataloger actions. It is included in Known Issues (https://support.proquest.com/s/known-issues/knowledge-detail?recordId=kA2QO0000000jZp0AI) with status "No Further Action".

    166 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. Create new reports for Authority management

    National libraries and institutions managing controlled vocabularies require robust tools to ensure the integrity of their authority files. Current Alma functionality (Authority Control Task List) focuses primarily on the link between bibliographic and authority records. We propose a new set of dedicated Authority Management Reports to identify internal inconsistencies, errors, and redundancies within the authority files themselves.

    Proposed Reports & Functionality

    · Orphan Authority Records: Identifies authority records without any associated bibliographic records. Crucial for cleaning up legacy data or unused headings.

    · MARC Encoding Errors: Detects structural errors within authority records (e.g., missing mandatory fields like 008, invalid indicators,…

    53 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. Persistent User Group Data in Borrowing Requests Subject Area

    We would like to request that the Borrowing Requests subject area in Analytics captures and stores the patron's information (specifically the User Group) at the time of the transaction, rather than pulling the current status from the user record.

    Currently, historical reports on borrowing requests reflect the requester's present-day group. If a student who made a request three years ago is now a staff member, or if their record has been deleted, the historical data is either overwritten or lost. This makes the data entirely out of context and renders historical analysis and longitudinal reporting impossible.

    In the Fulfillment subject…

    62 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  ·  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)
  13. Alma Analytics: Cost per Use - calculate use on all platforms

    When using Alma Analytics for cost per use reports, only use from the chosen COUNTER Platform are calculated. In part, this is because in Electronic Portfolio Editor, only one COUNTER Platform may be chosen. This is a problem for our Ovid Journal collections as Ovid records use across three platforms. We would like all use to be calculated in Alma Analytic Cost per Use reports, whether this be solved by allowing us to choose multiple platforms in Alma or have Alma Analytics calculate all use, not just the COUNTER Platform chosen in Alma.

    36 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. Display License TOU link with CDI Link-in-Record type records

    We display license terms of use for our electronic collections as we try to be compliant with the subscriptions. We noticed that with CDI link-in-record type records, there is no link for the license TOUs. It would be nice if there was a way to link to the TOUs or add a note to be able to link to TOUs.

    15 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. Authority control for name-title access points: link bibliographic 1XX+240 to authority 1XX $t

    In Alma, bibliographic records containing 1XX + 240 do not establish an effective authority link with the corresponding name-title authority record (1XX $t).

    As a result, when the authorized access point for a name-title authority is updated (for example, a change in the title portion in 1XX $t), the update is not propagated to the linked bibliographic records. The 240 fields in affected bibliographic records remain unchanged and must be identified and edited manually.

    This behavior results in:

    · High manual maintenance effort

    · Increased risk of inconsistencies between authority and bibliographic data

    · Reduced effectiveness of authority control in…

    48 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. Allow faster 'All titles export' in UI by adding option to only download titles' MMS ID

    We are grateful for 30 local parameters in Alma Analytics, but frankly could use way more (i.e. as many as the number of MARC fields that we use that are not already available in Analytics. For example '035' is available in Analytics via 'Network Number'). Sometimes to get Analytics to output what we need, we must run the search in Alma first. However, the 'All titles export' is intolerably slow for as few as 5K bib records. Possibly, if the Tech team thinks that 'All titles export' UI time could be shortened by adding an option to output/export only MMS…

    12 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)
  17. Please integrate aspect „last copy within library / IZ / NZ“ within “Withdraw Physical Items” process

    Ex Libris recently expanded the “Withdraw Physical Items” process to include more individual configurable aspects.

    We would like to suggest to include the aspect “last copy in the IZ (thus: do not delete!)” as well, which would protect the last copy from deletion.

    It would also be great to be able to protect the “last copy in the same library" or "last copy in the NZ” during the deletion process, if necessary.

    We are familiar with the “Retention Information - committed to retain: yes” feature, but it is too troublesome for us to use, because we would have to actualize…

    106 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. Subfield u must be preserved when linking to the Shared Authority File in fields 100 and 700

    When cataloguing conference papers and articles, it is important to be able to specify the authors’ affiliation at the time of publication. According to the MARC structure, subfield u in fields 100 and 700 is intended for this purpose. However, when links are created in the MDE (F3) to the Joint Authority File for the German-speaking region (GND) in these fields, subfield u is removed. We would therefore like subfield u to be preserved when linking to the authority file in the same way as for subfield 1, in which the ORCID ID is indicated. This would improve visibility and…

    18 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. Request expiration date in Analytics

    We are trying to retrieve a list of items that are about to expire on our holdshelf but it looks like the Request Expiration Date is not available in the Requests subject area in Analytics. We were expecting it to be in the Request Details section.

    Of course, the holdshelf is just a specific case, limited to patron physical item requests, but this idea can be extended to any other request type in which an expiration date is meaningful.

    32 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  ·  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)
  20. Linked Data Enrichment Moves $e Relator Subfields to Incorrect Positions When Saving Authorities with F3

    When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.

    Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end…

    80 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)

    Can you please confirm whether the $e subfield is always expected to appear before $0 and $1 in your workflows? If this is consistently the case, it may be possible to address the issue using an XSL normalization rule to automatically position the $e subfield before these subfields.

  • Don't see your idea?