1902 results found

1. Quick printing of Loan receipt in requests for personal delivery

   In the workflow for items requested for personal delivery via the GetIt tile, all documents are sent to Quick Printing except for the one needed most to ship the requested item, namely the Loan receipt containing the delivery address (quick printing means: opening it in the browser’s print dialog). When scanning in an item picked from the shelf, the loan receipt is not sent to Quick Printing but only to the email address configured as Fulfillment printer and to the printouts queue, where our staff must then locate it and send it to a local printer.

   We work in a strictly closed IT environment and can neither install apps such as the Alma Print Daemon nor address local printers by email. Consequently, our fulfillment staff are forced to perform five more clicks per order than necessary when retrieving the printout from the queue.

   When the request is a regular Rapido request, a document with the recipient’s address (Resource sharing shipping slip) is printed and sent to Quick Printing when scanning in the requested item’s barcode in ‘Shipping items’. Why not offer this option for personal delivery requests made via the GetIt section?

   Further information: The Quick Printing for personal delivery via the GetIt tile worked until the February 2024 release. According to Ex Libris, the “new” behavior is the expected behavior in Alma. “When the circulation desk is set to print loan receipt the expectation is that the receipt will be printed only when check out is done at the circulation desk Loan tab. The receive action will trigger a Personal Delivery Notification email. The printing is intended to be handed to a person that is at the desk, and is therefore done only when loan is done from the loan tab.” After we opened a second ticket, we got the following answer: ”After carefully review of this issue, and investigating through related opened defects regarding this matter, we have concluded that the current behavior is considered to be working as designed. Making a change to this behavior could cause any number of issues for other customers who rely on the current behavior."

   We cannot understand these arguments. When we loan an item to a patron that must be sent by mail, we need a document with their postal address to be printed immediately so that we can continue without further ado with the process of packing and sending the item off. Sending an email that includes the delivery address to the patron is not very helpful in that situation. In addition, and as stated above, in some cases a printer cannot be addressed directly from Alma and we need the Quick Printing (browser print dialog) function. It works for other letters generated by Alma, also for Rapido requests for personal delivery. Why not for personal delivery requests via the GetI tile? For library staff, there’s no difference between a personal delivery request done via Rapido or via the GetIt tile – both need to be sent by mail and therefore a receipt with the postal address is necessary. We cannot understand neither why allowing the quick printing via browser again for this kind of requests should have any impact on other customers – if a library doesn’t need quick printing via the browser, it’s possible not to activate it (a configuration done individually by every staff user, btw).

   See also Salesforce ticket 08345918.

   In the workflow for items requested for personal delivery via the GetIt tile, all documents are sent to Quick Printing except for the one needed most to ship the requested item, namely the Loan receipt containing the delivery address (quick printing means: opening it in the browser’s print dialog). When scanning in an item picked from the shelf, the loan receipt is not sent to Quick Printing but only to the email address configured as Fulfillment printer and to the printouts queue, where our staff must then locate it and send it to a local printer.

   We work in a… more

   8 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  ·  Fulfillment - 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

2. 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

3. Option to mark Home Delivery addresses added during requests as "Preferred"

   Most of our patrons do not have a pre-registered address in their records, so we rely heavily on the Home Delivery option in Primo VE, which allows users to provide their address directly during the request process. While this feature is highly valued by our patrons, it presents a significant operational issue because these addresses are not automatically marked as "Preferred" in Alma. Consequently, this information does not appear on the patron’s activity page and, more critically, it cannot be retrieved within the Analytics Fulfillment subject area, where only preferred addresses are accessible for reporting.

   To resolve this, we request that addresses added via request forms be automatically marked as preferred. If this poses a conflict for other institutions, we suggest implementing a configurable parameter in Alma to allow each institution to decide whether these addresses should be treated as preferred by default. This change is essential for us to effectively monitor and analyze the high costs associated with home delivery services, which currently require inefficient manual workarounds due to this lack of data visibility.

   Most of our patrons do not have a pre-registered address in their records, so we rely heavily on the Home Delivery option in Primo VE, which allows users to provide their address directly during the request process. While this feature is highly valued by our patrons, it presents a significant operational issue because these addresses are not automatically marked as "Preferred" in Alma. Consequently, this information does not appear on the patron’s activity page and, more critically, it cannot be retrieved within the Analytics Fulfillment subject area, where only preferred addresses are accessible for reporting.

   To resolve this, we request… more

   21 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  ·  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

