ILLiad Ideas
526 results found
-
Spell Check for custom emails When I type a custom email to a patron from within the client, I'd like spell check.
22 votes -
Support for multiple renewal requests by web user The end user needs to be able to request a renewal more than once. Also, once that renewal has been approved the next time, it should go back to Awaiting Renewal OK Processing, regardless that it has already been at that status once before.
22 votes -
Customize List of Queues in Route Button Dropdown List {Submitted by Kerry on behalf of customer}
UC Boulder would like the ability to customize which queues appear and in which order they appear in the Routing button's dropdown list in the ILLiad Client. The site does not use many of the default queues that appear in the dropdown list and wishes that it was possible to make their more frequently used queues easier to access.
They would like to be able to:
General Wishes:
*Suppress default queues.
*Rearrange the order of all available queues, without the forced separation between default queues and custom queues.Unicorn wish:
*Have the ability…21 votes -
Custom Pop-ups Allow the creation of pop-up messages based on custom parameters. For example, I would like to create a pop-up that appears for flagged items when processing lending returns.
21 votes -
Single Accessible Coversheet Interlibary loan articles often fail accessibility checkers when they are uploaded to a learning management system with the coversheet. Articles posted without a coversheet also fail to meet accessibility standards. If ILLiad created a standard coversheet, that meets accessibility standards, all libraries could use this document and help their faculty improve accessibility of shared materials.
20 votes -
question Provide an internal to ILLiad customer question function. Instead of us having to use an email, etc., incorporate functionality into ILLiad for customers to contact us regarding the request and for us to answer and have it all recorded within the transaction.
20 votes -
9.1 replacement for Expires table tag to display pdf expiration date The old web pages displayed an 'Expires' date on the table of electronically delivered articles. This let users know how long they had before they would have before the PDF disappeared.
There is no way to include this in the new 9.1 web pages since table tags are no longer supported. It would be great to have something to replace this, using DaysBeforeElectronicDeliveryCleanup and the transaction's tracking entries to determine when it was first Delivered to Web to calculate the expiration date.20 votes -
Do not move completed requests to Cancelled by ILL Staff when disavowing users When a user is disavowed, it makes sense to cancel all outstanding requests so that they are not processed. It does not make sense to move completed requests (in queues Request Finished or Delivered to Web) to Cancelled by ILL Staff. This skews statistics.
20 votes -
Integrate WSILL IFM Refund in ILLiad WSILL allows libraries to initiate refunds when erroneous charges are applied. Now that Undo Shipped is not an option for IFM requests, this functionality is needed.
20 votes -
I'd like to have the power to make mass changes such as changing Department Names. example: Our Political Science department changed their name. I want to be able to make this change to all the existing patrons it would apply to.
20 votes -
Filter notifications on web to only show emails sent to the user Ability to filter notifications under the History > Notification’s page to limit only emails sent to the patron. Right now, this includes all emails sent from ILLiad related to that user's account such as emails that were sent to Acquisitions about purchasing a book.
19 votes -
Allow the CreationDate field to be added to loan and article pull slip templates It isn't currently possible to add the CreationDate field to the loan and article pull slip templates because that field is not included in the xlsx datasource columns. Can this be fixed? Having the CreationDate field on pullslips would make it easier to know which printed requests are close to expiring and need immediate attention.
19 votes -
Extend database field length for ISSN Extend the max field length for the ISSN/ISBN field beyond 20 Characters. Users sometimes copy/paste an ISBN with a prefix (e.g. ISBN: 1234567891234). If they do that with a 13-digit ISBN, the last digits are cut off.
19 votes -
Bulk Renew in Borrowing With libraries closed indefinitley all over the world, we have to push due dates out, possibly multiple times. This is easy enough to do in an ILS, but ILLiad does not allow me, as the Borrowing Coordinator, to push out a renewal request for one new due date for all items currently due before that date. That would save me hours, possibly days of work!
18 votes -
Enable an end of semester due date change function It would be great if I could, through the Customization Manager or the client, set a Due Date Override so that I could make everything due before the end of the semester for specific patron groups (Undergraduates go far away over winter break and don't give their stuff back, but Staff are here year round)
18 votes -
Allow RapidR borrowing renewals to be sent in batch by the Send OCLC Renewal Requests button Currently, the Send OCLC Renewal Requests button will send out renewals for all requests in the status of "Renewed by Customer to MM/DD/YYYY", but it only works on requests with a SystemID of OCLC. Now that RapidR allows renewals within ILLiad, it would be helpful to be able to batch send requests to Rapid using the same button, so that renewals can be sent out regardless of the System ID.
The query that populates the ESPUpdate table is currently:
"SELECT t.TransactionNumber, t.ILLNumber, t.SystemID FROM Transactions t JOIN Users u ON (t.Username = u.Username) " +
"WHERE ((t.TransactionStatus LIKE N'Renewed by…17 votes -
Transfer User Notes when merging users When an existing user account is merged with an new one, in addition to moving the open requests, we would like any User Notes to be moved as well. We use these notes to track various issues with patron accounts and right now staff are manually copying each note.
17 votes -
Auto due date/overdue reminders should continue, even after an item has reached "very overdue" If an item gets to the stage of "very overdue" in ILLiad and then the item is renewed, I've noticed that ILLiad's auto-reminders stop going forward. It would be nice if they continued to be sent, adjusting for the new due date, regardless of the previous overdue history
17 votes -
Make barcodes more usable/searchable in the ILLiad client Expand the ItemNumber field in ILLiad to accommodate multiple barcodes for multi-volume sets. Add ItemNumber to the default Number search in the ILLiad ribbon for easy access. Add ItemNumber to fields searched by TN/ILL # search on Check Item In interface.
All of the above would allow more efficient handling of borrowing returns when paperwork with Transaction is missing.
17 votes -
Notify Patrons We Are Still Trying to Fill a Request In a recent OCLC customer service webinar it was suggested that we notify patrons regularly as to the status of outstanding borrowing requests. This would not be possible for us to do manually due to our work load. If we could use ILLiad to send out a notice for borrowing requests to let patrons know we are still trying to fill their requests, that would be great.
17 votes
- Don't see your idea?