1047 results found

1. Adding an interested user for paid invoice (or pol)

   For the orders to be reimbursed by other department, we cannot initiate the reimbursement request until the order is paid. Often, the invoice team would have to notify the management's assistant. The mechanism of "interested user" is already in place. I wonder interested user "after invoice is paid" can be set up.

   •  

   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  ·  Acquisition - PO & POLine  ·  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

2. Allow customers to select multiple retention reasons for Item records.

   Allow customers to select multiple retention reasons for Item records.

   As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:

   1. Institutional last copy

   2. Faculty publication

   3. Rare

   4. Committed to some Shared Print program

   5. Digitized material

   Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff workflows, respectively:

   1. Blocking withdrawal/weeding at the institutional (IZ) or consortial (NZ) level by collection development staff

   2. Generate a report that can be used to populate a display shelf highlighting local research at our campus

   3. Identification of materials that should be prioritized for preservation treatment

   4. Block withdrawal/weeding and select for inclusion in data integration/sharing with partners

   5. Identification of materials that are good candidates for off-site high density storage

   Absent the ability to assign multiple values in a dropdown, which will provide a kind of authority control for approved statuses, we would be dependent on cramming all of this information into the free text Retention Note field. Obviously, this would be more error prone as it would require 100% consistency to achieve the same level of data reporting as the dropdown menu options would have. Additionally, parsing a free text field to find specific substrings in an Alma Analytics report is a much more sophisticated and therefore difficult task to accomplish. This would therefore have the effect of limiting the number of staff who are capable of effectively querying for all retention reasons.

   Allow customers to select multiple retention reasons for Item records.

   As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:

   1. Institutional last copy

   2. Faculty publication

   3. Rare

   4. Committed to some Shared Print program

   5. Digitized material

   Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff… more

   72 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  ·  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. Facilitate entry of data into the resource sharing form from an external source

   Recent user experience testing for our resource sharing service indicated users would like a way to easily paste in data from other websites into the resource sharing form. For example, they would like to harvest the data easily from Google Scholar or another database and enter this into the form without manually copying and pasting each piece of data from one website into the webform. One way this could be accomplished is using a browser extension similar to Leganto's Cite It. When they find a resource they would like to request, this browser extension could harvest the required data. The user could then open the resource sharing form and paste all the data at once from the browser extension into the form. The browser extension might also have the ability to lodge the request information directly into Alma, bypassing the resource sharing form in Primo altogether.

   Recent user experience testing for our resource sharing service indicated users would like a way to easily paste in data from other websites into the resource sharing form. For example, they would like to harvest the data easily from Google Scholar or another database and enter this into the form without manually copying and pasting each piece of data from one website into the webform. One way this could be accomplished is using a browser extension similar to Leganto's Cite It. When they find a resource they would like to request, this browser extension could harvest the required data.… more

   8 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

