1106 results found

1. NOTIFICATION TO CIRCULATION DESK REQUEST CANCELED BY USER AT HIS PRIMO PROFILE

   We want that the Circulation-Desk receive a notification letter when the user cancel their requests at their Primo profile. The cancelled reason is Cancelled at patron request. Our institution have two branches, one in Madrid and other in Alcalá de Henares, when the user choice an item located in Alcalá de Henares, he can pick up in a Reading Room in Madrid, but when he did the request and did not change the room to Madrid. So they receive the notification letter that the request will be available in Alcalá de Henares and inmediatily they cancelled the request and made another one to be picked up in Madrid.

   Since we don’t receive notification that the user has canceled, those books remain on the hold shelf, and it isn’t until they are moved to the overdue shelf “awaiting pickup” that, when we scan them, Alma notifies us that they are being assigned to the next request in the queue. That request is the one made by the same user to check out the book at the Madrid branch.

   This means that the user receives it at Madrid readin room later than the date they requested.

   We want that the Circulation-Desk receive a notification letter when the user cancel their requests at their Primo profile. The cancelled reason is Cancelled at patron request. Our institution have two branches, one in Madrid and other in Alcalá de Henares, when the user choice an item located in Alcalá de Henares, he can pick up in a Reading Room in Madrid, but when he did the request and did not change the room to Madrid. So they receive the notification letter that the request will be available in Alcalá de Henares and inmediatily they cancelled the request… 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  ·  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

