ILLiad Ideas
532 results found
-
Improve Z39.50 and FOLIO connection There's already a call out to FOLIO to improve how multi-volume holdings appear in XML to make them visible via Z39.50, but it would probably help matters if Atlas Systems and FOLIO worked together to make this improvement for all libraries migrating to FOLIO. https://issues.folio.org/browse/ZF-84
Basically, if there are multiple volumes of a title, only summary holdings and inaccurate availability status are visible through Z39.50. Some libraries have implemented custom addons to get around this, but this is really a workaround to what should be a standard function.
8 votes -
Ability to add tags to Default Notes field of Cancellation Reasons. Cancellation Reasons have associated Default Notes fields. It would be great if tags could be inserted into the Notes fields to auto-fill information.
Example:
Cancellation Reason: We could not fill your request by your deadline.
Default Note:
You indicated you did not need this item after <#Transaction.NotWantedAfter>. If you would still like to received this item, please ....8 votes -
Prevent borrowing renewal requests when the lending library will not accept them As a lender, FSU does not accept renewals and this is indicated in our notes, in the Client when we mark a request as Shipped and in the Policies Directory. In WSILL, the Renew option disappears when a borrower has exhausted renewal requests. There is no equivalent in ILLiad and borrowers can continue to send renewal requests regardless of settings and indicated preferences. Borrowers should not be able to request renewals when lenders have indicated they will not be accepted. (via KAK)
8 votes -
Change the default "Save as type" for Electronic Delivery from TIFF to PDF Good to have a copy of files which wasn't sent via Odyssey and are sitting in ED. It will save processing time to save files form Electronic delivery.
8 votes -
Add SLChangeUserInfoSucceeded for ILLiad patron information webpages This option exists for Ares but is not available in ILLiad 9.1
The currently available webpages allow users to update address information and other personal account details, but there is no mechanism for letting a user know that their update has been successfully submitted-- i.e. the page reloads, displaying the information a user has just entered into the available fields, so from the user perspective there has not been any apparent change.8 votes -
ability to update OCLC request to complete Attempting to Check In from Lending Library will cause a Connection Manager error if an item is returned to the lender but the borrowing library has not performed the OCLC Received or Returned update.While the Connection Manager error can be cleared, the system flag will remain unless the borrowing library updates the request.
It would be helpful to have a way to override these flags, particularly if the item is considerably overdue.
8 votes -
Ability to push through renewals on the lender side, singularly and in bulk. Ability to push through renewals on the lender side, singularly and in bulk. Borrowers should be notified of the new due date.
8 votes -
Overdue Workflow Enhancement Add option set a time to auto-route extremely Overdue requests (e.g. those which have received notice 3 + 30 days) into a custom queue indicate that the item is lost and an invoice needs to be created.
8 votes -
Cover sheet for Lending Requests Add the ability to apply a coversheet on the lending side which would allow lenders to include copyright information as required by the CONTU guidelines.
8 votes -
Allow API to Add, Remove, and Update records in the UserValidation table Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.
8 votes -
ILLiad stub accounts made when users fail to complete the registration process should be assigned to an NVTGC in use. When an ILLiad stub account gets made due to incomplete registration it should not be assigned to a site not in use like "ILL." Allow users to configure what site/NVTGC those stub accounts should be assigned to.
8 votes -
Remove Patron Name Field in OCLC request When you submit a request through OCLC there is a field in Borrowing Information for the patron name. We have been deleting the patron name from this field for some time because we've found that it is sent to the lending library. If the library has a newer version of ILLiad, the patron name isn't sent, but if the lending library is on another system, it is. Removing this field would be an easy fix for patron privacy.
8 votes -
Have the Patron ID number viewable on the request page. Currently, you can only see the patron's name, address, status, delivery methods on the patron tab in Borrowing. You have to use the "View User" button to access the patron's ID number. This would help eliminate a step when you need the ID number for accessing library accounts and fines in an ILS.
8 votes -
Track flag history along with status history of each request It would be really useful at our library to be able to track flag history in the Staff Client along with status/queue history of each request. We would love to see what flags have historically been added to a request, and when and by whom they were added and removed.
There are several flags in our system that stay on requests indefinitely because that's the only way we can identify and run reports on those requests specifically. There are also many times it would be useful to see who applied a flag to a given request so that follow-up clarifying…
7 votes -
Summary Notification Provide weekly summaries to patrons for all items checked out to that patron, separating and highlighting items that are overdue
7 votes -
Add ability to "pin" or "favorite" staff Note in ILLiad request In cases where staff have the need to re-use the text of a staff note in an ILLiad request, it would be helpful to enable functionality to "pin" or "favorite" a specific note at the top of that day's listing of notes so as to get there in a single click, without having to scroll down to it (or to have to type in the beginning text for that needed note in the Recent Notes field, in order to auto-suggest).
7 votes -
Make Billing Categories Default by SystemID When new lender addresses are created it should be possible to set SystemID specific default billing categories. For example, all Rapid lender addresses should come in as Exempt by default. ISO is another example where a specific
7 votes -
Hide due dates on shipped Borrowing loans on Web 9.1 web pages, patrons can see due dates for requested/shipped items before they’ve arrived. This has confused patrons and does not always reflect the due date that will actually be assigned to the material.
7 votes -
Additional section of the homepage for storing filled article requests We have received a request from one of our most active researchers to add an additional section to the ILLiad homepage that users could route article requests to, rather than all filled requests being under Electronic Documents. This would help our users manage higher volumes of requests.
7 votes -
Keep user on Main Menu Page after renewing an item If a user is on the Main Menu page and wants to renew a checked out item, clicking on the renew button directs the user to the transaction details. Instead, allow the user to remain on the Main Menu and display the success error so the patron doesn't have to navigate back to the main page.
7 votes
- Don't see your idea?