1038 results found

1. Improve how Alma selects libraries for internal requests

   We are 1 institution on Alma/Primo, our organisation is NHS Scotland. We have libraries from different NHS regions (or health boards) each linked to a particular campus.

   When a patron requests an item on Primo and selects the pick-up location they belong to, Alma checks to see if that particular library can fulfil that request.

   Thereafter it will just select randomly from the list of other libraries to fulfil the request.

   The issue we have is that a library from the same campus may be able to fulfil that request but Alma may select a library up to 150 miles away to fulfuil the request.

   So although we would not want to restrict a patron from making a request from any library, we would like it if Alma could select a library from the patron's campus first before checking other libraries from our institution.

   We noted an idea 'Requestable by Campus Affiliated Patrons Only' but it is not quite the same our suggestions but I wonder if the changes made for this idea could be expanded to accomodate ours.

   Derek

   We are 1 institution on Alma/Primo, our organisation is NHS Scotland. We have libraries from different NHS regions (or health boards) each linked to a particular campus.

   When a patron requests an item on Primo and selects the pick-up location they belong to, Alma checks to see if that particular library can fulfil that request.

   Thereafter it will just select randomly from the list of other libraries to fulfil the request.

   The issue we have is that a library from the same campus may be able to fulfil that request but Alma may select a library up… more

   135 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…)
   12 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   Completed  ·  Dana Moshkovits responded

   When a hold request is created and the holdings to fulfill the request is not available in the selected pickup location, Alma now matches the holdings to the request using additional parameters
   For more information please see:
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes#Select_Request_Locations

2. Add in function to exclude non -SBN content from ISBN matching in the Alma purchase request function

   Within Alma, the purchase request function does a matching process with local record using the ISBN field (MARC 020 $$a). Unfortunately, whether it is set up using fuzzy or exact, any 020 $$a with a-z text in the field causes an error and prevents the purchase request from being created. This occurs often with older or imported records, where the additional information has not been added to the $$q. The workaround from Ex Libris is to link the bib and then unlink to edit the bib information, removing the non-ISBN information before saving. However, this would mean that the purchase request is not attached to the local record. We queried with Ex Libris (case number 07042507) regarding the setup of the purchase request form within Alma to provide a work around for the fact that any local record with a-z in the field results in an error, even with fuzzy matching, and were told to add an enhancement request.

   We cannot use this feature in Alma currently due to the mis-matching causing additional work for our Acquisitions staff to re-link, our Metadata Team having to clean up the record before the order being placed, or us spending a lot of time and effort in trying to create a normalization rule that could clean up the records in bulk and continuously. We would like the form to call only on the element that is the ISBN, e.g by using reg ex to only bring in the ISBN element even when the $$a has non ISBN elements within it.

   Within Alma, the purchase request function does a matching process with local record using the ISBN field (MARC 020 $$a). Unfortunately, whether it is set up using fuzzy or exact, any 020 $$a with a-z text in the field causes an error and prevents the purchase request from being created. This occurs often with older or imported records, where the additional information has not been added to the $$q. The workaround from Ex Libris is to link the bib and then unlink to edit the bib information, removing the non-ISBN information before saving. However, this would mean that the purchase … more

   11 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

3. Ability to view ISO messages in Lending requests

   We would like the ability to view the original XML/ISO messages sent between lender and requester in our Lending requests. There is information we need that doesn’t display in requests when they come into our system.

   Examples include:

   *Copyright declaration: we need this for copyright compliance reporting purposes

   *Maximum cost: if this doesn’t display, we have to confirm that the requesting library accepts our charges if the cost is going to be over the standard charge

   *Expiry date: the request status changes to Expired if this date is passed, and the request moves on in the rota

   *Need by date: the field is in the request, but the information doesn’t display. We need to be able to see this so we can notify the requesting library if we can’t supply the item in time

   *Date and time that request is received: we need to know the date and time a request comes into our system so we can ensure our turnaround time meets the service level – particularly important for Express requests

   Being able to view the ISO messages in requests would be invaluable.

   We would like the ability to view the original XML/ISO messages sent between lender and requester in our Lending requests. There is information we need that doesn’t display in requests when they come into our system.

   Examples include:

   *Copyright declaration: we need this for copyright compliance reporting purposes

   *Maximum cost: if this doesn’t display, we have to confirm that the requesting library accepts our charges if the cost is going to be over the standard charge

   *Expiry date: the request status changes to Expired if this date is passed, and the request moves on in the… more

   77 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…)
   Already Supported  ·  3 comments  ·  Resource Sharing  ·  Delete…  ·  Admin →

