ILLiad Ideas
532 results found
-
Match on TN in the Electronic Delivery Process form Relais FTP process does not allow the inclusion of the ILL Number from Docline requests (I assume OCLC requests either) so the received xml file only has the DocumentID for Sender and Receiver. The Electronic Delivery Process does not match the file to the request on the TN even though it displays in the form. Please enhance to match the received Odyssey file to the request by the TN if the ILL number is not included in the xml file.
3 votes -
Replace removed NotWantedAfter field and associated dropdown calendar on default web forms The NotWantedAfter field was removed as a default from the 9.1 ILLiad web pages. This should be be replaced, with the corresponding hidden field removed, and a dropdown calendar should appear when clicking in the field box, as in previous versions of ILLiad. This feature was appreciated by our patrons and desired for the 9.1 pages. (write up by Kerry).
3 votes -
3 votes
-
3 votes
-
3 votes
-
Ability to reorder web Alerts so they appear in a different order on the web page Ability to choose the order in which the alerts appear on the web pages. This includes the #SYSTEMALERTS, #USERALERTS,#STATUSALERTS alerts.
3 votes -
Option to "Undo Conditional" We would love to have an option to "Undo Conditional" for those times when we realize too late that a conditional was unnecessary. This would be helpful if, for example, we send a "Non-circulating" conditional before realizing the request is for an article, or conditionalize for "Not as cited," then we find the citation. There are any number of situations where we may miss information in a request and send a conditional, then realize it was unnecessary. Even if this is only possible until the Connection Manager runs, it would be a very useful feature. Thanks!
3 votes -
Collapse the Electronically Received, Checked Out Items, and Outstanding Requests menus and all their items on the main patron web page Ability to collapse the listings under a link for each of under the categories of Electronically Received, Checked Out Items, and Outstanding Requests on the main page rather than listing all possible requests under each category. This would match the style for "Cancelled" and "Completed Requests" and also take up less room on the main page if the patron has a lot of requests in one or both categories. Otherwise, the patron needs to scroll through all three (3) category listings to get to the bottom of the listing.
3 votes -
ILLiad does not pull all data from Docline when an ISBN for a book is provided For example, the field will be "978-0". This leaves staff without entire citation and have to go back to Docline to retrieve it. It would be great if this were fixed
3 votes -
Adding a notification about no ILL number matches Adding a notification to when a No ILL Number Match comes in to ILLIAD to be received. Currently there is no notification about unmatched items. So I have to set reminders a couple of times a day to go in and check the electronic delivery screen to make sure I am not missing anything.
3 votes -
Check Routing rules after a TN is moved to a new status/queue via IDS Logic ILLiad does not apply routing rules to a TN if it was moved to its current status via an addon, like the IDS Logic addon for example.
3 votes -
Have ISBN Search populate the fields on the webrequest form The old GIST webpages for ILLiad had a function that allowed a patron to enter an ISBN into a search box on the webrequest form, search for the item, and have it populate the title, author, etc.
3 votes -
color code due dates on patron webpages On the patron webpages, color code the due dates on the checked out items display. Green dates - due in the future, Yellow dates - due in the next week, Red dates - overdue.
3 votes -
Encrypt Passwords in Customization Manager Having an email password in plain text available to anyone with Customization Manager rights is a security risk.
3 votes -
Batch Add notes to requests It would be helpful to be able to select multiple requests then click a button on the ribbon saying "Add Note," which would then open a field to add a note to all highlighted requests. Having to open each request to add the same note repeatedly is unwieldy.
3 votes -
Allow auto renewals for ILLiad requests by status and date settings A customer asked for this during the #ILLiad24 event at roundtable. Have an options for settings per time period like semester table in Ares to specify dates until which items can be renewed automatically. After that date items could be renew denied or manually processed. It would be nice to set this by status so that faculty could request renewals across semesters but students would need to return items by end of semester etc. Decision Support Pipeline and Business Rules can probably already make this work when the new renewal features are released.
3 votes -
Multi-language support for ILLiad Patron Web Interface Please provide multi-language support for ILLiad web pages or a Spanish language web interface option.
3 votes -
Case-insensitivity for queue name and custom field names When creating routing rules or addons that route to queues, allow for case-insensitivity. For example, normal behavior would prevent the renewal button from showing in the default 9.1 web pages if a routing rule includes "Checked Out To Customer" instead of "Checked Out to Customer" since this isn't the correct name case sensitivity in ILLiad. Allowing for case insensitivity could open the door to allowing for custom field names.
3 votes -
satisfaction survey per transaction We would like the patron to be able to answer a satisfaction survey when they receive their document or response. it would be valuable to identify transactions that were challenging (from the patron's perspective) and have front-line staff followup with them. a 1-5 star rating would be sufficient along with a comment box.
3 votes -
Electronic Delivery Utility Enhance EDU to allow multiple copies (using Automode) to process files from the same scanned file folder for different nvtgc sites. Currently the EDU reads through all scanned files in a folder and when more than one EDU is running it can lock the file causing errors for the other EDUs trying to process that file.
3 votes
- Don't see your idea?