2. Add to the "Monitor Request" screen a filter which will allow users to see "Rejected and active" requests

   On behalf of the Product management team we would like to understand the need and use cases of the following Idea (which it's need was raised by a specific library) - any comment is welcome.

   When trying to delete a circulation desk user is notified: 'This circulation desk is attached to one or more requests and cannot be deleted'. User goes to the monitor request screen and does not find any request that prevents the desk deletion...

   The reason is that the request was rejected but it is still active (item was not scanned)

   Due to the fact the 'Monitor requests' screen does not present 'Active rejected' requests (not even in the 'All' filter), customer needs to approach EXL support to analyze the issue, find the request in the database and clear it.

   The need in this idea is to allow customers to see rejected requests which are still active in order to clear them. and potentially add an action that will clear the request without the need to physically scan the item.

   On behalf of the Product management team we would like to understand the need and use cases of the following Idea (which it's need was raised by a specific library) - any comment is welcome.

   When trying to delete a circulation desk user is notified: 'This circulation desk is attached to one or more requests and cannot be deleted'. User goes to the monitor request screen and does not find any request that prevents the desk deletion...

   The reason is that the request was rejected but it is still active (item was not scanned)

   Due to the fact the… more

   17 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
   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

3. Lending requests - requests shipped as physical non-returnable should automatically get status Request Completed

   Now when there is an lending request in Alma and we choose the option "Ship non-returnable" then such request gets a status "Shipped physically". We suggest that such request should automatically get status "Request Completed" because it was shipped and such request is completed according to our workflow.

   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

4. Add "Print Slip Report" action to the "Resource Request Monitoring" screen

   The Print Slip Report function is currently available from the "Pick Up Requested Resources" and "Resource Sharing Lending Requests Task List" screens. But when a hold is placed on an item that is checked out, the returning item is automatically placed on hold and the request bypasses the "Pick Up Requested Resources" screen and shows up on the "Resource Request Monitoring" screen as "On Hold Shelf". But the Print Slip Report is not available here. It does need to be available here, as well.

   "Print Slip Report" is a different action than "Print Slip." The Print Slip Report is a function that was developed for the Orbis Cascade Alliance based on our need to be able print enhanced hold slips from Alliance-hosted server. The Print Slip Report sends an XML-formatted email with metadata for requests to our server, where the XML is parsed and used to generate PDFs for printing via a web browser interface. This function is crucial to the workflow of our 38 institutions for both local and resource sharing requests. Exporting to Excel won't work, since the Print Slip Report is used to email an XML format to our server. As I indicated above, use of the Print Slip Report is a key step in our workflows at all institutions. Not being able to use the Print Slip Report for requests that bypass the "Pick Up Requested Resources" screen disrupts that workflow.

   The Print Slip Report function is currently available from the "Pick Up Requested Resources" and "Resource Sharing Lending Requests Task List" screens. But when a hold is placed on an item that is checked out, the returning item is automatically placed on hold and the request bypasses the "Pick Up Requested Resources" screen and shows up on the "Resource Request Monitoring" screen as "On Hold Shelf". But the Print Slip Report is not available here. It does need to be available here, as well.

   "Print Slip Report" is a different action than "Print Slip." The Print Slip… more

   121 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…)
   29 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   Closed  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

   Hi,

   The request monitor page is not intended to be the routine working space, but rather be an interface that allows searching and fining specific requests to query about their status, and run some specific actions (such as cancel). The routine work on the requests list is intended to be done via the task lists.

   Thanks,
   Moshe

5. New UI - request pickup location

   When placing a physical item request for a user the 'Pickup at' box is confusing. If you just click in the box or hit the drop-down arrow the only suggestion that comes up is 'No campus' . You then need to click on 'No campus' to get up a pickup locations list to choose from. The old UI gives 'No Campus' but also lists the other pickup locations as well. I'm told this is because the new UI groups libraries to improve the clarity of the list, but it seems to have created a backwards step in usability. Can the previous behavior be restored?

   When placing a physical item request for a user the 'Pickup at' box is confusing. If you just click in the box or hit the drop-down arrow the only suggestion that comes up is 'No campus' . You then need to click on 'No campus' to get up a pickup locations list to choose from. The old UI gives 'No Campus' but also lists the other pickup locations as well. I'm told this is because the new UI groups libraries to improve the clarity of the list, but it seems to have created a backwards step in usability. Can the… 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…)
   1 comment  ·  Fulfillment - Requests  ·  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

6. Patron physical item request – automatic cancellation of requests when ‘Date Needed By’ has passed:

   I suggest that if the "not needed by " date is reached then the patron request is cancelled.

   The only function of “date not needed by” for patron physical item requests is to prevent items from being put into transit from other locations if the transit cannot be completed by the required date.

   However this is not clear to patrons and users ask us why we send Hold available notices when they already indicated a date when they would no longer need the item.

   Staff also waste time locating items that Patrons have indicated are no longer needed, only to waste more time when they take the unused item off the Hold shelf when it eventually expires.

   I suggest that if the "not needed by " date is reached then the patron request is cancelled.

   The only function of “date not needed by” for patron physical item requests is to prevent items from being put into transit from other locations if the transit cannot be completed by the required date.

   However this is not clear to patrons and users ask us why we send Hold available notices when they already indicated a date when they would no longer need the item.

   Staff also waste time locating items that Patrons have indicated are no longer needed, only… more

   600 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 - Requests  ·  Delete…  ·  Admin →
   Completed  ·  Dana Moshkovits responded

   The “Date needed by” field (also known as “Not Needed After”), which can be populated by the patron, was taken into account only in the “pick from shelf” workflow step, cancelling the request when the date was in the past without sending a cancel notification (since the patrons indicated that they are no longer interested).

   Following this development, this behavior will be applied in other workflow steps in the request lifecycle:

   Queued requests that are not yet active but are past their date needed by will now be canceled by the “Request – handle last expiration date” (to avoid recalling items to fulfill requests that are no longer relevant).
   When an item is scanned in, if the “date needed by” of the request had passed, the request will be canceled.
   When an item is placed on the hold shelf, if the date needed by is earlier than the regular hold shelf expiry, the hold shelf expiration date will be populated by the date needed by (so that the request will not remain on the hold shelf after the patron is no longer interested).

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

   The “Date needed by” field (also known as “Not Needed After”), which can be populated by the patron, was taken into account only in the “pick from shelf” workflow step, cancelling the request when the date was in the past without sending a cancel notification (since the patrons indicated that they are no longer interested).

   Following this development, this behavior will be applied in other workflow steps in the request lifecycle:

   Queued requests that are not yet active but are past their date needed by will now be canceled by the “Request – handle last expiration date” (to avoid recalling items to fulfill requests that are no longer relevant).
   When an item is scanned in, if the “date needed by” of the request had passed, the request will be canceled.
   When an item is placed on the hold shelf, if the date needed by is earlier than the regular hold… more

7. Check past requests

   When a request is cancelled or completed, there is no possibility to retrieve any information about the past request. If something went wrong, it is impossible to trace the patron or destination of the request.

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

   Thank you for submitting this idea and for highlighting the need to view past patron requests in Alma.

   
   

   With the introduction of the new Manage Patron Services interface, this functionality is now available. The Requests tab includes both active and historical requests, allowing staff to review a patron’s full request history directly from the same screen.

   
   

   Since this enhancement is now part of the updated workflow, I’m closing this idea as completed.

8. Increase customisation options for the resource sharing request form

   User experience testing that we conducted showed that most users prefer to place resource sharing requests via the resource sharing request form in Primo. Users also expressed frustration with some aspects of the form including the format of the fields. They also expected that the Library could add notices relevant to the resource sharing service to this page.

   The current options for configuring this form do not allow us to meet the expectations of our users. We would like to have more options for customising the page the form is on and the form itself. Specifically we would like :
   1)The ability to customise the format and appearance of the page (e.g. the width of form fields, the positioning of the radial buttons)
   2)The ability to add a notice or message to the form (this is crucial to communicate important information about the service to our users)
   3)The ability to add custom fields to the form

   User experience testing that we conducted showed that most users prefer to place resource sharing requests via the resource sharing request form in Primo. Users also expressed frustration with some aspects of the form including the format of the fields. They also expected that the Library could add notices relevant to the resource sharing service to this page.

   The current options for configuring this form do not allow us to meet the expectations of our users. We would like to have more options for customising the page the form is on and the form itself. Specifically we would like… more

   358 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…)
   14 comments  ·  Resource Sharing  ·  Delete…  ·  Admin →
   Accepted  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

   We are looking into improvements that can be made to the Primo VE form, such as:

   • Add a custom notice or message to the form
   • Improve the form fields’ responsiveness to the requested format (book/article and physical/digital)
   • Look into ways to enhance the configurability of the look and feel for the form

