ILLiad Ideas
66 results found
-
Check for duplicate requests from user at the point of submitting the request form We have a few users who frequently submit duplicate requests. While a routing rule has been helping us catch these, it takes staff time and would be better if it could be caught at the point where the patron is submitting their request. I think there are two parts of this:
First, if a user has a slow connection, it turns out to be possible to click the "submit" button multiple times, resulting in multiple identical requests submitted within seconds of each other. Could default web pages be updated to disable to disable the "submit" button after it has been…
3 votes -
Alert statistics Could ILLiad keep statistics on what Alerts on the patron web interface are clicked on to view? The various website analytics software my library has used over the years has not always tracked ILLiad webpages. Having consistent stats, easily accessible from within some part of ILLiad, would be helpful.
1 vote -
Limit Cloning in webpages by status We want to be able to make the action “Clone” ONLY allowed for Completed Requests. We want to remove it from Checked out Items, Outstanding Items, Cancelled Items, and Delivered PDFs.
8 votes -
Add a user confirmation check to the WebCirc checkout process It's easy for a high-volume institution with many student workers at many desks to mistakenly check a book out to a user that is not for the user in front of them. Because the TN# is attached to the user, ILLiad then indicates that the item is checked out to the requesting user when the book may have been given to the wrong user. A simple pop-up during the checkout process confirming the username/ID# of the user the item is being checked out to would help prevent this. (and the ability to undo if necessary)
4 votes -
Improve WebCirc functionality Allow for WebCirc users (staff) to undo something they did by mistake, for instance, marking an item in transit back to ILL instead of checking it out. And/or add a "are you sure" message when moving a request to in transit that is not already at "checked out to customer"
4 votes -
Allow for more targeted web alerts Allow for multiple critera for displaying web alerts. We have 23 campuses and I'd like to be able to specify I want (for example) Faculty at One Campus (organization field) to receive an alert but not the Faculty at the other 22 campuses. (and other similar circumstances)
4 votes -
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 -
Only display "Reason for Cancellation" in Request Details on the web if the item is currently in a cancelled status. We regularly cancel items that get revived later once the patron has made a decision or change of some sort. When those items are revived, "Reason for Cancellation" continues to show in the Request Details on the web. It would be helpful if this field only displayed if the item was in the status of "Cancelled by ILL Staff" or "Cancelled by Customer", and otherwise was hidden.
10 votes -
Hide due dates on shipped Borrowing loans on Web 9.1 web pages, patrons can see due dates for requested/shipped items before they’ve arrived. This has confused patrons and does not always reflect the due date that will actually be assigned to the material.
7 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 -
Additional section of the homepage for storing filled article requests We have received a request from one of our most active researchers to add an additional section to the ILLiad homepage that users could route article requests to, rather than all filled requests being under Electronic Documents. This would help our users manage higher volumes of requests.
7 votes -
Allow WebCirc customization in Customization Manager Since WebCirc changes are not supported on Atlas hosted servers, it would be nice to add some customization options for WebCirc and WebReports into the Customization Manager.
As an example, changing the status message that pops up when checking out a transaction for a blocked user.
14 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 -
Prevent the submission of auto-truncated data in request forms Summary by KAK: There isn't anything to indicate to users that their submissions will be truncated when they enter too many characters in request form fields. We've created a workaround by using the WebValidation table for PhotoJournalInclusivePages with a validation of ^$|^.{0,30}$ to represent the field is not required and may only be submitted when its character count is less than 30.
11 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 -
Set maximum date range for Resumbit Request link in ILLiad web To allow proper tracking of current requests, this option should have some sort of maximum time restriction, where it couldn't be used after a specific amount of days.
1 vote -
25 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 -
DOI Resolver adjustment for auto Open Access DOI Resolver
1 vote -
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
- Don't see your idea?