ILLiad Ideas
540 results found
-
Another button for "submit and place another request" that reopens the same form again This way the request form automatically appears and the users don't have to go back through the navigation menu.
1 vote -
Allow autofill for New User Registration Form for users who have previously abandoned the form. Provide a way for the UserValidation to import into the Registration Process even though the Patron account was created and it is showing the Cleared as New.
2 votes -
View item format on detail page It would be helpful to view an item's format in the Detail page of a request. We recently sent a music score instead of a sound recording because the titles were the same and no ISxN was given. We would love an option for the format to be visible in the Loan Info tab (preferable) or Item Information section.
1 vote -
4 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 -
PMID Addon It would be great to have an Addon similar to the existing DOI Addon. If a user on the webform enters a PMID, ILLiad searches and fills in/adjust the rest of the request data.
11 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 -
Ability to hide the AccountNo field in the Transaction Request Forms We'd like to be able to hide the AccountNo field in the Transaction request forms on the web. Right now, if we want Borrowing billing active with each patron being assigned a Default Account, the transactions created do not have an account selected unless we include this code:
<select id="AccountNo" name="AccountNo" size="1" class="f-name"><#OPTION name="ValidAccounts">But we don't want the patrons to see that account at all. They don't need to know they even have an AccountNo. Right now there is no way to pass it through as a hidden value though.
1 vote -
Warn or prevent staff from marking requests found after they have aged out to next lender in OCLC OCLC Lending requests remain in processing queues even when they have aged out and moved to the next lender (or are returned to the borrowing library unfilled, if the library is the last/only in the lending string). Staff are unable to filter by or see the OCLC status in grid views, so individual requests must be opened to see if a request is no longer in a CONSIDERING status and has aged (or even been deleted by or cancelled by the borrower). Requests may age out for various reasons while sites are continuing to retrieve/process requested items and it is…
54 votes -
Tag other ILLiad users in a staff note We can use flags and notes to ask other ILLiad staff users questions about a request, but it would be even simpler if we could include @PersonName in a staff note and notify them that they'd been tagged for review/response.
6 votes -
Support multiple files for Illiad transactions We have some files that get quite large when delivering PDFs. We would like to parse these out - call them chapters or parts. unfortunately, Illiad has the restriction of a single file per TN. We would like the option of being able to upload multiple files per TN, so that when batch loading, all files with the same TN would be attached to the transaction (think TN018765a,TN018765b,TN018765c all being attached to transaction TN018765)
9 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 -
Allow staff to customize which transaction statuses are displayed under each heading in the patron interface I would like more customizable display options for transaction statuses in the patron interface. For example, once a patron clicks the "Renew" button, the request disappears from their checked out items list until the renewal is processed and routed back to checked out to customer. I would like items in the Renewed by patron status to also appear under the checked out heading.
We use a lot of custom queues and would like to be able to manage where requests display in the patron interface.
2 votes -
Option for selecting queues from a drop-down when creating routing rules To piggyback off of the case-insensitivity with queue names ideas: https://uservoice.atlas-sys.com/forums/581665-illiad-ideas/suggestions/42375580-case-insensitivity-for-queue-name-and-custom-field. Another option to avoid having errors if a queue name is typed in a routing rule without proper case sensitivity would be to have a way to select queues such as a drop-down menu when creating custom routing rules.
4 votes -
Save Customized Grids It would be incredibly helpful to be able to save grid layouts as .xml files in ILLiad to apply to other users or to other queues for the same user. It appears this is already supported in Aeon: https://support.atlas-sys.com/hc/en-us/articles/360011821354-Saving-and-Loading-Grid-Layouts
(I saw this suggested on the Ares Ideas area; this would be great for Ares as well.)2 votes -
1 vote
-
Email Notification to a user/lender/borrower that is NOT tied to a specific request, but from the user record, or lender address record. It would be great to be able to send an e-mail notification (from a template) to an individual user, lender, or borrower from the user record, or address record for a library. One instance I would use this for would be to provide individualized tracking information that may apply to a large number of requests at one time. Or to alert a patron of an entire list of things they have out--or to let a group of patrons know that we are temporarily suspending a particular aspect of service. Although many of these things could be handled through a regular…
10 votes -
12 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
- Don't see your idea?