1812 results found

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

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

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

   41 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

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

5. Allow cost per use reports for TR reports, not just TR_B1 and TR_J1

   We would like the ability to create cost per use reports based on the Cost Usage Measure TR, not just TRB1 and TRJ1 reports.

   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  ·  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. Be able to see the full email message when using Send email to partner or Send query to patron

   Currently we cannot see the full context of these email messages, we only see the “body” of the email, but that does not include any pre-set text or the greeting and signature.

   Staff are left guessing what information is included in the full message, and the sent messages often look poorly composed and unprofessional. It is inconvenient and time consuming to find the templates to check the complete message before sending. Knowing what the full message looks like at the moment of writing, would help staff decide exactly what to write in the email
   Message.

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

7. Be able to cancel, or reject, a request that is updated as shipped in error

   Sometimes lenders update a request as shipped in error. Once we have confirmed with the partner that we will never receive that item, we should be able to either cancel the request, or reject it so it moves on to another partner. Currently we can only “receive” and “return”, but that creates incorrect analytics reports.

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

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

9. Show character limits in field

   If there is a character limit for a field, show it. Ex being Vendor Details: Contact Information: Web Addresses: Notes. As of now, an entry going over the character limit is truncated with no notification, so unless you know to check, data is lost. Simply adding character limits visible (i.e. 351/400) would solve this completely.

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

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

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

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

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

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

16. Allow configuration of the default destination location for item move requests

    Currently, when creating an item move request (temporary or permanent) in Alma, the Destination Location field is pre-populated with a default location. This default value cannot be changed or cleared by configuration.

    We request an enhancement that would allow institutions to control this behavior - specifically, the option to leave the Destination Location field blank by default. This would require staff to actively select the appropriate destination location from the dropdown list, reducing the risk of accidental or incorrect moves.

    This behavior would align item move requests more closely with patron physical requests, where required fields are not pre-filled and must be intentionally selected by staff.

    Currently, when creating an item move request (temporary or permanent) in Alma, the Destination Location field is pre-populated with a default location. This default value cannot be changed or cleared by configuration.

    We request an enhancement that would allow institutions to control this behavior - specifically, the option to leave the Destination Location field blank by default. This would require staff to actively select the appropriate destination location from the dropdown list, reducing the risk of accidental or incorrect moves.

    This behavior would align item move requests more closely with patron physical requests, where required fields are not pre-filled and… more

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

17. Allow individual process types for detailed borrowing rules.

    It would be helpful to enable the individual process types to configure detailed borrowing rules. We have created several process types for items, such as "Searching," "Cataloging," and "Request on Hold." However, in the fulfillment unit rule parameters, these process types are grouped with the system-generated "Acquisition Technical Services" under the "In Process" category. Consequently, we cannot select them individually as parameters, which prevents the library from setting detailed borrowing rules for specific process types.

    133 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 - Loans  ·  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. Expand the character limit for Inventory number field

    The Inventory number field for physical items in Alma is currently limited to 20 characters. We are using RFID tags to track some of our items, and would like to store them in the Inventory number field. Because these codes are generally about 25 characters long, it'd be helpful if the size of the field could be extended to 30 or (preferably) 50 characters.

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

19. Find User in Other Institution

    Currently, the "Find user in other institution" functionality is only available for designated Resource Sharing libraries.

    Many institutions have multiple libraries, only some of which are designated Resource Sharing libraries, yet all libraries are open to all users. We would like to see the "Find user in other instutition" available for ALL libraries in the institution (not just Resource Sharing libraries), to facilitate checkout of library materials to borrowers visiting from other libraries within the network zone.

    This functionality is found on the Patron Identification page after going to Fulfillment > Manage Patron Services.

    •  

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

20. Rialto marketplace Keywords Searching - not working

    Rialto marketplace Keywords not working. When trying to "Manage Purchase Requests" and do "Search in market" the default Search by"Keywerds" is not working on works when you change to "Title", please have this fixed.

    •  

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