ILLiad Ideas
455 results found
-
Have Lender Select box consider Odyssey and email addresses too
Atlas support said recently that only the shipping and billing address fields are checked for incoming ILL requests. Libraries often change their contact info. and it would be best if the system is checking for that too in order to avoid outdated Lender records in the Client and misdeliveries
10 votes -
Ability to add tags to Default Notes field of Cancellation Reasons.
Cancellation Reasons have associated Default Notes fields. It would be great if tags could be inserted into the Notes fields to auto-fill information.
Example:
Cancellation Reason: We could not fill your request by your deadline.
Default Note:
You indicated you did not need this item after <#Transaction.NotWantedAfter>. If you would still like to received this item, please ....6 votes -
question
Provide an internal to ILLiad customer question function. Instead of us having to use an email, etc., incorporate functionality into ILLiad for customers to contact us regarding the request and for us to answer and have it all recorded within the transaction.
16 votes -
Add semicolon as option for separating multiple email addresses
When sending emails to multiple recipients, ILLiad functionality should be expanded to allow both commas and semicolons, as semicolons are the known character for the function with other email programs/ API.
7 votes -
Ability to utilize IFM via Billing Manager for Lost Book/other charges
Paying/Billing for lost or damaged items is complicated! It would be great if we could utilize the power of IFM to bill one another instead. Also, we would know that the money is going right back into ILL services!
8 votes -
Eliminate the requirement for Microsoft Word.
Requiring Microsoft Word to print is problematic with Microsoft 365 because it requires users to authenticate and retains the connection to the user's account. Machines used with a generic account cannot have Microsoft 365 applications installed to protect users from each other. Thus these machines can't be used to print from ILLiad.
There is another proposal to add integration with Google, but that is also limiting. What happens when the next suite comes along?
Better, would be if ILLiad integrated the necessary components of LibreOffice (an open source alternative). Then ILLiad could print without any dependencies on third-party software. It…
8 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.
5 votes -
Add another note type
We like to hide our staff notes (via customization manager), but it would be nice to have another option for adding notes viewable to the user. Perhaps a Staff-hidden and Staff - so we could hide some notes but make others visible to the user in their account/request.
17 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.
4 votes -
Increase the DOI field character limit to 100 characters
The current 50 character limit for DOIs is not long enough and many get cut off. Please double the character limit to 100. Example: https://doi.org/10.1093/acrefore/9780190236557.013.20
22 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.
2 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.
11 votes -
Support for Controlled Digital Lending Software and Workflows
Ability to identify requests that will use the lend-like print method using an owned-to-loan ratio, manage due dates, etc. Details on CDL can be found here: https://controlleddigitallending.org/.
20 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.
2 votes -
ReShare Addon create a more robust breadcrumb trail
When the ILLiad ReShare addon creates a request in ReShare, there isn't much in the way of tracking after the request is submitted. We suggest adding notes to the ILLiad TN anytime the addon takes action on the request so there is a static history of what actions the addon has taken. That way if the request enters a different fulfillment method, such as OCLC, then there is preservation of the past ReShare request number and any other actions that the addon has taken. Otherwise, this information is lost (the ReShare Request ID is overwritten in the ILL number field).
2 votes -
Clear OCLC search filters when a request is closed
When searching for harder to find items in OCLC through ILLiad, we often use the custom search or set filters in the Limits box. The search terms and filters stick from request to request. The worst problem is that if I filter by year, this doesn't appear obviously in the limits, but when I search the next request by ISSN/ISBN nothing comes up. I have to remember to open Limits and clear the year from the filter.
It would be so helpful if these fields would just reset with every request. There isn't any case where I want the same…
1 vote -
Add User Expiration Date as an option for Customized Layout in 1-borrowing form, and 2-Check In From Lending Library batch screen.
We'd like to be able to see the User Expiration Date in the client on the borrowing request form and the borrowing batch process "Check In From Lending Library." This would help us when assigning due dates and renewals (in case we need to truncate what the lending library offered), and may also determine where we send initial requests as well. At the moment, User Expiration Date is not in the list of fields to choose from when customizing layouts.
1 vote -
Integrate API keys for Docline
NLM rate limits Docline searches to 3 per second without an API key. It is rare, but under the right circumstances, the client can exceed this, in which case using the API would be beneficial.
1 vote -
Highlight active requests that you've worked on but need to follow up on
An option to highlight requests in a queue so if you've opened it, you know you've already worked on it or need to follow up on it later. Ability to assign different colors based on your labeling preferences.
23 votes -
Replace Lending Web Shipped Items Due Date field in new pages
The Lending Web pages don't contain due date information in the tables, despite the documentation saying it should be a default table field and it historically being displayed in the pages.
1 vote
- Don't see your idea?