ILLiad Ideas
501 results found
-
Allow API to update existing users
This is similar to the request to "update user account by pulling user data from org directories via Single Sign on"
8 votesCorrection: The API supports creating users but not updating existing users. We are reviewing this request.
-
Add a verification when cloning requests
After clicking "Clone to Current User" have a pop-up window/box that asks "Are you sure you want to clone this request?" Several times I have accidentally cloned a request when I didn't mean to.
1 vote -
"Import" answered email from Outlook into email history of a request
Currently we only see one side of a conversation in the email history of a request. It would be helpful to be able to import a response into ILLiad so we have a complete history in one place (as opposed to cutting-pasting into notes as we do now.)
26 votes -
10 votes
-
Populate new user registration with data from ILS after authentication
Allows users to login with their Symphony barcode and pin and then pull their existing data from Symphony into the new user registration form for Illiad account to help users complete the form.
2 votes -
New ILLiad Document Type: E-Book
Having a new document type of E-Book would help when doing custom reports.
23 votes -
Allow us to adjust the number of times a journal is requested before it appears on our copyright list.
If CONTU is not law, and our institution decides that 10 requests is the definition of replacing a subscription, we should be able to change a setting in ILLiad so that we can easily follow our own guideline, rather than ignoring the list and reconciling all titles at the end of the year.
4 votes -
Spell Check for custom emails
When I type a custom email to a patron from within the client, I'd like spell check.
21 votes -
Allow changes to be saved to tables other than the Transactions table via server addons.
SaveDataSource only works for changes to the Transactions table currently, but it would be great if it could save changes to other tables. Or extend the functionality to the Users table at the very least.
1 vote -
I'd like to have the power to make mass changes such as changing Department Names.
example: Our Political Science department changed their name. I want to be able to make this change to all the existing patrons it would apply to.
20 votes -
Allow API to Add, Remove, and Update records in the UserValidation table
Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.
8 votes -
Improve retrieval of Alma holdings when there are multiple volumes.
ALMA doesn't have holdings for each volume when there are multiple volumes, so in z39.50 only the most recent volume is pulled up in the search. Is there a way for ILLiad to handle this better? If not within z39.50, then via an addon maybe? (This is from ticket 8080)
13 votes -
One Button to Turn Off ILLiad authentication
We no longer use ILLiad authentication. We have been using our University authentication system for years. With the new update, all of our old user accounts that still have ILLiad Authentication checked were locked out. Please create a way to change the authentication method for all of our users at once.
1 vote -
Remove Patron Name Field in OCLC request
When you submit a request through OCLC there is a field in Borrowing Information for the patron name. We have been deleting the patron name from this field for some time because we've found that it is sent to the lending library. If the library has a newer version of ILLiad, the patron name isn't sent, but if the lending library is on another system, it is. Removing this field would be an easy fix for patron privacy.
8 votes -
Move ILLiad to cloud
It'd be great to replicate the great ILLiad on the web so that staff can work remotely.
10 votes -
ILLiad stub accounts made when users fail to complete the registration process should be assigned to an NVTGC in use.
When an ILLiad stub account gets made due to incomplete registration it should not be assigned to a site not in use like "ILL." Allow users to configure what site/NVTGC those stub accounts should be assigned to.
8 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 -
Search for Update Stacks Searching and Check-In from Lending Library
Change the search option in the ribbons for Update Stacks Search and Check In from Lending Library to be on search field that searches both TN and ILL Number, similar to search option on the Check In from patron form.
3 votes -
Default setting for Accept non-English Set on User Record
Add a setting to the user records that would apply their selection of Accept Non-English field as the default on all requests from that user
via Site Visit with WVU
2 votes -
Proxy User Functionality
We have teaching assistants/administrative assistants/research assistants who are asked to request materials on behalf of an other ILLiad user. It would be helpful if a proxy account could be created for these assistants to create the request, but for the primary user to be responsible for the item (loan) and notified of delivery (article).
10 votes
- Don't see your idea?