4. Expose valid pickup locations and digitization departments via API

   Problem:
   The API endpoint for creating requests currently requires mandatory information such as pickup locations (physical item requests) or digitization departments (digitization request). BUT: The API does not provide a way to determine valid values for these mandatory(!) parameters.

   Impact:
   That means, every application using this API (discovery systems, mobile apps, ...) has to implement its own logic to determine valid pickup locations or digitization department. This is cumbersome, error-prone and violates the DRY-principle ("don't repeat yourself") paradigm of programming.

   Solution:
   Since Alma already has that logic built-in, it would be a very easy solution, if the API would expose valid pickup locations and digitization departments for a given user + title or item.

   Problem:
   The API endpoint for creating requests currently requires mandatory information such as pickup locations (physical item requests) or digitization departments (digitization request). BUT: The API does not provide a way to determine valid values for these mandatory(!) parameters.

   Impact:
   That means, every application using this API (discovery systems, mobile apps, ...) has to implement its own logic to determine valid pickup locations or digitization department. This is cumbersome, error-prone and violates the DRY-principle ("don't repeat yourself") paradigm of programming.

   Solution:
   Since Alma already has that logic built-in, it would be a very easy solution, if the API would expose… 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…)
   0 comments  ·  APIs and Integrations  ·  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. Make bulk job reports explain why individual records were skipped

   When a bulk job finishes, please provide a downloadable report for records that were skipped or failed. For each record, the report could include its ID, the attempted action, the reason it was not changed, and a suggested next step where possible.

   This would help library staff distinguish records that need correction from records that were intentionally left unchanged, without opening each record individually.

   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  ·  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. Browse Shelf Listing Call Numbers - 852 $$j

   Under the current design, browsing shelf listing by 852 $$j is not a supported feature in Alma.

   Example:
   852 18 $$b SBG $$c 91 $$8 222 B $$h 22/Z 1244 $$= l $$9 00 $$j 22/Hbl E 600 $$9 09 $$x DE-22

   For the holdings' field 852 subfields $$h 22/Z 1244 and $$j 22/Hbl E 600, the holdings call number “22/Z 1244 22/Hbl E 600” will appear only when the browse term is “22/Z 1244 22/Hbl E 600” or “22/Z 1244,” but not when the browse term is “22/Hbl E 600”.

   We need a 'Browse Shelf Listing' that lists ALL existing call numbers completely and in the correct sequence, regardless of whether they are call numbers from the holding level or from the item level and regardless of whether they can be found in the holdings' field 852 $$h or in 852 $$j.

   This function is essential to prevent call numbers from being assigned or recorded twice. The selection 'All' within the 'Browse Shelf Listing' should fulfill exactly this requirement. However, the 'All' selection actually does not list all existing call numbers. This browsing logic does not meet all our needs.

   Under the current design, browsing shelf listing by 852 $$j is not a supported feature in Alma.

   Example:
   852 18 $$b SBG $$c 91 $$8 222 B $$h 22/Z 1244 $$= l $$9 00 $$j 22/Hbl E 600 $$9 09 $$x DE-22

   For the holdings' field 852 subfields $$h 22/Z 1244 and $$j 22/Hbl E 600, the holdings call number “22/Z 1244 22/Hbl E 600” will appear only when the browse term is “22/Z 1244 22/Hbl E 600” or “22/Z 1244,” but not when the browse term is “22/Hbl E 600”.

   We need a 'Browse Shelf Listing' that lists ALL… more

   78 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…)
   1 comment  ·  Resource Management - Physical  ·  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. Integrated peer-to-peer chat and collaboration network within Alma

   Establishing direct and agile communication between institutions using Alma would significantly improve daily workflows and collaborative problem-solving. Currently, exchanging specific information with librarian colleagues at other universities regarding day-to-day Acquisitions tasks (workflows, vendor issues, best practices) is complex and inefficient. Relying on traditional email often leads to dead ends, as we frequently do not know the right contact person, or responses are delayed.We propose that Ex Libris implements an integrated chat or messaging feature within the Alma platform. This tool would allow users to easily find and connect with peers in the same functional areas (like Acquisitions) across other user institutions. Enabling this direct knowledge exchange would enrich the user experience, foster a stronger community, and help libraries optimize their usage of Alma through shared collaborative practices.

   Establishing direct and agile communication between institutions using Alma would significantly improve daily workflows and collaborative problem-solving. Currently, exchanging specific information with librarian colleagues at other universities regarding day-to-day Acquisitions tasks (workflows, vendor issues, best practices) is complex and inefficient. Relying on traditional email often leads to dead ends, as we frequently do not know the right contact person, or responses are delayed.We propose that Ex Libris implements an integrated chat or messaging feature within the Alma platform. This tool would allow users to easily find and connect with peers in the same functional areas (like Acquisitions) across other user… more

   4 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  ·  Collaborative Networks  ·  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. Sync Tasks widget display groups to match the user-selected display groups under Customize Tasks List

   Currently the persistent menu Tasks function and the home page Tasks widget do not sync to display only the groups the user has selected. This leads to the Tasks widget being cluttered with information not relevant to the user and distracts from the groups they need to pay attention to.

   In an academic library environment, staff members often have specialized roles (e.g., an Electronic Resources Librarian who does not need to see Fulfillment or Resource Sharing task categories). When unchecked sections continue to display, it creates unnecessary UI clutter, forces users to scroll more than necessary, and reduces the overall efficiency of the Alma dashboard. Hiding these sections would provide a cleaner, highly tailored, and more intuitive workspace that accurately reflects a user's daily workflow.

   Currently the persistent menu Tasks function and the home page Tasks widget do not sync to display only the groups the user has selected. This leads to the Tasks widget being cluttered with information not relevant to the user and distracts from the groups they need to pay attention to.

   In an academic library environment, staff members often have specialized roles (e.g., an Electronic Resources Librarian who does not need to see Fulfillment or Resource Sharing task categories). When unchecked sections continue to display, it creates unnecessary UI clutter, forces users to scroll more than necessary, and reduces the overall… more

   •  

   •  

   16 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  ·  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. Physical journal records with holdings but no items to generate an identifier which can be used in an Alma workflow

   We would like the ability for physical journal records with holdings but no items to generate an identifier which can be used in an Alma workflow, e.g. to be put on hold, in transit etc.

   4 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  ·  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

10. Relationship designators should not be searched in Field 5XX, subfield $a

    In Authorities, when relationship designators are used to specify relationships between agents in field 5XX, with subfield $i (relationship information), Alma searchs the relationship designators included in $i instead of searching the agent name included in subfield $a (personal names; corporate names, etc.). The subfield $i is not part of the name of the author or contributor, it is a separate element that denotes a relationship between agents. It is for this reason that we propose that names be indexed by the name included in subfield $a instead of subfield $i.

    15 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 - 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

11. Support MARC 956 thumbnail images in Alma Staff Interface

    Description:

    Currently, Alma Staff Interface does not display thumbnail images originating from MARC field 956, even when these thumbnails are correctly displayed in Primo VE through thumbnail template configuration.

    At the moment, Alma Staff Interface only displays cover images resolved through internal mechanisms such as:

    ISBN-based cover services (MARC 020)
    Digital representations
    Internal cover enrichment services

    This creates an inconsistency between Primo VE and Alma Staff Interface.

    For example:

    A thumbnail image linked through MARC 956 appears correctly in Primo VE.
    The same record in Alma Staff Interface continues to display only the default placeholder icon.

    It would be very useful if Alma Staff Interface could also support thumbnail display from MARC 956 URLs, similarly to Primo VE.

    Benefits:

    Better visual identification of records by catalogers and library staff
    Improved consistency between Alma and Primo interfaces
    Greater flexibility for institutions that maintain their own thumbnail repositories or use external image sources
    Reduced dependency on ISBN-based enrichment services

    Suggested enhancement:
    Allow Alma Staff Interface to use configurable MARC fields (such as 956) as thumbnail sources, similarly to Primo thumbnail templates.

    Description:

    Currently, Alma Staff Interface does not display thumbnail images originating from MARC field 956, even when these thumbnails are correctly displayed in Primo VE through thumbnail template configuration.

    At the moment, Alma Staff Interface only displays cover images resolved through internal mechanisms such as:

    ISBN-based cover services (MARC 020)
    Digital representations
    Internal cover enrichment services

    This creates an inconsistency between Primo VE and Alma Staff Interface.

    For example:

    A thumbnail image linked through MARC 956 appears correctly in Primo VE.
    The same record in Alma Staff Interface continues to display only the default placeholder icon.

    It would be very… more

    14 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  ·  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. MDE & Sets - Send to MDE should offer options to send bibs or holdings for editing

    When working with sets, it would be very helpful to have the send to MDE offer two options. One for sending bib records to MDE for fixing AND one for sending Holdings records to MDE.
    OR send BOTH (all) to MDE.
    Working with sets of holdings requires you to see all holdings on a single bib to fix errors or move items from one holdings record to another - you cant see this on a holdings list.
    So, i would like to bulk edit these records on either bib level OR holdings level.

    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…)
    0 comments  ·  Metadata 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

