1861 results found

1. Incorporate All AI Metric Types/Access Method from recent 5.1.1 COUNTER Standard Update into Analytics

   Counter Standards were recently updated to incorporate new metric types and new access methods for AI Bot Traffic within COUNTER standards (https://www.countermetrics.org/code-of-practice/best-practice/bp-ai/). Requesting that Ex Libris incorporate all metric types and the new access methods into analytics.

   45 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add "Available for Group" record fields to Analytics

   Currently, Analytics exposes which groups have Available for Group records, but it doesn't expose the other fields in those records.

   For example, Analytics can show that a collection is available for Group A and Group F, and it can show that Electronic Collection Proxy Enabled is set to Yes at the collection level; however, it can't show whether proxy is enabled for Group A or Group F.

   For Network Zones, and institutions that make extensive use of Available for Groups, the lack of access to these fields in Analytics means we can't periodically audit and correct configuration inconsistencies and data entry errors. It also hinders the progress of large-scale system change projects that require reviewing and selectively updating group-level collection, service, and CDI settings.

   Currently, Analytics exposes which groups have Available for Group records, but it doesn't expose the other fields in those records.

   For example, Analytics can show that a collection is available for Group A and Group F, and it can show that Electronic Collection Proxy Enabled is set to Yes at the collection level; however, it can't show whether proxy is enabled for Group A or Group F.

   For Network Zones, and institutions that make extensive use of Available for Groups, the lack of access to these fields in Analytics means we can't periodically audit and correct configuration inconsistencies and data… more

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Analytics  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Add Analytics support to compare "Available for Group" settings on electronic collections and services

   Currently, Analytics can show Available for Groups on the electronic service or, if none exist there (if they're inherited from the electronic collection), then on the electronic collection.

   However, we can't report on discrepancies between collection-level and service-level groups.

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Analytics  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Partner Details for Filled Borrowing Requests should reflect the partner that filled the request

   Currently, when creating an analytics report for filled borrowing requests and using the Partner Name, Partner Code, Partner ID, and/or Partner institution fields, the report displays all of the partners that were in the rota for the request and the same value in the Num of Request Filled column for all partners. This is confusing for filled requests as it incorrectly implies that a request was filled by each partner in the rota. When a Partner Active Status and Num of Active Partner Requests filters are added to the report, it is clear that only one partner remained active and filled the request. We would like to have the Num of Request Filled field clearly indicate the number of requests filled (as displayed in the Num of Active Partner Requests field) and the partner that filled the request when the partner details are added to a report.

   Please see the attached screenshots of the analytics report results.

   Currently, when creating an analytics report for filled borrowing requests and using the Partner Name, Partner Code, Partner ID, and/or Partner institution fields, the report displays all of the partners that were in the rota for the request and the same value in the Num of Request Filled column for all partners. This is confusing for filled requests as it incorrectly implies that a request was filled by each partner in the rota. When a Partner Active Status and Num of Active Partner Requests filters are added to the report, it is clear that only one partner remained active and… more

   •  

   •  

   2 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Resource Sharing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Reactivate deferred order POLs in bulk

   For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.

   We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a REST API process to update the POLs and ensure the records are consistent and ready for processing.

   At this point, however, reactivation can only be performed manually through the Alma UI, requiring staff to reactivate each POL individually. Having to move from a largely automated, bulk workflow to a one-by-one manual process is time-consuming and inefficient.

   Could Ex Libris provide a supported way to reactivate deferred POLs in bulk, either through an existing job, a new workflow option, or a public API? This would allow institutions to return deferred POLs to In Review and continue them through the standard acquisitions workflow without requiring manual intervention for each individual record.

   For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.

   We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a… more

   12 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Alma Mobile: scan in sort order and remove automatic active curser

   Two suggestions that would greatly improve the workflow in the Alma Mobile app.

   First, please stop placing an active cursor in the barcode field when switching to Scan In from the Pick from Shelf area.

   When the cursor is active in the input field, it automatically opens the keyboard on the phone. As a result, I have to close the keyboard every time before I can access the button used to scan a barcode with the camera.

   Secondly, please make it possible to sort scanned-in items in either ascending or descending order.

   Currently, after each scan, I have to scroll all the way to the bottom of the list to see the action required for the item I just scanned. This is an unnecessary inconvenience. Ideally, the most recently scanned item should appear at the top of the list.

   Two suggestions that would greatly improve the workflow in the Alma Mobile app.

   First, please stop placing an active cursor in the barcode field when switching to Scan In from the Pick from Shelf area.

   When the cursor is active in the input field, it automatically opens the keyboard on the phone. As a result, I have to close the keyboard every time before I can access the button used to scan a barcode with the camera.

   Secondly, please make it possible to sort scanned-in items in either ascending or descending order.

   Currently, after each scan, I have to scroll… more

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mobile  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Wildcard search for MMS ID.

   When working in conjunction with Excel, pasting MMS ID will be limited by the floating point standard and truncate the the last 3 digits to '000'. Only just realised this, having wildcard search would allow me to at least more efficiently identify and retrieve the now corrupted MMS ID I've been pasting into Excel.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Analytics  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Add Resource sharing requesting to block_request_if_not_loanable

   Currently blockrequestifnotloanable only includes holds and bookings for items we own. And digitization requests, if you are using that functionality and not doing the fill locally workflow. We use the fill locally workflow.
   A block on resource sharing requesting if people meet criteria of blockrequestifnotloanable block parameters, is essential. We are particularly trying to catch those with fees in excess of a certain amount who won't be able to check out the item they are requesting. With out it we will continue to see two types of behavior. users who cannot check out our items due to a block then getting around it by requesting a scan. Or placing a physical item borrowing request that they cannot check out once it arrives if the fee is not resolved. Thus, we will have incurred effort and in some cases expense for nothing.
   If some libraries don't want to block RS under these conditions, it should at least be option to add RS requests to configuration, or you can make it a separate configuration.
   We currently as a work around, before the functionality was even available at all, have a manual block created that we get put on automatically via an hourly job. And that gets taken off hourly. Based on criteria. While this is better than nothing -- it has its limitations. It is not immediate in being added or removed. As it is based off a set of users with fees over a certain amount and that repository search only includes actual active fees not transferred fees it doesn't catch a lot of students.
   The new blockrequestifnotloanable does include active and transferred fees because we have it set to a parameter to include transferred fees in the active fee bk=lock for fulfillment services. That is why if we could include RS requesting in this block it would cover all our scenarios.

   Currently blockrequestifnotloanable only includes holds and bookings for items we own. And digitization requests, if you are using that functionality and not doing the fill locally workflow. We use the fill locally workflow.
   A block on resource sharing requesting if people meet criteria of blockrequestifnotloanable block parameters, is essential. We are particularly trying to catch those with fees in excess of a certain amount who won't be able to check out the item they are requesting. With out it we will continue to see two types of behavior. users who cannot check… more

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Management  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Repository search for Users using Fine/Fee total sum field filter should include transfer fees

   Currently when search for users in the repository and filtering using Fine/Fee total sum field it only looks at users with fees with a status of active. The issue with this is that we have other configurations that include transferred fees in active fee field block and that leave transferred fees on users' accounts.
   By not including transferred fees when doing this repository search it makes it difficult to find users with transferred fees in real time. Analytics is nice but it is a day behind. It also means that the logical set I created to find users with active and transferred fees to add a manual block of requesting via a scheduled job does not catch all users.
   This need is exacerbated by the fact that the new blockrequestifnotloanable feature which does look at users with fee block which does include transferred fees in total does not include Resource sharing requesting only holds and bookings. So, this manual block is my only option.
   My only other option is for users with just transferred fees it to add the block manually based on analtyics report or data from bursars job. And then disable my job to remove automatically when fees drop below a threshold otherwise after I added manually it would be removed.

   Currently when search for users in the repository and filtering using Fine/Fee total sum field it only looks at users with fees with a status of active. The issue with this is that we have other configurations that include transferred fees in active fee field block and that leave transferred fees on users' accounts.
   By not including transferred fees when doing this repository search it makes it difficult to find users with transferred fees in real time. Analytics is nice but it is a day behind. It also means that the logical set I created to find users with active… more

   2 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  User Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Please add notification about blocks in Primo when requests are not allowed for the item or patron

    This idea relates to Fulfillment configuration setting ‘Prevent Requests for Blocked Loans’ in the Alma May 2026 Release Notes (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/080General/Configuring_Fulfillment_Jobs#block_request_if_not_loanable):
    In our Sandbox we changed the parameter key ‘blockrequestifnotloanable’ from NONE to PHYSICAL, which indeed activates a block when a pratron is not eligible to request an item. But now we see that in Primo the Patron is not informed about the reason for the block, so he/she gets lost.
    Please add a setting that shows the user a specific notification about blocks in Primo when requests are not allowed for the item or patron by the selected policies.

    This idea relates to Fulfillment configuration setting ‘Prevent Requests for Blocked Loans’ in the Alma May 2026 Release Notes (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/080General/Configuring_Fulfillment_Jobs#block_request_if_not_loanable):
    In our Sandbox we changed the parameter key ‘blockrequestifnotloanable’ from NONE to PHYSICAL, which indeed activates a block when a pratron is not eligible to request an item. But now we see that in Primo the Patron is not informed about the reason for the block, so he/she gets lost.
    Please add a setting that shows the user a specific notification about blocks in Primo when requests are not allowed for the item or patron… more

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Request to Add Bulk Pop-up Note Option to Update/Notify Users Job

    We would like to add pop-up notes to multiple patrons in bulk. However, there is currently no checkbox to add a pop-up note when running the job under:
    Admin > Manage Jobs and Sets > Run a Job > Update/Notify Users > Add Note

    At present, a pop-up note can only be added individually through:
    Individual Patron Record > User Details > Notes > Add Note > Pop-up Note

    It would be very helpful if a “Pop-up Note” checkbox could be added to the Update/Notify Users job parameters, allowing pop-up notes to be added to multiple patrons in bulk rather.

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Move the Fund and Ledger Fiscal Period Table from Configuration to Operational Acquisitions Module in Alma & Update Role Requirement

    We request that the Fund and Ledger Fiscal Period table be moved from the Configuration menu to the operational Acquisitions module in Alma and associated with the Fiscal Period Manager role. The management of fiscal periods is an operational, recurring activity performed by acquisitions and finance staff as part of the annual fiscal rollover process. Although the table is currently located under Configuration, updating fiscal periods does not represent a system configuration change. Instead, it is a routine operational task that must be completed each fiscal year.

    A transition of this kind aligns the location of fiscal period management with its operational purpose. It allows institutions to assign full fiscal period management roles to the appropriate staff without granting broader Configuration permissions, improving security and streamlining operational workflows. Lastly, it supports better separation of duties between system administrators and acquisitions/finance operations staff.

    Moving the Fund and Ledger Fiscal Period table to the operational Acquisitions menu would improve usability, streamline annual fiscal workflows, and enable institutions to follow the principle of least privilege when assigning Alma roles and permissions.

    We request that the Fund and Ledger Fiscal Period table be moved from the Configuration menu to the operational Acquisitions module in Alma and associated with the Fiscal Period Manager role. The management of fiscal periods is an operational, recurring activity performed by acquisitions and finance staff as part of the annual fiscal rollover process. Although the table is currently located under Configuration, updating fiscal periods does not represent a system configuration change. Instead, it is a routine operational task that must be completed each fiscal year.

    A transition of this kind aligns the location of fiscal period management with… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Acquisitions - General  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Add a Remediation Status/Step to the Digitization Workflow

    Alma's digitization process has no built-in status or step for accessibility remediation before a digitization request is delivered to a patron. Alma customers adhering to WCAG 2.1 AA under Title II ADA compliance for document delivery have no internal way to flag, route, or track items that need remediation (e.g., OCR correction, tagging, reading order) before fulfillment.

    We'd like to see a dedicated "Remediation" status added to the digitization workflow, allowing staff to route an item for accessibility review before it's marked complete and delivered. This would let Alma customers track remediation volume and turnaround time via Analytics and support consistent compliance with applicable accessibility laws across the community.

    Alma's digitization process has no built-in status or step for accessibility remediation before a digitization request is delivered to a patron. Alma customers adhering to WCAG 2.1 AA under Title II ADA compliance for document delivery have no internal way to flag, route, or track items that need remediation (e.g., OCR correction, tagging, reading order) before fulfillment.

    We'd like to see a dedicated "Remediation" status added to the digitization workflow, allowing staff to route an item for accessibility review before it's marked complete and delivered. This would let Alma customers track remediation volume and turnaround time via Analytics and support… more

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Fulfillment - Requests  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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 Primo should be the same for all content regardless of format.

    There should be an option to display on Primo the portfolio, to show it was inactive, but also to show that it is on order, so that it is consistent behaviour to the print books

    After raising a support call thinking this was something we could configure, we have been advised to raise it as an Idea so that it might be considered for development.

    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… more

    23 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Acquisitions - General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Display Requester's Name in Interlibrary Loan (ILL) Request Details

    We would like to request an enhancement so that the requester's name (Ful outgoing email letter-code: %reqName%) is displayed together with the Request ID in the request details when submitting an Interlibrary Loan (ILL) request to another institution.

    Currently, the receiving library can only view the Request ID. Since each institution uses its own ID format and structure, the receiving library cannot identify the requester based on the ID alone or access the corresponding user information.

    Displaying the requester's name along with the Request ID would allow the receiving library to identify the requester more accurately, improving the efficiency and accuracy of request processing.

    We would appreciate your review and consideration of this enhancement request.

    We would like to request an enhancement so that the requester's name (Ful outgoing email letter-code: %reqName%) is displayed together with the Request ID in the request details when submitting an Interlibrary Loan (ILL) request to another institution.

    Currently, the receiving library can only view the Request ID. Since each institution uses its own ID format and structure, the receiving library cannot identify the requester based on the ID alone or access the corresponding user information.

    Displaying the requester's name along with the Request ID would allow the receiving library to identify the requester more accurately, improving the efficiency and… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Add Kortext to the list of vendors for Autoholdings

    As many institutions in Germany need to switch to Kortext, it would be very helpful if ExLibris could add Kortext to the list of vendors for Autoholdings.
    This would be a great help, particularly for smaller organisations with limited staff.

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Enable NACO contributions in the MDE or linked data editor

    NACO libraries contribute authority records to the Library of Congress Name Authority File (LCNAF) through a distribution recipient (aka "NAF copy holder" or "full node"; https://www.loc.gov/aba/pcc/naco/nodes.html). Besides OCLC, one of the full nodes is Clarivate's Innovative/SkyRiver (https://iii.com/products/skyriver/). If Clarivate's Ex Libris Alma became a full node as well, NACO participants could create and edit LCNAF records in the Metadata Editor or even potentially Alma's linked data editor, rather than needing to use OCLC for this work.

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Metadata Management  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Add "Open Access" Electronic Access Type

    Please add "open access" as an electronic access type (like perpetual, current, current and perpetual) at both the portfolio and collection levels. With more resources being open access, it would be helpful to be able to mark them as such.

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. 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 here do not currently exist in the Excel template.
    First, there should be a third option for VAT type at invoice heading level: there is a column in "HINV" row which is titled "Inclusive", so that it can be filled at "INV" level as a boolean: thus, "True" stands for "Inclusive" VAT and "False" stands for "Exclusive" VAT, but Alma offers a third option, "Line Exclusive", which cannot be indicated in the Excel template as it has not been defined as a third option. In this case of "FACe" invoicing, "Line Exclusive" is the proper option to apply, and it cannot be indicated in the Excel spreadsheet for Alma.
    Second, last but not least, there should be another column at invoice line level (HIL/IL) where to indicate whether the invoice line is fully or partially invoiced. Every single test I have performed takes the invoice line as "Totally invoiced", and it is correct in most cases but not necessary in all situations. Furthermore, once uploaded it cannot be corrected in Alma, as this information stays in a non-editable state: the only "solution" to correct it in Alma implies deleting the [partially] invoiced invoice line and to create it once again, indicating that it's partially invoiced instead of fully invoiced.
    So, to sum up, I think that there should be a way to indicate in the Excel template that the VAT type is "Line Exclusive" and another one to indicate if an invoice line is fully or partially invoiced.
    Kindest regards,
    José Ángel

    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… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Acquisition - Invoices  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Option to automatically suppress Bib records when AutoHoldings portfolios are unlinked or deactivated

    The Issue:
    Currently, when using vendor AutoHoldings collections (such as Wiley, Elsevier, etc.), Ex Libris recommended best practice is to set "Automatically delete portfolios removed from service" to No. This protects institutions from permanent data loss if a title is temporarily dropped or updated by the vendor.

    However, when AutoHoldings unlinks or deactivates a portfolio in the Institution Zone (IZ), the portfolio remains in the system while becoming inaccessible. Because the bibliographic record is not automatically suppressed, patrons still encounter these titles in Primo VE as "Not Available" or broken links, leading to a poor user experience and unnecessary support tickets.

    Existing parameters like logicalsuppressnoavailinventory do not resolve this, because Alma currently treats an unlinked/inactive AutoHoldings portfolio in the IZ as "active inventory", preventing the parameter from hiding the Bib record in Primo VE.

    Suggested Solution:
    Introduce a built-in feature or automated scheduled job that allows Alma to:

    Automatically suppress Bib records from Discovery when an AutoHoldings update unlinks or deactivates its associated portfolio (without requiring complete portfolio deletion).

    Automatically unsuppress/reactivate the Bib record if the portfolio is later re-linked or reactivated by a subsequent AutoHoldings job.

    Why this is needed:
    Libraries need a way to maintain an accurate discovery catalog for patrons in Primo VE while maintaining safe, conservative collection management settings in Alma without resorting to risky portfolio deletion or manual set maintenance.

    The Issue:
    Currently, when using vendor AutoHoldings collections (such as Wiley, Elsevier, etc.), Ex Libris recommended best practice is to set "Automatically delete portfolios removed from service" to No. This protects institutions from permanent data loss if a title is temporarily dropped or updated by the vendor.

    However, when AutoHoldings unlinks or deactivates a portfolio in the Institution Zone (IZ), the portfolio remains in the system while becoming inaccessible. Because the bibliographic record is not automatically suppressed, patrons still encounter these titles in Primo VE as "Not Available" or broken links, leading to a poor user experience and unnecessary support… more

    38 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating