1766 results found

1. Monthly Limit Feature for Patron Purchase Requests

   We propose adding a feature that enables libraries to set a monthly limit on the number of purchase requests each patron can make. If a patron exceeds this limit, the system should automatically decline their request and display a message explaining the reason, such as: "Each patron is limited to submitting N purchase requests per month.

   Thanks!

   154 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…)
   3 comments  ·  Acquisition - Purchase 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

2. ensure that when 'po_line_description_update_upon_bib_change' enabled, subfield A does not get overwritten by subfield L in 022

   Sharing description from our Cataloger, CH:

   We believe the following describes a defect.

   Support indicates it is an enhancement request and suggests we propose on Idea Exchange.

   Background:
   1) We turned on the ‘polinedescriptionupdateuponbibchange’ enhancement in the sandbox.
   2) The enhancement overwrote the $$l instead of pulling in the $$a from 022 – this behavior describes a defect
   None of the following 3 options allow us to properly use the ‘polinedescriptionupdateuponbibchange’ enhancement:
   1. Ideally, we want to enable the ‘polinedescriptionupdateuponbibchange’ function to auto-sync changes in the bib record to the POL bib description. This saves our Cataloging team from an additional step to manually edit the POL record.
   However, we are unable to use this Alma function at all because when we do, it auto-reverts the POL bib desc ISSN from $$a to $$l.

   1. Less ideal, we use the Reload Bib Data button to sync changes in the POL bib desc to match the bib record (a more manual approach—it means our Cataloging team needs to click the ‘Reload Bib Data’ button).
      However, again, we are unable to use this function because this option also changes the ISSN from $$a to $$l. Another Alma feature we are not able to use.

   2. Least ideal – Cataloging team manually updates every field in POL bib desc to match bib record updates. This is the most work for the Cataloging team, as it does not allow them to use the 2 previous enhancements in Alma to make their jobs easier. With this feature enabled, if the Cataloging team manually types anything into the ISSN field in the POL bib description, the system will auto-revert to $$l and override manual changes. Once the Cataloging team makes any change to the ISSN field in the POL bib description, they CANNOT revert it back to $$a. It's as though they lost control of that field entirely. This feels to our organization to be a major glitch - why doesn't the system allow the user to make and save a MANUAL change to a field?

   Sharing description from our Cataloger, CH:

   We believe the following describes a defect.

   Support indicates it is an enhancement request and suggests we propose on Idea Exchange.

   Background:
   1) We turned on the ‘polinedescriptionupdateuponbibchange’ enhancement in the sandbox.
   2) The enhancement overwrote the $$l instead of pulling in the $$a from 022 – this behavior describes a defect
   None of the following 3 options allow us to properly use the ‘polinedescriptionupdateuponbibchange’ enhancement:
   1. Ideally, we want to enable the ‘polinedescriptionupdateuponbibchange’ function to… more

   10 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

3. Support linking Analytics Subject Areas Requests and Fulfillment

   As analytics users, we would like to link request information to loan information in Analytics so that we can obtain a better picture of the entire end-to-end loan process for a patron, from request to loan.

   For example, the Fulfillment subject area could contain fields such as:
   - Loan is based on a prior request (True/False)
   - Originating Request ID

   Similarly, the Requests subject area could contain these fields:
   - Request resulted in a loan (True/False)
   - Resulting Loan ID

   7 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

4. Block when overdue: add a "days per overdue days" unit of measurement option

   Hello everyone,
   when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
   There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first one, "days...", generates larger block periods, but they are over in a shorter time; on the other hand, when using the second one, "open days...", the block periods are smaller but they take more time to be fulfilled.
   https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/Configuring_User_Blocks#Configuring_User_Blocks_Due_to_Overdue_Loans
   So, I guess that the "perfect" option for us would be something in between, an "Days per open overdue days" which does not currently exist in Alma.
   Would it be possible to add this "Days per open overdue days" option and, as its opposite, an "Open days per overdue days"?
   Thanks a lot in advance and best regards.

   Hello everyone,
   when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
   There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first… more

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

5. Add/remove public notes for electronic collection notes in bulk

   If there are known access issues with one specific provider, it would be useful to add / remove a note to all electronic collections, which an institution may have for this provider / interface at once. At present, we have to edit all collections for providers individually if we want to add the same public note for all.

   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…)
   1 comment  ·  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