13. Add barcode check in Receive

    We propose an enhancement to the Alma system to include a barcode verification check during the receiving process in the Receive module.
    Currently we have observed that Alma does not perform this check when scanning barcodes, unlike the functionality available in the Edit Item section under List of Items.
    Implementing this feature would help ensure greater accuracy and streamline the receiving process.

    14 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 - Receiving  ·  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. Sort Routine for ordered items in PO Line

    I wish to get support from all Acquisition Librarians who visit this idea.

    My library has to order more than 100 copies for different locations for certain titles. During creation of these PO Lines, the sorting of Ordered Items is in chaos after pressing the “Save” button. The sorting is not following the input sequence, or by alphabetical order. My acquisition colleagues, therefore, cannot double check the ordered items in sequence. Contacted Supports Team, it is confirmed that the sort routine functionality for Order Items is not currently supported in the system, and suggest me to post here for your vote.

    I wish to get support from all Acquisition Librarians who visit this idea.

    My library has to order more than 100 copies for different locations for certain titles. During creation of these PO Lines, the sorting of Ordered Items is in chaos after pressing the “Save” button. The sorting is not following the input sequence, or by alphabetical order. My acquisition colleagues, therefore, cannot double check the ordered items in sequence. Contacted Supports Team, it is confirmed that the sort routine functionality for Order Items is not currently supported in the system, and suggest me to post here for your… more

    •  

    19 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

15. Barcode Generation with "Prefix+Sequence+Mod-10 Option 1"

    Our library is a new user to Alma, and we found that our using barcode generated by "Prefix+Sequence+Mod-10 Option 1" with Mode-10 Option 1 as the 14th check digit is not supported in Alma. We have to, therefore, scan in the barcode one item by one item when for creating and receiving items. I wish your vote to us, even your library is not using "Prefix+Sequence+Mod-10 Option 1" for barcode generation configuration, to empower the diversity and features of Alma.

    Below please find the Mod 10-Option 1 calculation:

    https://docs.zebra.com/us/en/printers/software/zpl-pg/c-zpl-mod10-mod-10-mod-43-checkdigits/t-zpl-mod10-mod-10-check-digit.html

    Thank you.

    15 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

