ILLiad Ideas
536 results found
-
Sites should be limited to view Web Alerts to only those created by their staff For sites within a consortium, it would be a good idea to limit sites to view Web Alerts only to those created by their staff i.e. limit to view those created by their NVTGC.
The delete option also should be restricted to the Web Alerts created by their own staff/NVTGC. Otherwise their is danger of the wrong alert (Alert of another institution) inadvertently getting deleted.2 votes -
5 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 -
Keep user on Main Menu Page after renewing an item If a user is on the Main Menu page and wants to renew a checked out item, clicking on the renew button directs the user to the transaction details. Instead, allow the user to remain on the Main Menu and display the success error so the patron doesn't have to navigate back to the main page.
7 votes -
Allow tracking of multiple renewals for one request through ILLiad Currently ILLiad will only track the first renewal for a request. However, many lending libraries allow for multiple renewals, and with current closures this is happening more frequently. It would be helpful to have ILLiad route and track renewals for requests beyond the first one so that the due date in borrowing requests match what the lender has determined.
39 votes -
Use regexp to parse values for OpenURLMapping This would allow staff users to specify certain pieces of a parsed values in OpenURL to be imported into the ILLiad record with a clean data format.
3 votes -
3 votes
-
4 votes
-
7 votes
-
3 votes
-
Allow Address number field change When a new lender address is created, an address number is automatically assigned and that number cannot be changed. Please allow that field to be edited in case we want to re-arrange the order of our addresses. Some addresses are used a lot more often and we want that to be 1 or 2 but cannot right now. Thank you.
12 votes -
Refine Transaction Permissions for Borrowing Write in ILLiad Staff Manager Currently in ILLiad Staff Manager, under Transaction Permissions, if a staff is granted Borrowing Write permission, that person will be able to access, modify, process and impact all Borrowing TNs. We would like to be able to limit staff to Check In From Lending Library and Print Receives functions only, and deny the staff the ability to modify TNs in Awaiting Request Processing queue and other more "sensitive" queues.
2 votes -
ILLiad does not pull all data from Docline when an ISBN for a book is provided For example, the field will be "978-0". This leaves staff without entire citation and have to go back to Docline to retrieve it. It would be great if this were fixed
3 votes -
2 votes
-
3 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.
3 votes -
Make sure all accounts that log in with past Expiration Dates must go through the Expired Users page and update their information Users with old expired stub accounts are not prompted to update their information when logging into their ILLiad accounts again. The account status goes from Cleared=NEW to Cleared=NO, and ExpirationDate isn't checked/updated because the account was technically already created.
We need ILLiad to check whether an account is expired or overwriting an existing expiration date. Having a patron from 2012 able to submit requests without updating their contact information or preferences is a real problem for us -- patrons can and do change their email addresses, and we allow patrons to choose to have loans delivered to their home if…
2 votes -
Allow conditionals based on OpenURL fields We would like to be able to add a function to the OpenURL configs such that we can take a value and interpret an ILLiad value from it.
For instance, as rft.lib=UNIV needs to translate to LendingString=EMU.
We had scripts for this before, but we're migrating to OpenURLs and APIs, so this enhancement would be very appreciated.
1 vote -
Option to "Undo Conditional" We would love to have an option to "Undo Conditional" for those times when we realize too late that a conditional was unnecessary. This would be helpful if, for example, we send a "Non-circulating" conditional before realizing the request is for an article, or conditionalize for "Not as cited," then we find the citation. There are any number of situations where we may miss information in a request and send a conditional, then realize it was unnecessary. Even if this is only possible until the Connection Manager runs, it would be a very useful feature. Thanks!
3 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
- Don't see your idea?