4. User Requests Should Pop or Be more Visible for Cataloguers

   When cataloguers are processing new books or fixing bibliographic records or item records, there is no notification that a user has requested the item we are working on. We won't know to give the item to Fullfillment so that they can put the item aside for the user.

   I know there is a little number that indicates there is a request, but for new books ordered in there is already 1 request from Acquisitions. This does not pop-up and it is just a little number that you can barely see in the results screen. It should be much more obvious when a user has put an item on hold.

   When cataloguers are processing new books or fixing bibliographic records or item records, there is no notification that a user has requested the item we are working on. We won't know to give the item to Fullfillment so that they can put the item aside for the user.

   I know there is a little number that indicates there is a request, but for new books ordered in there is already 1 request from Acquisitions. This does not pop-up and it is just a little number that you can barely see in the results screen. It should be much… 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…)
   1 comment  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Incoherent date in the “Date” column when the transaction type is “Expenditure”

   According to the developer, the expenditure date comes from the invoice date and always comes from it (see documentation at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/030Invoicing/020Creating_Invoices).

   As you can see there, the calculation of the exchange rate is also done according to this date: "By default, Alma calculates the value of the transaction based on the exchange rate on the date specified in Invoice Date."

   Now we know where the date comes from when the type of transaction is “Expenditure”. However, in other types of transactions (transfer, allocation, encumbrance, etc.) the date that appears corresponds to the moment in which the transaction occurs. For this reason, it seems impractical that in the type of transaction “Expenditure” the invoice date is used and not the date on which the transaction is triggered, that is, the “create on” date.

   We request to incorporate a new column in the table of visualization of transactions that is “create on”.

   We provide explanatory screenshot of how it could be implemented.

   According to the developer, the expenditure date comes from the invoice date and always comes from it (see documentation at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/030Invoicing/020Creating_Invoices).

   As you can see there, the calculation of the exchange rate is also done according to this date: "By default, Alma calculates the value of the transaction based on the exchange rate on the date specified in Invoice Date."

   Now we know where the date comes from when the type of transaction is “Expenditure”. However, in other types of transactions (transfer, allocation, encumbrance, etc.) the date that appears corresponds to the moment in which the transaction occurs. For… more

   •  

   •  

   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…)
   1 comment  ·  Acquisition - Funds  ·  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. Change the pick up location when an item is "On Hold Shelf"

   When an item is "On hold shelf" (in a library A), by clicking on "Edit", we can change (only in Alma fortunately) the pick up location (to the library B for example).

   It's a good option, useful when a user has made a mistake and would like to change the pick up location.
   In Alma, currently, when you use this option (so edit > change the pick up location", there is no notification to the library A (livrary A have to send the book to library B).
   So, in the patron folder, the pick-up location is B (as the user's request) but in reality the book is still in the library A.

   Library A can't know that user has requested an other pick-up location.

   In fact, this option is useless as offered.

   If a user resquest to change the pick-up location when the item is "On hold sheld", the item should appears in the "Expired Hold Shelf Item" > "Send to the library".

   Thanks

   When an item is "On hold shelf" (in a library A), by clicking on "Edit", we can change (only in Alma fortunately) the pick up location (to the library B for example).

   It's a good option, useful when a user has made a mistake and would like to change the pick up location.
   In Alma, currently, when you use this option (so edit > change the pick up location", there is no notification to the library A (livrary A have to send the book to library B).
   So, in the patron folder, the pick-up location is B (as the user's … 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…)
   0 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

7. Resource Sharing Borrowing Requests - Renewed by Partner Status

   It would be great if there was a way to configure requests so that they do not retain the status 'renewed by partner' and instead automatically revert to 'loaned item to patron'

   9 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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. Clearly show a patron's home campus when placing requests

   Occasionally we will need to place a 'Patron physical item request' on a title/item on behalf of a patron when all existing copies are unavailable. We'd like to clearly be able to see what a user's home campus is from the 'Create Request' screen after entering the Requesters name. Alternatively, if we were to click on the 'Select from a list' to choose the requester, we are taken to a 'Find and Manager Users' popup. It would be useful to be able to see the patron's campus within a column in this display.

   Currently, we must first go into a patron's record to check what their default campus is, so that the book can be sent to that campus for pickup when it is available.

   Occasionally we will need to place a 'Patron physical item request' on a title/item on behalf of a patron when all existing copies are unavailable. We'd like to clearly be able to see what a user's home campus is from the 'Create Request' screen after entering the Requesters name. Alternatively, if we were to click on the 'Select from a list' to choose the requester, we are taken to a 'Find and Manager Users' popup. It would be useful to be able to see the patron's campus within a column in this display.

   Currently, we must… 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  ·  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

9. Provide the ability to sort the order of Resource Sharing Requests and General Electronic Services requests.

   Right now he tables which control the orders of requests in the Get It Window are currently not "interdisciplinary", which means that it is possible to sort the order of all General Electronic Services among themselves, all Online Service, etc. But it is not possible to control the complete sorting of services in the ViewIt or GetIt. Would be nice to sort together.

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

10. Select partners from multiple pages when adding to rota or template

    When adding partners to a borrowing request rota or rota template, you have the ability to add multiple partners at the same time but only if the partners appear on the same page of the partner pick list. Whenever you move to a different page of the pick list, selections on the previous page are lost.
    Alma already has the ability to remember selections across multiple pages in other functional areas (e.g. selecting portfolios for activation from a CZ collection).
    It would make creating a rota more efficient if this ability could be extended to the add partners list.

    12 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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. Resource Sharing Borrowing Requests back button

    For some reason the Resource Sharing Borrowing Requests screen does not have a back button or a method of clearing the search. Even if you quick link the screen the link takes you to the search you have just done. It would be extremely useful to have a back button or a method of clearing the search.

    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. Reprint the slip for physically received copies

    In "Fulfilment > Resource Sharing > Borrowing Requests > Physically received by library" the option to reprint the slip for physically received copies (e.g. because the printout did not work) is missing. In the submenu there is no option to reprint the slip. In "Fulfilment > Resource Sharing > Lending Requests > Shipped physically", however, there is an analogous option for reprinting the slip. This is exactly what we would like to see in Borrowing Requests.

    71 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  ·  AdminErez Shabo (Product Manager, Ex Libris) responded

    The Print Slip bulk action now enables the library staff to reprint received or returned slips in bulk.

13. Improve xml for FulResourceRequestSlipLetter and FulTransitSlipLetter

    We would like the option to add more information to our Resource Request Slips, but are limited by data not present in the xml. Specifically we would like the following to appear:

    -All request attributes
    -Course Reserve information, primarily the department placing the request

    The addition of these xml fields for possible display on these slips would increase staff efficiency when sorting and processing materials arriving from other library locations.

    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

14. Add Rapid ILL lending categories to Electronic Collections in Alma

    Please add a new Rapid ILL lending status field to electronic collections so libraries can indicate the following Rapid ILL lending statuses and more easily create logical sets to automatically send holdings to Rapid:
    • LendableInternational: You are able to fill lending requests from any other Rapid libraries around the world. This is typically the Lendable value used for print materials that you want to make available in Rapid.
    • LendableCountry: You are able to fill lending requests only from Rapid libraries in your country. This is typically the Lendable value used for electronic materials.
    • LocalOnly: You are not able to fill lending requests from other Rapid libraries, however these items are still available to fill your local patrons’ borrowing requests.

    Currently, the documentation suggests putting these labels in electronic collections’ internal notes field. https://knowledge.exlibrisgroup.com/RapidILL/Implementation_Guides/Alma_Holdings_Harvest_for_RapidILL

    It would better to have a dedicated field in electronic collections where a Rapid lending status value could be selected.

    Libraries should also have the ability to perform bulk changes to this field via the E-Collection Quick Update Cloud App.

    Please add a new Rapid ILL lending status field to electronic collections so libraries can indicate the following Rapid ILL lending statuses and more easily create logical sets to automatically send holdings to Rapid:
    • LendableInternational: You are able to fill lending requests from any other Rapid libraries around the world. This is typically the Lendable value used for print materials that you want to make available in Rapid.
    • LendableCountry: You are able to fill lending requests only from Rapid libraries in your country. This is typically the Lendable value used for electronic materials.
    • LocalOnly: You… more

    150 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  ·  Resource Sharing  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Add DOI to email sent to resource sharing partner

    Currently if a DOI is added to a request it isn't included in the email request sent to an email resource sharing partner. The DOI could help identify the correct article more quickly - seems strange that this is not included already

    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

16. Improved claiming functionality for resource sharing

    There is a need for improving claiming functionality in resource sharing. When items are borrowed by library A from library B, it should be possible for library B to automatically claim library A when lending requests are overdue.

    More details in attached file.

    • 

    224 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  ·  Resource Sharing  ·  Delete…  ·  Admin →
    Completed  ·  Dana Moshkovits responded

    Completed as part of Alma December release:
    It is now possible for a resource sharing lending library that is using NCIP-P2P to send an automatic claim to the borrowing library when the request is overdue. The claim is sent as an email.
    For more information please see Alma release notes https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/001Alma_2018_Release_Notes?mon=201812BASE

17. Is it possible to reassign an ILL request to a different library when patron sends a wrong request because he hasn't set his ILL library?
    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…)
    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

18. Prevent change of due-date when the item is under the recalled status.

    Or have an alert message of some kind when the due date is being changed.
    Because when the due date is changed, the recalled item reverts back to its initial status making it difficult to determine if there are requests placed on the item.

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

    We're exploring a solution that would allow configuration of a warning when the "Change Due Date" action is applied to recalled loans. The warning would be overridable, giving users the flexibility to proceed if needed.

    In cases where "Change Due Date" is performed on multiple items, and this warning is enabled, a pop-up would notify the user that some of the loans are recalled and offer options for how to proceed.

    This isn’t planned for immediate development, but it’s definitely on our radar

19. Allow Fines API to return closed fees in the /users/<userID>/fees/<feeID> endpoint

    Something I have noticed is that the fines API has strange behavior when it comes to returning data. /users/<userID>/fees will return only fines for a certain status supplied in the query params, which defaults to active. This makes sense and is fine, but what doesn't make sense is that /users/<userID>/fees/<feeID> doesn't return closed (paid) fees. It returns this error message
    {
    "errorsExist": true,
    "errorList": {
    "error": [
    {
    "errorCode": "401873",
    "errorMessage": "Request failed: API does not support closed fees.",
    "trackingId": "E01-1412050816-2AZKJ-AWAE514295771"
    }
    ]
    },
    "result": null
    }

    This is fairly strange, I would have expected for the fine to still be returned, especially considering that the status of the fine is returned as part of the body so the consumer could still see the status and do logic to filter out closed fees if they wanted. Or alternatively there could be a flag that the consumer sets (something like includeClosed = true/false) to allow the API to return these values

    The use case for this is that we do a nightly reconcile of our transactions and run them again through our processors just to make sure nothing was missed, due to the sensitive nature of needing to get things to do with people's money done correctly. Our processors then do a lookup and check to see if it's a reconcile (receipt# in Alma = receipt# being processed) or if someone has done a duplicate payment somewhere along the line (receipt# in Alma is different to receipt# being processed). However this doesn't work because this endpoint doesn't allow us to lookup previously paid fees for a specific feeID

    I know I could make a request to /users/<userID>/fees, with the filter of closed fines, but this is honestly a workaround and not a real solution. As I then have to search through all those closed fines in order to find the one that I want. As we continue to use Alma over the years this list could potentially be rather long for users that accrue lots of fees

    tldr - behaviour seems strange for an endpoint to not return data for a fee that does exist when the endpoint's job is to return data for one specific record, no filtering required

    Something I have noticed is that the fines API has strange behavior when it comes to returning data. /users/<userID>/fees will return only fines for a certain status supplied in the query params, which defaults to active. This makes sense and is fine, but what doesn't make sense is that /users/<userID>/fees/<feeID> doesn't return closed (paid) fees. It returns this error message
    {
    "errorsExist": true,
    "errorList": {
    "error": [
    {
    "errorCode": "401873",
    "errorMessage": "Request failed: API does not support closed fees.",
    "trackingId": "E01-1412050816-2AZKJ-AWAE514295771"
    }
    ]
    },
    "result": null
    }

    This is fairly strange, I would have expected for the fine to… more

    21 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    7 comments  ·  Fulfillment - Fines &Fees  ·  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. Bulk Recall by Staff

    Currently in ALMA, an item can only be recalled by request. While we do not allow our patrons to recall items from other patrons, we do, on occasion, need to recall items from patrons for course reserves.

    It appears that there is no way, either with the Scan in Items feature, or by uploading an excel spreadsheet, to indicate by barcode a number of items that need to be recalled, submit the recall, and truncate the due date of the patrons to which those items are currently loaned.

    If we could have a functionality like this that not only recalls the items in bulk, truncates the patrons' due dates, notifies them, but also automatically submits a resources sharing request for the patron of the title that is being recalled, that would be extremely helpful.

    Currently in ALMA, an item can only be recalled by request. While we do not allow our patrons to recall items from other patrons, we do, on occasion, need to recall items from patrons for course reserves.

    It appears that there is no way, either with the Scan in Items feature, or by uploading an excel spreadsheet, to indicate by barcode a number of items that need to be recalled, submit the recall, and truncate the due date of the patrons to which those items are currently loaned.

    If we could have a functionality like this that not only… 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 - Loans  ·  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