6. Primo Analytics Mixpanel Data Integrated Into Alma Analytics as External Data Resources

   As stated in the Alma Roadmap 2025-2026, "Analytics will support integrations with external data sources, allowing users to analyze data from multiple systems within the Analytics platform." (https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2025-2026)/Analytics_and_Insights#Integration_with_External_Data_Resources )
   This new feature is expected to simplify workflows and save time by eliminating the need to access multiple systems, thereby improving staff efficiency and effectiveness.

   It would be highly valuable if Primo Analytics Mixpanel data were considered a priority candidate for inclusion within this consolidation initiative.

   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…)
   1 comment  ·  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

7. New title search - include subfield t in Names section

   we would like to see subfield t in the names section of the new titles search. This subfield shows when it is present in field 600 but not in 700. This would be very useful when searching for Author/title

   • 

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

8. Separate Default Format Settings for Book vs. Article Requests - Resource Sharing Request configuration

   Separate Default Format Settings for Book vs. Article Requests - Resource Sharing Request configuration

   Summary:

   Currently, Alma does not allow libraries to configure different default Format values (Physical vs. Digital) for Book (Loan) requests versus Article (Copy/Scan) requests in the Resource Sharing Request form. The single “Delivery fields > Format” default applies globally to both request types even though these request types have very different workflows and downstream impacts.

   Problem:

   When the default format is set to Physical (helpful for book requests), article requests originating in Primo can be incorrectly submitted as Loan requests. This causes article requests to enter ILLiad with the wrong request type and results in lost or incomplete citation data unless patrons manually change the format to Digital.

   Leaving the default blank fixes article behavior but removes the ability to default book requests to Physical.

   Requested Enhancement:

   Allow libraries to configure separate default Format values for:

   Book (Loan) requests and Article (Copy/Scan) requests.

   For example, by moving the Format default into the existing Book and Article request field sections.

   Benefit:

   This would ensure accurate request routing, preserve citation metadata, reduce patron error, and support efficient ILL workflows—especially for libraries integrating Alma/Primo with ILLiad.

   Separate Default Format Settings for Book vs. Article Requests - Resource Sharing Request configuration

   Summary:

   Currently, Alma does not allow libraries to configure different default Format values (Physical vs. Digital) for Book (Loan) requests versus Article (Copy/Scan) requests in the Resource Sharing Request form. The single “Delivery fields > Format” default applies globally to both request types even though these request types have very different workflows and downstream impacts.

   Problem:

   When the default format is set to Physical (helpful for book requests), article requests originating in Primo can be incorrectly submitted as Loan requests. This causes article requests to enter… more

   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…)
   1 comment  ·  Resource Sharing  ·  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. Alma as a linked entity User Interface

   The Alma backend comprises a large bunch of linked entities of different types like title, holding, request, item, report, ... However, on the user interface side theses links and references often are only displayed implicitly. We propose to make these references explicit. Example: The list of requests shown in "Monitor Requests and Item Processes" display a MMS-ID as well as (in certain cases) an Item ID. In order to view the respective title or item entity one has to copy the ID and paste it into the title, respectivly item search. We propose to add a "one click link" for any entity ID displayed by Alma. Further examples:

   • Active and Expired Hold shelf: Item entities as well as title entities should be linked.
   • Lending requests: Item entity shoul be linked.
   • Process reports: Any entity IDs should link their respective entities.
   • Analytics: Any entity ID within an arbitrary analysis should get a direct link to their respective entity within the Alma User Interface.

   In addition in order to becom a linked entity User Interface, Alma must provide a means to share entities with other. Deep linking funktionality is a overdue feature, and, of course a prerequisite for linking Alma entities from within Analytics.

   Last but not least: The usage of book cover thumbnails is inconsistent within Alma. We propose to provide book cover Thumbnails whereever a reference to a title entity is given (explicitly or implicitly).

   The Alma backend comprises a large bunch of linked entities of different types like title, holding, request, item, report, ... However, on the user interface side theses links and references often are only displayed implicitly. We propose to make these references explicit. Example: The list of requests shown in "Monitor Requests and Item Processes" display a MMS-ID as well as (in certain cases) an Item ID. In order to view the respective title or item entity one has to copy the ID and paste it into the title, respectivly item search. We propose to add a "one click link" for… more

   13 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  ·  Linked Data  ·  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. Feature Requests for the NZ Fulfillment Network

    1. Access to Borrowing History Across NZ Institutions
       • Feature Request:
       Enable librarians to view the borrowing history of their university patrons at other NZ institutions.
       • Current Situation:
       a. On Network Activity tab, it only displays current FN loans and current FN requests.
       b. Librarians cannot directly access the borrowing history or detailed transfer records when their patron borrows books from another NZ institution.
       c. Assistance from librarians at the other institution is required, which delays service and limits the ability to provide comprehensive patron support.

    2. Show more information on Network Activity tab
       • Feature Request:
       On Network Activity tab, allow librarians to see (1) the pickup location selected by patrons (2) request queue of that item (3) loan time of patron loan in the format MM/DD/YYYY HH:MM
       • Current Situation:
       a. Patrons occasionally overlook the correct pickup location and arbitrarily select a library, causing confusion at service desks.
       b. Service desks cannot retrieve the patron’s selected pickup location in the system, as this information is only displayed in the patron’s email.
       c. Being able to see the request queue of that item and loan time can make the librarian's workflow smoother.
       d. Additional details are provided in the attached document.

    Many thanks.

    1. Access to Borrowing History Across NZ Institutions
       • Feature Request:
       Enable librarians to view the borrowing history of their university patrons at other NZ institutions.
       • Current Situation:
       a. On Network Activity tab, it only displays current FN loans and current FN requests.
       b. Librarians cannot directly access the borrowing history or detailed transfer records when their patron borrows books from another NZ institution.
       c. Assistance from librarians at the other institution is required, which delays service and limits the ability to provide comprehensive patron support.

    2. Show more information on Network Activity tab
       • Feature Request:
       On Network Activity tab,… more

    •  

    •  

    128 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…)
    3 comments  ·  Resource Sharing  ·  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. Improve the Update Inventory Import Profile so that it can add standalone portfolios to electronic collection

    When using the GOBI API to create e-book orders, we've chosen to not match to CZ collections, and prefer to use vendor provided marc records loaded via an update inventory import profile. The GOBI API creates standalone portfolios when PO lines are created. The Update inventory import profile lacks the ability to update standalone portfolios with electronic collection information.

    If the Inventory tab > electronic resource mapping > portfolio type is set to part of an electronic collection, but the inventory in Alma is standalone, the import job will update the bib record but not the portfolio and yield the error " portfolios skipped (profile not allowing)". To update the portfolios, the electronic resource mapping > portfolio type has to be "standalone". We then have to move the portfolios to their correct local electronic collections via jobs after the import job has run.

    The update inventory import profile would be greatly improved if it could update/move standalone portfolios to designated electronic collections. The match point in an update inventory import profile is the PO line, and the bib record is updated when the import profile runs, it should also be able to update/assign an electronic collection to inventory.

    When using the GOBI API to create e-book orders, we've chosen to not match to CZ collections, and prefer to use vendor provided marc records loaded via an update inventory import profile. The GOBI API creates standalone portfolios when PO lines are created. The Update inventory import profile lacks the ability to update standalone portfolios with electronic collection information.

    If the Inventory tab > electronic resource mapping > portfolio type is set to part of an electronic collection, but the inventory in Alma is standalone, the import job will update the bib record but not the portfolio and yield the… more

    24 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