16. Portfolio ordering

    It would be very helpful to have the option to define the order of portfolios manually, rather than having them displayed in a fixed or predefined order.

    Thank you!
    Stephan

    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…)
    0 comments  ·  Metadata 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

17. Expose Shared License, Distribution, and Negotiation Details in the license REST API

    The Alma license REST API (POST/PUT/GET /almaws/v1/acq/licenses) does not expose several pieces of license configuration that are available in the Alma UI. This prevents end-to-end license provisioning via API and forces manual UI work after every API call.

    Fields currently absent from the API:

    At the top of the License Details form — the "Shared License" on/off setting, and the "Distribution" multi-select controlling which sections are shared with member institutions (Summary, License Terms, Notes, Attachments).

    In the Negotiation Details tab that appears for shared licenses — per-member rows containing Member Name, Price per year, Price increase (percentage), Currency, Start date, End date, Order Status, Notes, and Available Content, plus the ability to add and remove members.

    Notably, the public Alma license XSD documents a "negotiation_members" element, but it does not appear in actual GET responses even for licenses that clearly have members configured via the UI.

    Impact: Consortial customers using the Network Zone cannot programmatically provision, update, or audit shared licenses or their per-member pricing. Every API-created license requires manual UI steps to configure sharing, distribution, and member-level pricing. External systems cannot read this data at all.

    Request: Expose the Shared License / Distribution settings and the Negotiation Details member list as both readable and writable via the license API. The member list would likely be best modeled as a sub-resource (similar to /acq/licenses/{code}/amendments or /acq/licenses/{code}/attachments), so members can be created, updated, and deleted individually.

    Related idea: "Add API support for licenses with type Negotiation" (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/48119375) — this may be partially or fully addressed by implementing the above.

    The Alma license REST API (POST/PUT/GET /almaws/v1/acq/licenses) does not expose several pieces of license configuration that are available in the Alma UI. This prevents end-to-end license provisioning via API and forces manual UI work after every API call.

    Fields currently absent from the API:

    At the top of the License Details form — the "Shared License" on/off setting, and the "Distribution" multi-select controlling which sections are shared with member institutions (Summary, License Terms, Notes, Attachments).

    In the Negotiation Details tab that appears for shared licenses — per-member rows containing Member Name, Price per year, Price increase (percentage), Currency, Start date,… more

    14 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  ·  APIs and Integrations  ·  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 'Portfolio Parser Parameters' as a Portfolio Loader matching option

    Please add 'Parser parameters' as an additional matching option for activating CZ portfolios using Portfolio Loader.

    Matching by ISBN for large ebook activations results in too many multiple portfolio matches. Since the title IDs in most vendor lists or KBART files match Alma’s parser parameters perfectly, they provide a much better unique identifier than ISBNs for ebooks.

    5 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. Analytics report for POLs cancelled or closed in specified Fiscal Periods

    Provide an Analytics report that identifies Purchase Order Lines (POLs) cancelled or closed within user-selected Fiscal Periods. Libraries need to analyse cancellations and closures by fiscal year or accounting period for budgeting, supplier review, collection management, and audit purposes. Current reporting options do not easily support filtering by the fiscal period in which a POL was cancelled or closed. This enhancement would improve financial reporting accuracy, support year-end analysis, and reduce the need for complex workarounds or external data processing.

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

20. Add General Electronic Services information to Analytics

    In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".

    Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would allow for the simultaneous viewing of a lot of information.

    Please add the General Electronic Services to Analytics, with all fields:
    Active
    Service Code
    Service Name
    Service Description
    Public Name
    Public Note
    DD/ILL Service
    Display Location
    URL Template
    Enable without login
    Disable Service
    All Service Availability Rules

    Thank you for considering!

    In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".

    Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would… more

    66 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  ·  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