4. Placing digitization requests via Primo on holdings without items

   Currently, titles with no inventory for their holdings do not appear to provide a title-level Digitization Request option in Primo.

   This is a potentially huge defect in the Request functionality as many requests might well specifically be for material in that situation, e.g. older physical journal holdings where there is no item information into Alma but where there is potentially a functional need for the Digitization service. We think that if there is an Physical holding published to Primo, there should always be at least the possibility for the library to offer and configure Patron Digitization requests. This defect has a negative impact on the patrons and the services that libraries offer.

   To allow patron digitization requests via Primo on holdings without items, libraries have to create dummy items. This is not a valuable and long-term solution... We would like a General Digitization Request functionality (like there is currently already one with the General Hold Request).

   Currently, titles with no inventory for their holdings do not appear to provide a title-level Digitization Request option in Primo.

   This is a potentially huge defect in the Request functionality as many requests might well specifically be for material in that situation, e.g. older physical journal holdings where there is no item information into Alma but where there is potentially a functional need for the Digitization service. We think that if there is an Physical holding published to Primo, there should always be at least the possibility for the library to offer and configure Patron Digitization requests. This… more

   270 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…)
   7 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   Completed  ·  Dana Moshkovits responded

   Completed as part of Alma December release:
   Patrons can now place a general digitization request in Primo or Alma for a holdings with no items in the same way that they can place a general hold request. The new option is also available when using the Manage Fulfillment Options for the purpose of fulfilling a resource sharing document delivery request.
   For more information please see Alma release notesL
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/001Alma_2018_Release_Notes?mon=201812BASE

5. More API options for Borrowing Requests

   The current API:s for Borrowing Requests are limited to get a list of request for a specific user, get a specific request of a specific user or create a new request.

   To be able to integrate better with other systems, in our specific case the Swedish national ILL broker system "Libris Fjärrlån", we would need to be able to update and delete requests as well.

   We would also want to retrieve lists of requests without knowing the user, for example by status, by external system or other criteria.

   28 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

6. Improve job "Requests - Handle Expiration steps"

   The job "Requests - Handle Expiration Jobs" updates requests and at present, the output of the job informs only on the number of outputs. The job can block on a request-ID which then must be manually handled.
   In order to save time and better inform the lending libraries, it would be helpful to have at least an information on any Error-causing request, with it's request-ID. Ideally it would be great to also have an output of successfully handled requests in form of a list, which can be exported to Excel.

   Improve the job "Requests - Handle Expiration Jobs" with output
   - Errors - List the blocking request with its request-ID
   - List all successfully treated requests and allow to export to Excel

   The job "Requests - Handle Expiration Jobs" updates requests and at present, the output of the job informs only on the number of outputs. The job can block on a request-ID which then must be manually handled.
   In order to save time and better inform the lending libraries, it would be helpful to have at least an information on any Error-causing request, with it's request-ID. Ideally it would be great to also have an output of successfully handled requests in form of a list, which can be exported to Excel.

   Improve the job… more

   20 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

7. Searchable archive of old/completed requests outside active request screen

   Too much clutter in active screen. Would be great if this screen only showed new /pending created requests. The facets to the left would then be more meaningful and useful as filters to find specific requests - those sent to partner, those that overdue etc instead of requests with these statuses being presented within the active request mix

   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  ·  Resource Sharing  ·  Delete…  ·  Admin →
   Closed  ·  AdminErez Shabo (Product Manager, Ex Libris) responded

   Hello All,

   This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

   This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

   We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

   Alma Product Team

8. Rapid ILL: ALMA Created lending request. To have .PDF Preview viewer also in 'Download Electronic Resource'

   In ALMA there are two different ways to upload a .PDF file to a Rapid ILL created lending request. The 'Ship item digitally' (Document Delivery) way allows upload and also content preview of the actual .PDF file. The other way is via 'Download Electronic Resource' which is better because citation information also appears. But the 'Download Electronic Resource' way does not have a content preview of the .PDF file. The idea proposed is to add the same .PDF file preview window, within the 'Download Electronic Resource' option. This will improve accuracy and efficiency in our workflow.

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