9. Send borrowers an email when they place a request

   It would be good if, when someone places a request on Primo, they could be sent an email receipt to confirm what they have requested. (This is an idea for both Alma and Primo, as I assume the email would be sent from Alma).

   Not only would it be useful for users to have confirmation (a lot of webforms will send users a copy of their completed form, so people half-expect one from Primo/Alma), but it would allow libraries to include important messaging.

   eg. at the moment, January 2021, we're in lockdown again, so the email could ask people to bear in mind that requested books might not be retrievable if the person who has the item is off-campus/self-isolating.

   It would be good if, when someone places a request on Primo, they could be sent an email receipt to confirm what they have requested. (This is an idea for both Alma and Primo, as I assume the email would be sent from Alma).

   Not only would it be useful for users to have confirmation (a lot of webforms will send users a copy of their completed form, so people half-expect one from Primo/Alma), but it would allow libraries to include important messaging.

   eg. at the moment, January 2021, we're in lockdown again, so the email could ask people… 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  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Convert digitization request to purchase request

    I would like to convert a request from a scanning request to a purchasing request, particularly when the permissions cost is high. I am not sure if this is a Alma or Rialto workflow, but it would be nice to do a "search in Market" to find out price and auto-reject the way we can do in Rapido. Additionally, we would like 'Pay-per-use" functionality from Alma digitization requests.

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Automatic selection of "Complete the request" when shipping Lending Digital requests

    For Lending Digital requests, could the "Complete the request" be automatically selected when we ship an item (or maybe the recent choice remembered) – so we don't have to select it each time we supply an item?

    8 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  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

12. Adding "Level of Service" to Resource Sharing Borrowing/Lending Request Facet

    Currently, when placing a Resource Sharing Requests (both Borrowing and Lending), clients are able to select a "Level of Service" e.g. Core, Rush, Express. The Borrowing/Supplying library will then base on this level of service to prioritize the workload. At the moment, Level of Service is not available as a facet for filtering in Alma. The impact is that library staff need to go through every requests to find out what level of service the client has requested. When the Borrowing and Lending Request list contains hundreds of requests, this task is impractical and defeat the purpose of having "level of service" feature. Hence, we need the "Level of Service" field to be on the facet.

    Currently, when placing a Resource Sharing Requests (both Borrowing and Lending), clients are able to select a "Level of Service" e.g. Core, Rush, Express. The Borrowing/Supplying library will then base on this level of service to prioritize the workload. At the moment, Level of Service is not available as a facet for filtering in Alma. The impact is that library staff need to go through every requests to find out what level of service the client has requested. When the Borrowing and Lending Request list contains hundreds of requests, this task is impractical and defeat the… more

    46 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…)
    Completed  ·  7 comments  ·  Resource Sharing  ·  Delete…  ·  Admin →

13. A purchase request with the status "Approved" can be rejected (NOT deleted) and that this information is updated in My Library

    Our proposal is that a purchase request with the status "Approved" can be rejected (NOT deleted) and that this information is updated in My Library (we want the user can see that their purchase request was rejected). The problem when you try to do this is that Alma warns that requests with status "Approved" can not be rejected.

    Ideally, when the POL associated with the purchase request is canceled, Alma should automatically reject this request and it would be displayed in Primo-My Library. (for example, the provider says the book is out of stock)

    26 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

