ILLiad Ideas
64 results found
-
Create a way for ILLiad to export citations associated with their requests directly to RefWorks or another reference manager. Often users acquire articles first through ILLiad and then decide if they want to use them for their research. The DOI resolver and DOI DSP addon features provide complete citations for our users. It would be helpful if a user could simply export the citation associated with a request directly to a reference manager for their bibliography.
4 votes -
Enable exclusion of subdomain for integrated SAML - fix broken Logon as User functionality Updating to the new integrated SAML prevents staff from utilizing the Logon as User button in the Client without redesigning the web directories.
The key that had been put in place to assist with circumventing proxy folder redirects - StaffProxyWebURL - will not work for integrated SAML sites when it its value is pointed to subdomains, the way it could with EZProxy.
Locally-hosted Shibboleth sites can set requireSession = false to support the Logon to User feature and LDAP and ILLiad Exclusive sites can use the feature without additional adjustments.
This means that sites who implement the integrated SAML are…
4 votes -
Add autofocus to the first field on all ILLiad web forms (request forms, search page, etc.) It would enhance accessibility if each of the ILLiad 9.1 forms (request forms, search page, new user info, reset password, login, etc.) used the autofocus feature to activate the cursor in the first blank field. See: https://www.w3schools.com/tags/att_input_autofocus.asp We're working on adding this manually to our pages, but having it in the pages by default would be better!
4 votes -
Renew Button doesn't immediately reflect new status in the next page When you click the Renewal button on the ILLiadMainMenu.html page, it takes you to the page that shows all the information about the transaction but even though the status line tells the patron they have placed a renewal, the TransactionStatus still shows Checked Out to Customer, and the Renew button still seems to be active. If you refresh the page, then those update, but it's confusing to the patron.
4 votes -
Add hidden fields to request forms for more flexibility Currently the Status field is the only option for creating unique request forms. It would be nice to be able to have more information to customize request forms. Some of the user information, such as Status or User Info # would be valuable to work with on request forms. If could be queried to hide/add fields based on unique statuses. The data could be in a query parameter or hidden input field on the page.
4 votes -
API method to get requests based on other parameters besides User Extend the Web API to include methods that will return data of requests made on parameter like RequestType and RequestDate. This would enable the interfacing of ILLiad data with other database systems.
4 votes -
Improve functionality of the patron's search results webpage We would like to see improvements to the ILLiad search results webpage. These improvements would benefit all users, but particularly those users with a large number of requests or lengthy user history. Some suggestions provide by users:
A method to reorder results in ascending and descending order.
A method to limit/filter results by various values, such as Document Type.
A method to limit/filter results by date received and/or date finished.
A method to sort requests alphabetically, such as by title or author.Thanks!
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 -
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 -
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 -
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 -
Upgrade Forgot Password to Forgot Login some users do not recall their username, so we are wondering if the Forgot Password feature would ever upgrade and offer other options such as allowing input of email address or alternative options between forgot password vs. forgot username and etc.
3 votes -
Improve web field notes Patron often add multiple citation entries into one field i.e. paste all of teh citation information into the journal title field. It would be helpful to have field note more obvious to users. Maybe something like this example
https://www.screencast.com/t/YDgAWZB4EE-submitted on behalf of Cleveland Health Sciences Library
3 votes -
Reorder items in the Custom DropDown Table Please give libraries the ability to re-order the CustomDropdown Table in the Customization Manager - there are cases when an order other than alphabetical is what makes most sense to the user.
3 votes -
Include Display Status in any call to the API that returns a Transaction Status Currently, Display Statuses are not returned with Transaction Status information when using the API.
Our library is using the API to integrate ILLiad into the patron account interface; it would be very helpful to be able to use the Display Status table to mask the queue names.
3 votes -
Expand the borrowing statuses in which patron cannot cancel. Not sure if this goes in the web interface. We have some custom queues we use for items that we've already ordered and do not want to have the ability for a patron to cancel. Right now can only specify cannot cancel if item is in the "Request Sent" status.
3 votes -
Allow patrons to re-order "All Requests" by clicking on column header - to prevent duplicates Allow patrons to re-order "All Requests" by clicking on column header - patrons could look for titles to prevent duplicates.
2 votes -
Conditionally display due date on All Requests web page On the All Requests page in ILLiad patron web interface, make the display in the “Request Finished” (or similar) status appear without the due date, while the others retain them.
2 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.
2 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
- Don't see your idea?