12. Request for Enhancement of the "Patron Physical Item Request" Function

    We would like to request an enhancement regarding the "Patron Physical Item Request" function.

    Currently, Alma recommends using the "Patron Physical Item Request" function at the title level, and customer institutions are also using the function in the same way.
    When a purchase request is made, notifications for item arrival and hold requests for interested users are also processed at the title level. As a result, when multiple items (e.g., volumes/issues) are ordered under a single title, even if several items are received by the library through that order, interested users receive a notification indicating that only one item has arrived (arrival notification or hold shelf notification).

    In cases where multiple items are ordered under a single title, if there are interested users for that order (users who have checked "Notify user upon receiving/activation" and/or "Hold Item"), we request the following improvements:

    1. When the items are received by the library, a notification ("Notify user upon receiving/activation") should be sent to the interested users, informing them of the arrival of all received items associated with that order.
    2. When the items become available for use, a notification ("Hold Item") should be sent to the interested users, informing them of the availability of all items associated with that order.

    We kindly ask that the function be modified accordingly.

    We would like to request an enhancement regarding the "Patron Physical Item Request" function.

    Currently, Alma recommends using the "Patron Physical Item Request" function at the title level, and customer institutions are also using the function in the same way.
    When a purchase request is made, notifications for item arrival and hold requests for interested users are also processed at the title level. As a result, when multiple items (e.g., volumes/issues) are ordered under a single title, even if several items are received by the library through that order, interested users receive a notification indicating that only one item has… 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  ·  Acquisition - Purchase 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

