ILLiad Ideas
530 results found
-
Integrate ILLiad with Google Docs Allow ILLiad to merge data not only with Microsoft Word but also Google Docs because many organizations are migrating from Microsoft Office to G Suite
4 votes -
Eliminate extranneous shipping labels for multi-piece loan transactions For Lending Loan Shipping Labels, and Borrowing Return Shipping Labels, we only need ONE shipping label per transaction. As is, if we ship a 4-volume set under one transaction number, we get 4 shipping labels. This means that each time we print, we either have to discard extra labels, or take the time to delete the extra labels from the print document.
36 votes -
Add RequestType to default IFM ILLiad reports Purdue University needs to break down IFM charges by RequesType for internal reporting. Having this in the default reports would be very helpful. We'd like to see it for both Lending and Borrowing.
7 votes -
Display of Tracking Table on the Web Add ability to customize which statuses from the tracking table display to the user on the ViewDefaultDetailed.html page
2 votes -
ILLiad Event Hook for Borrowing Item Shipped Would it be possible to create an event hook that would trigger when ILLiad detects that an item has been updated to Shipped in OCLC? Currently, my code is regularly checking the Request Sent status for a new value in the DueDate field, but it would be preferable to have it triggered by a system event.
16 votes -
Change when billing occurs Currently, when the lender updates a request to ship, the borrower is automatically charged. This creates problems when items are never received or the wrong item is shipped. The borrower should have an option to indicate that the item was never received or the wrong item was shipped and not be charged through IFM in such situations.
1 vote -
Add ability to track sent email copies by template It would be helpful to know which email templates were being used and which are not. There is currently no mechanism to track outgoing notifications by ID. University of Washington would use this information to remove unused or infrequently used templates, to reduce the amount of options in the notifications drop down.
1 vote -
Flag or add a notification of some sort sort to identify stale requests. It would be nice to be able to see requests that are sitting around in queues when they should have moved on or some action might need to be taken by staff. An example would be items that have been sitting in Request Sent for too long with patrons not getting their materials in a timely fashion.
16 votes -
Improve retrieval of Alma holdings when there are multiple volumes. ALMA doesn't have holdings for each volume when there are multiple volumes, so in z39.50 only the most recent volume is pulled up in the search. Is there a way for ILLiad to handle this better? If not within z39.50, then via an addon maybe? (This is from ticket 8080)
24 votes -
When processing incoming borrowing requests, allow to search on any number the same way it works to process lending returns You receive a book in borrowing and the default search box is TN, which you almost NEVER have...you usually just have the OCLC ILL number or the not-helpful TN from the lender. In lending, there is one box from which to scan any number when processing lending returns. Would like this same feature in borrowing side.
35 votes -
Change how system auto-creates and inserts due date for Lending requests At Stanford, we often page books from one site to another and this can take a bit of time. We want the DueDate to reflect when we mark the book as Shipped, instead of when we first open the request. It would be beneficial if changes to this functionality also improved the client's ability to deal with server addons or workflows that bypass opening the request form, entirely, since those requests can wind up missing the due date on pull slips.
4 votes -
Enable automatic Odyssey coversheets for borrowing There is currently a function that allows a custom coversheet to be inserted automatically before Odyssey sending for Borrowing & Document Delivery, but not for Lending. It would be great from the lending library’s standpoint since we’d be more compliant in terms of copyright & licenses if we could include the Title 17 notice there, and any usage restrictions. It would also be great for the borrowing library’s standpoint since Odyssey is a more direct delivery method than Article Exchange
13 votes -
15 votes
-
Allow renewal requests while patron blocked Allow patrons to submit renewal requests for other books even when they're blocked (with web access) for other overdue items. Maybe even add an option on the user account to let us pick and choose who we give this privilege to.
3 votes -
Option to print articles and loans separately in Doc Del In Doc Del, have a dropdown choice of printing either articles or loans instead of all. We process these on different floors and it's really handy in Lending.
6 votes -
Enable text/sms messaging options without a third party provider. This is from ticket 8079. Site would like to see text messaging/sms options that do not require a 3rd party provider.
16 votes -
See last opened request Could there be a way to see a list of the last 5 or so requests that a staff person opened? We sometimes forget to place notes or verify a piece of information before it gets routed to the next step. Titles or usernames are not always remembered correctly to find the request again. Even just the last request opened would be helpful.
9 votes -
Extend database field length for date field We regularly receive requests for microfilm reels from patrons who cannot fit the request information into this field. For example, if there are specific dates from different months and years, this never fits. We always have to contact the patron and ask him/her to put this information in the notes field. If the date field for loan requests could be longer, this would be very helpful to us.
2 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 for staff to login to the ILLiad client via LDAP or SSO From customer: If we could automatically/programmatically create Staff User accounts in ILLiad and have the option for them to authenticate via LDAP to the ILLiad client, that would be really convenient. (Or if there was a Single Sign-On option that used the computer's Windows credentials to authenticate staff users).
4 votes
- Don't see your idea?