14. Fulfillment Network AFN- Add "Manual Locate Job" id to Borrowing Request details; Add Borrowing Request ID to "Manual Locate Job" details

    In an Automated Fulfillment Network (AFN), when an institution's user places a resource sharing borrowing request, Alma runs the "Manual Locate Job" to build the rota for the request. The job report can be viewed in the Admin> Manage Jobs and Sets> Monitor Jobs> Job History.

    Currently, the only way to match the "Manual Locate Job" for a specific user's borrowing request, back to that borrowing request as listed in Fulfillment> Resource Sharing> Borrowing Request is by timestamp.

    Please add the Manual Locate Job's identifier to the user's Fulfillment> Resource Sharing> Borrowing Request details, as well as adding the Borrowing Request identifier to the corresponding Manual Locate Job's details, so that job and the request can be more easily cross-referenced.

    In an Automated Fulfillment Network (AFN), when an institution's user places a resource sharing borrowing request, Alma runs the "Manual Locate Job" to build the rota for the request. The job report can be viewed in the Admin> Manage Jobs and Sets> Monitor Jobs> Job History.

    Currently, the only way to match the "Manual Locate Job" for a specific user's borrowing request, back to that borrowing request as listed in Fulfillment> Resource Sharing> Borrowing Request is by timestamp.

    Please add the Manual Locate Job's identifier to the user's Fulfillment> Resource Sharing> Borrowing Request details, as well as… 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  ·  Collaborative Networks  ·  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

15. Store information about request history

    It is currently not possible to see whether an item has previously been requested, only that it's checked out. I want (often) to be able to tell: how many times throughout the history of this item has it been requested and in what way (page from shelf, recall, something else). It's super weird to me that this isn't present in the fulfillment history at least, and probably in analytics.

    90 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Converting Digitization request to RS request - The notes field from the digitization request should be added to the RS request note field

    When converting a digitization request to resource sharing borrowing request. The digitization notes field should be copied to the resource sharing request note field. This would also help interlibrary loan staff know that the item was converted from a digitization request. But also many notes are added by library staff in the digitization request notes field when triaging the request. Therefore, this would be useful for the interlibrary loan staff to see on the first page of the request, rather than having to click through to the notes section.

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

    As of the June 2021 release, the digitization note is transferred to the resource sharing request that is created by the conversion.

    The note appears in the task list – see https://www.screencast.com/t/1SyVsRmnR1S

17. Add labels to Digitization request form

    The following three labels are on ”Digitize Other Issue” request form, but not on the “Digitization” request form.

    ・almaDigitizationOther.manualDescription
    ・almaDigitization.volume
    ・almaDigitization.issue

    We also want the three labels to appear on the “Digitization” request form so that patrons can specify the issue they want to digitize when multiple issues are bound.

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

    Where there are issues with volume/issue (and therefore a Description) then the request form is on the item level. The selection of the item is what identifies the exact volume/issue.

    The ”Digitize Other Issue” option is intended to enable requesting a volume that is not catalogued and therefore cannot be selected for requesting. This is why it has explicit volume/issue fields.

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

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

    Please see the attached screenshots of the analytics report results.

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

19. Increase the visibility of digitization requests in case of multiple requests

    When there is more than one digitization request on a same item (same or different requesters), only the first request is displayed in the Task List. When this request is completed, the second request is not listed in the Task List or in the “In Process Items” page, except when the barcode is scanned again.

    We think that “In process Item” page should not be empty once the first request is completed. Or least, there should be an alert informing the operator that there is another request on the same item just ready to be fulfilled...

    • 

    322 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…)
    8 comments  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
    Completed  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

    August 2026 release notes -

    Digitization Request Queue Indicator

    
    

    Manage In‑Process Items now highlights when an item has additional digitization requests waiting in the queue. Staff can use the new View Queue row action to manually activate the next one, improving workflow efficiency and ensuring queued digitization work progresses smoothly. Completing the active request automatically activates the next in the queue.

20. Allow staff to override auto return when a borrowing request is received after needed by date has passed or request has been cancelled

    When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.

    Likewise, Alma automatically updates borrowing reqeusts to returned when they've been cancelled by the user after the lending library has already shipped the item. Alma does provide an alert when this happens, which is helpful. We would like the option to override this automatic return too.

    When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.

    Likewise, Alma automatically updates borrowing reqeusts to returned when they've… more

    53 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