13. Library staff Email Notifications capability for Subscription Renewals

    Although Alma allows library staff to specify the Renewal Reminder Period in number of days, there is currently no mechanism in place to allow the configuration of subscription renewal reminders to be sent via email to staff.

    This would be a particularly useful tool for subscription management. Could this capability be added to the Renewal Information section please?

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

14. Feature Request for Individual Interlibrary Loan Requests

    We would like to request a functional enhancement regarding individual borrowing requests in the following menu:

    [Alma > Fulfillment > Resource Sharing > Borrowing Requests]
    When a user at an Alma customer institution (e.g., a university library) submits a KERIS interlibrary loan (ILL) request via the library website, the request is received in the Alma menu above. In such cases, the staff in charge of resource sharing must separately submit the request through WILL (the KERIS interlibrary loan system).

    At this stage, the staff would like to send a notification email to the user confirming that the interlibrary loan request has been successfully submitted. Currently, there is a “Send query to patron” function available for individual interlibrary loan requests in Alma; however, it requires staff to manually enter the same message repeatedly each time, which is inefficient.

    We would like to request an additional feature that allows staff to send a predefined or templated message to users, separate from the “Send query to patron” function.

    The message content we would like to use is as follows:

    “Your interlibrary loan request has been successfully submitted. Please note that even if you are among the first 10 applicants eligible for shipping cost support, you will still be required to pay the round-trip shipping fee (KRW 5,840) if the material is not collected. We kindly ask for your understanding.”

    Thank you for your consideration.

    We would like to request a functional enhancement regarding individual borrowing requests in the following menu:

    [Alma > Fulfillment > Resource Sharing > Borrowing Requests]
    When a user at an Alma customer institution (e.g., a university library) submits a KERIS interlibrary loan (ILL) request via the library website, the request is received in the Alma menu above. In such cases, the staff in charge of resource sharing must separately submit the request through WILL (the KERIS interlibrary loan system).

    At this stage, the staff would like to send a notification email to the user confirming that the interlibrary loan request… 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  ·  Resource Sharing  ·  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. Expanding Unicode Tool range in Metadata Editor

    The new Insert Unicode Characters tool in the Metadata Editor should be expanded to include the 0300-036F range of characters. This range includes several diacritics that are commonly used by catalogers, including the ligature (0361), candrabindu (0310), and combining diaeresis below (0324).

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