9. Allow institution to determine which type of Bibliographic record will be created when creating a Purchase Request

   This idea was submitted by Ex Libris product management team in order to better understand the need as well as get feedback from the community.

   Current situation:

   • A purchase request can be created from Primo/Leganto/Alma
   • A purchase request must rely on a Bibliographic record, there are 2 options for the purchase request to match on a Bibliographic record:
   • Match to an existing Bib record (if exists)
   • Create a new Bib record (this is the use case described below)

   When creating a purchase request, the user has the option to decide whether it is a "One Time" purchase (Book) or "Continuous" (Journal) AND which material type should be purchased (Physical or Electronic) - see attached screenshot 1.

   The way that the Bibliographic record is created (currently) is that upon creation of the purchase request, Alma looks to see the default template which is set by the institution (in the MD Editor) and a Bib record is created with material type according to this template.

   The need:

   Purchase request can create 4 types of PO lines (as you can see in screenshot1):
   - Physical book
   - Electronic Book
   - Physical Journal
   - Electronic journal

   The Bib record which will be created as a result from the creation of the purchase request will only have the type which is set in the default template in the MD Editor

   So in certain scenarios, a Purchase Request which was created for Electronic Book
   will create a bib record was with type "Physical-Book", why? Because this is the default template set in the MD Editor.

   Desired outcome:

   The material type of the Bibliographic record created as a result from the purchase request should match the material type set on the purchase request.

   This idea was submitted by Ex Libris product management team in order to better understand the need as well as get feedback from the community.

   Current situation:

   • A purchase request can be created from Primo/Leganto/Alma
   • A purchase request must rely on a Bibliographic record, there are 2 options for the purchase request to match on a Bibliographic record:
   • Match to an existing Bib record (if exists)
   • Create a new Bib record (this is the use case described below)

   When creating a purchase request, the user has the option to decide whether it is a "One Time" purchase (Book) or… more

   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…)
   Accepted  ·  0 comments  ·  Acquisition - Purchase Requests  ·  Delete…  ·  Admin →

10. Add request time stamp and note to Retrieve user requests API and xsd

    Hello,

    We'd like the request time stamp and note added to the Retrieve user requests API and xsd, so we can retrieve them:
    https://developers.exlibrisgroup.com/alma/apis/xsd/rest_user_request.xsd?tags=GET
    https://developers.exlibrisgroup.com/resources/xsd/rest_user_request.xsd

    Thanks,

    Ryan Edwards
    Digital Access and Systems Librarian
    Information Systems
    Getty Research Institute
    1200 Getty Center Drive, Suite 1100
    Los Angeles, CA 90049-1688
    reedwards@getty.edu
    310.440.7398

    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  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    Completed  ·  AdminAsaf Kline (VP Library Solutions, Ex Libris) responded

    In the August 2019 Release, the following change was done:

    Request time is now available for the Get-Request and GET-requested-resources (task lists) APIs, including the exact time (HH:MM:SS) the request was placed.

11. Change the “No requesting from available holding” functionality (check item availability)

    Circulation desk librarians want to make a distinction between items and holdings that are (not) available for requesting purposes.
    Patrons shouldn't be able to request items that are available, but they should be able to request items that are NOT available. In our case our items are created under the same holding, and Alma checks the holding for availability, not the item.
    Use case: 1 holding with 3 items (with the same item description): 2 items are loanable, 1 item should stay in the shelves for consulting.
    When the 2 loanable items are on loan and the 3rd one being a non-loanable copy, the first 2 items cannot be requested, there’s no request button.

    We want to be able to show a request button when an item is on loan, even though there is still a no loan item available under the same holding.

    Circulation desk librarians want to make a distinction between items and holdings that are (not) available for requesting purposes.
    Patrons shouldn't be able to request items that are available, but they should be able to request items that are NOT available. In our case our items are created under the same holding, and Alma checks the holding for availability, not the item.
    Use case: 1 holding with 3 items (with the same item description): 2 items are loanable, 1 item should stay in the shelves for consulting.
    When the 2 loanable items are on loan and the 3rd one… more

    114 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 - General  ·  Delete…  ·  Admin →
    Completed  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

    Hi,

    In the July 2017 release the following was done:

    The calculation of the fulfillment unit On Shelf Request Policy was changed for serial titles. For each item, if there are available items that have the same description and are requestable, then the request link will be suppressed. If the available items are not requestable then the request link will not be suppressed.

    Thank you for this very helpful suggestion !

    Moshe

