ILLiad Ideas
532 results found
-
Ability to delete and correct pdf - same as tif images Ex. Borrower received article on 7/13 and that one was delivered to web, but then they received it again on 7/16 from the same lender. That time it was a duplicate, and it was stuck at 'unmatched' in the OdysseyReceived table in the database, so every time they hit Electronic Delivery it would come in for them to match it and deliver it.
Usually if a site receives a wrong TIF file that is unmatched, they should use the "delete all" button in the electronic delivery screen in the client. That will change the OdysseyReceived table entry to "Deleted" and…
5 votes -
Client fields for Transaction vs Database Fields - all should be available There are several fields in the Transactions table of the ILLiad database that show up on the Borrowing Request form, but not on the Check in from Lending Library form, or vice versa. Examples: "Priority Shipping" shows up on Borrowing Request form, but not Check In form "Handle With Care" shows up on Check In form, but not Borrowing Request form. These items also do not show up on the list of fields available when customizing form layouts. Is there another way to add them to a form? If not, is there a reason for this inconsistency?
User would like…5 votes -
Scan button too close to Article Exchange button leading to missends Scan button too close to Article Exchange button leading to missends
5 votes -
5 votes
-
Allow ILLiad to receive a renewal request once it has been requested in ILS, so that ILLiad can request the renewal from the lending library If items from other libraries are checked out to users in the ILS, when that user places a renewal request, ILLiad needs to know about it so it can ask the lending library for a renewal.
5 votes -
Allow borrowing articles to deliver immediately via trusted sender and auto bill the default amount to the user If every user is always charged $x for an article, there is no reason for staff to mediate those. The billing could be added and the article delivered to the user.
5 votes -
5 votes
-
When creating new users in the staff client, default to electronic notification options Currently, none of the notification check boxes are checked by default on the new user form. Staff have to remember which of the check boxes to check to set a new user to receive all electronic notifications. It would be good to have a setting that made those check boxes checked by default.
5 votes -
Allow Z39.50 searches to work with servers that don't support unicode Several Z39.50 servers don't support Unicode or non-ASCII characters. If the ILLiad title has those characters in it, the search returns no results. It may be necessary to replace characters with their Latin equivalent before searching.
5 votes -
Allow cloned requests to be routed Option 1: Add a tracking entry that is created before the routing rule is triggered so that the routing rule can reference the tracking table.
Option 2: Create a new menu option of Clone and Route that prompts the staff user to pick the new queue.
5 votes -
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…
4 votes -
Extend length of firstname field Extend the max field length for the Users table firstname field beyond 40 Characters. We serve many patrons who have first names that go beyond this limit and their names end up getting truncated, which is not ideal.
4 votes -
bposner@gc.cuny.edu Create/enable a status for a category of users or a specific user be set so that they can only request copies and not loans/returnable. (This could be of use for people who are not local.)
4 votes -
Send Notification dropdown should only display applicable emails based on ProcessType and RequestType Emails showing in the Send Notification dropdown are apparently populated when the TN is opened, and it shows ALL the EmailRouting table entries for that ProcessType (e.g. borrowing, doc del, lending) regardless of whether that particular email has a notification template for that RequestType (article or loan).
So what happens, is that there is a long list of emails in the dropdown, and if they choose an email template that doesn't apply to that TN's RequestType, then it throws an error, which isn't really graceful.
Ideally, the Send Notification dropdown would only show applicable emails that work for both that…
4 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 -
Notification Email sent to user upon request submission Send user a confirmation email when a request is submitted.
4 votes -
Allow users to specify pickup locations on a per-request basis ILLiad should support the selection of a pickup location on a per-request basis.
4 votes
- Don't see your idea?