16. Allow Resource Sharing Request Owning Library to be Set by Pick Up Location

    The Owning Library designation in a resource sharing borrowing request determines where the lending library will send the item. In most instances it is preferable for the Owning Library and the Pick up Location to be the same - that way, in the case of an institution with multiple remote libraries, the item will be sent to where the patron want to pick it up.

    Out of the box, it is currently it is possible to set a default Owning Library, or else allow the patron to choose the "Owner" on the resource sharing request form. It is also possible to designate a Resource Sharing Library in the user record.

    The first option only works if your institution only has one resource sharing library and delivering to other libraries on campus is not a problem. The second option would require patron training and is unlikely to be consistently correct. The final option, adding a resource sharing library to the patron record can get pretty complicated when working with patron loads. It is also fairly common for a patron to be in a law program, and perhaps get assigned the law library as a RS library, but live near main campus and prefer to pick up their items there.

    I think it would be great if there could be a code table that would allow admins to crosswalk which resource sharing library would be the owner of a request based on the pick up location chosen by the patron. I hope this can be considered for Alma Resource Sharing as well as Rapido.

    The Owning Library designation in a resource sharing borrowing request determines where the lending library will send the item. In most instances it is preferable for the Owning Library and the Pick up Location to be the same - that way, in the case of an institution with multiple remote libraries, the item will be sent to where the patron want to pick it up.

    Out of the box, it is currently it is possible to set a default Owning Library, or else allow the patron to choose the "Owner" on the resource sharing request form. It is also possible… 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…)
    1 comment  ·  Resource Sharing  ·  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. Improve the Alma Link Resolver display logic to include conditions and thresholds (as they are available in SFX)

    I would like to see the Alma link resolver have the same configuration options as the SFX link resolver.
    The SFX link resolver offers the following conditions:
    - sametarget
    - threshold
    - notimediffwarning
    - samethreshold
    See: https://knowledge.exlibrisgroup.com/SFX/Product_Documentation/01_Version_4.0/SFX_General_User's_Guide/07_Configuration/05_Menu_Configuration/06_Display_Logic

    In addition, I'd like the Alma link resolver to offer thresholds to further configure the threshold condition in a display logic rule.
    See: https://knowledge.exlibrisgroup.com/SFX/Product_Documentation/01_Version_4.0/SFX_General_User's_Guide/02_KBManager/07_Thresholds

    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…)
    1 comment  ·  Link Resolver  ·  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. MDE Virtual Keyboard – Add Welsh as a separate language option.

    The new Virtual Keyboard for Inserting Special Characters and Diacritics in the Metadata Editor has many different language options. However Welsh is not amongst them.

    Can Welsh be added as a separate language.

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

19. Support file exchange via Odyssey

    While we are able to send and receive files with other Alma, Rapido, and RapidILL libraries via RapidX, the resource sharing world is much larger than these three systems. While ExLibris talks about supporting interoperability, we are not yet able to receive files using the file sharing method dominant among our peers, even though its platform is open source. Odyssey is a major player in the library secure file exchange world, and while we stress to our partners that they need to send non-returnables to us via other methods, often folks forget, deliver via Odyssey, and assume the request is filled. As the borrowing library, we don’t notice these files haven’t come through until an unreasonable amount of time has passed and we check in with the other library. Meanwhile, our patrons could have had these files the whole time - and in some cases, by the time we catch it, it’s past the patron’s deadline. Please build in the ability to receive files via Odyssey when using ISO to communicate with other libraries through Alma Resource Sharing & Rapido

    While we are able to send and receive files with other Alma, Rapido, and RapidILL libraries via RapidX, the resource sharing world is much larger than these three systems. While ExLibris talks about supporting interoperability, we are not yet able to receive files using the file sharing method dominant among our peers, even though its platform is open source. Odyssey is a major player in the library secure file exchange world, and while we stress to our partners that they need to send non-returnables to us via other methods, often folks forget, deliver via Odyssey, and assume the request is… 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…)
    1 comment  ·  Resource Sharing  ·  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. Improve user blocks functionality to prevent resource sharing requests for users who have resource sharing loans overdue

    Within Alma, it is possible to configure blocks that ensure users who have items on loan and overdue are unable to place any more requests until the items have been returned. However, it isn’t possible to apply blocks in a more granular way, such as to prevent a user who has resource sharing items on loan and overdue from placing any more resource sharing requests. It is not our library policy to prevent users with items on loan and overdue from requesting anything else until they have returned their overdue items, so we cannot apply blocks to encourage people to return their resource sharing items by the due date either. This is unfortunate because additional fees can be payable to some resource sharing partners for late return of their items. We would like to be able to specify in Alma configuration that a user who has resource sharing items on loan and overdue will not be able to place any more resource sharing requests until the overdue items have been returned.

    Within Alma, it is possible to configure blocks that ensure users who have items on loan and overdue are unable to place any more requests until the items have been returned. However, it isn’t possible to apply blocks in a more granular way, such as to prevent a user who has resource sharing items on loan and overdue from placing any more resource sharing requests. It is not our library policy to prevent users with items on loan and overdue from requesting anything else until they have returned their overdue items, so we cannot apply blocks to encourage people to… more

    39 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 Sharing  ·  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