12. Add "Job category" in the expandable requester's info label in the RS request.

    We would like to have a requester's "Job category" (Department) listed in the expandable requester's info label in the RS request (see the picture attached).
    When a request is unfilled the Document Delivery staff send a notification message to the relevant department mailbox straight from the request via “Send query to patron”.
    Currently, we must open the requester's account to find out their department then go back to the request to send a message. This is very inconvenient.
    It would be useful to make the label modifiable to let a library to create the label by selecting only parameters necessary for their needs.

    We would like to have a requester's "Job category" (Department) listed in the expandable requester's info label in the RS request (see the picture attached).
    When a request is unfilled the Document Delivery staff send a notification message to the relevant department mailbox straight from the request via “Send query to patron”.
    Currently, we must open the requester's account to find out their department then go back to the request to send a message. This is very inconvenient.
    It would be useful to make the label modifiable to let a library to create the label by selecting… more

    •  

    2 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Sharing  ·  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. Allow Request Notes to be edited even with complex Fulfilment Rules

    We introduced Fulfillment Rules to check if there are any "Process Types" assigned to an item and make them unrequestable. For example if an item is MISSING, REQUESTED, LOST, LOANED, etc.

    This allows an item without a process type to be requested fine. Unfortunately, the moment you try to edit the Request Note and update the request, it ends up rechecking the Fulfillment rules and oddly cancels the request.

    We were hoping we can use the edit Request Note process to mark items when our library officers have done 1st/2nd/3rd shelf searching of items before they become officially marked as missing from the shelf.

    Instead, we're marking the physical slips with notes instead of doing all these in Alma, which somewhat defeats the purpose of centralized inventory management.

    We introduced Fulfillment Rules to check if there are any "Process Types" assigned to an item and make them unrequestable. For example if an item is MISSING, REQUESTED, LOST, LOANED, etc.

    This allows an item without a process type to be requested fine. Unfortunately, the moment you try to edit the Request Note and update the request, it ends up rechecking the Fulfillment rules and oddly cancels the request.

    We were hoping we can use the edit Request Note process to mark items when our library officers have done 1st/2nd/3rd shelf searching of items… more

    •  

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Display purchase request approval/rejection reason in purchase request alerts in citations

    We think it would be helpful for the purchase request approval/rejection alerts for citations in Alma to include the approval/rejection reason. This would appear in the Type field of the alert in addition to the "Citation Purchase Request Approved/Rejected" text (like how the rule used to approve/reject copyright for a citation appears after "Approved" or "Rejected" in the Copyright Status field).

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Purchase Requests: Create 'Archived' Tab?

    Purpose: Purchase Request Management. To retain complete request history, whether approved/ordered or rejected, in a group separate from new, not-yet-assigned requests.

    Controls needed: 'Archive' operation added to the Row Action Menu. Full ability to move archived requests out of the archived condition and back into the 'unassigned' state and condition, or to delete.

    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…)
    1 comment  ·  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. Alma TPRS - Remote System ID number 001 is populated in Alma Request UI

    Currently,
    If TPRS sends their system identification number 001 e.g. "000074745018 " in their system, this 001 field vale does not get populated in the receiving side Alma's Lending request UI despite this value may be found in xml <supplierUniqueRecordId>

    i.e. ALMA UI > Lending Request > field Remote Record ID = empty

    We would like this to be populated in the Lending request Form, so that staff can view Remote Record ID as consistantly reflecting TPRS 001 value, in both Borrowing and Lending requests. Book or Article requests.

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

17. Ability to Type Over Date For Physical Item/Booking Request

    When creating a Physical Item Request or a Booking for a future day and time for a patron, I think it would be nice if you could just type in the date and time as opposed to having to wipe the existing date and time or click around on the calendar.

    •  

    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  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Product Manager, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

18. Resource Request Monitoring screen should not only show the date but also the time when a request was made

    In Alma Menu -> Resource Requests -> Monitor Requests & Work Orders we need to be able to see the time that a request was created, not just the date.

    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  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Product Manager, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

19. Configure how an active request is defined in Alma Resource Sharing

    Currently a user's request at a borrowing library is considered 'active' until the lending library receives and checks in a returned item. We would like the option of making our users' requests 'inactive' when they have returned the item to our library, even if we haven't returned the item to the lending library.

    We have set a limit on 'active requests', and the current definition is penalising our borrowers. They cannot place another request, even though they have returned the item to our library (because the lending library has not checked the item in at their end).

    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 →
    Completed  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

    Completed as part of January release:

    The Active resource sharing request limit policy now ignores active requests which were already returned from the patron to the library, but were not yet returned to the lender.
    Please see Alma January release notes for more details:
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/009_2019/Alma_2019_Release_Notes?mon=201901BASE

20. Have the Proxy For setting available for placing Requests.

    Currently our incarcerated students have their requests put into a spreadsheet that is sent to the Off Campu team. They then have to process the request (sometimes having to spend time finding the correct item or call number) and then process the request. It would be much more efficient if the Proxy For function could be expanded to include the placing of requests, which would then place the items on the Pick from Shelf list for collection and processing

    88 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…)
    5 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    Completed  ·  Dana Moshkovits responded

    A new type of proxy user has been introduced as part of Ala December release, that will function as an extension for the sponsor user: Fulfillment proxies will have a proxy account (separate from their personal account, if exists), with which they’ll be able to log into Primo or Primo VE, place hold and resource sharing requests on behalf of their sponsor user, follow up on these requests, be notified when they reach the hold shelf, and check out items on behalf of the sponsor user.

    For more information please see Alma December Release Notes:
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2021/Alma_2021_Release_Notes