ILLiad Ideas
515 results found
-
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.
19 votes -
Button to route to Partial/Incorrect queue in Odyssey window
It would be great to have a button to route requests to the Received Partial/Incorrect queue, in the Electronic Delivery window that appears as part of Awaiting Odyssey Processing. Currently, one must delete the Odyssey file then manually route the request to that queue when the situation applies
3 votes -
IPv6 Support
As the EPA eyes moving to IPv6, we have concerns about our ability to connect to the OCLC-hosted server, as well as concerns about compatibility with Odyssey, Rapid, etc.
1 vote -
Improve Error handling in Electronic Delivery Utility (EDU) to keep cascading errors from occurring.
When the EDU loses connection to a network location where files are stored due to a timeout or issue, the EDU continues to try and process causing a loop of error messages that cause the EDU to crash. See ticket# 38285 on 3/14 screenshots for error. Please enhance to report the loss of the connection and stop the EDU from continuing. Matt did not think we could re-establish the connection so I don't know if restarting the EDU is an option but Matt added
"we could maybe better handle the errors when it can't make open files and stop trying…
3 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 -
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.
22 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
31 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.
1 vote -
Support for WMS WorldShare Management Services Z39.50
OCLC's WMS system credentials can exceed ILLiad's current username/password field lengths. Field sizes need to be expanded to support OCLC authentication for WMS Z39.50.
2 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…
9 votes -
Prevent borrowing renewal requests when the lending library will not accept them
As a lender, FSU does not accept renewals and this is indicated in our notes, in the Client when we mark a request as Shipped and in the Policies Directory. In WSILL, the Renew option disappears when a borrower has exhausted renewal requests. There is no equivalent in ILLiad and borrowers can continue to send renewal requests regardless of settings and indicated preferences. Borrowers should not be able to request renewals when lenders have indicated they will not be accepted. (via KAK)
5 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 -
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…
2 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/.
26 votes -
Update Lender Billing Fields and Description on Transaction Form
Adjust the availability of lender address fields in the transaction form.
Remove Billing Notes from the Transaction view in the Client. Dev believes this is an artifact from before lending billing was split into 2 parts and we have been unable to populate it with data.
Add LibBillingMethod as an option for addition to the layout. It's available in the LenderAddress record view, but not the transaction form view.
Rename the "Billing Groups" label in the Transaction form's Library tab. These are just groups and should not be described as specifically related to billing.
1 vote -
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).
3 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 -
SAML multiple attributes (allow for multiple and to list those which are allowed)
We have come to understand that ILLiad's SAML module does not support SAML2 attributes sent by the Identity Provider with multiple values. These would take the basic form in the SAML assertion XML like:
<saml:Attribute Name="multiAttributeName">
<saml:AttributeValue>Value 1/saml:AttributeValue
<saml:AttributeValue>Value 2/saml:AttributeValue
<saml:AttributeValue>Value 3/saml:AttributeValue
/saml:AttributeIt is described on pg 31 of the spec https://www.oasis-open.org/committees/download.php/56776/sstc-saml-core-errata-2.0-wd-07.pdf#page=31
As this is a common method of delivering data structures inside of SAML attributes especially when specifying items like user affiliations or group memberships, we request that support be added in the future to read and operate on multi-value/list attributes within the RemoteAuthValidation table.
2 votes -
Fulfillment Data should be included in Custom Search results
Custom searching for transactions doesn't return information from the FulfillmentData table. We need to be able to calculate money spent through DSP addons like Reprints and Get It Now and there isn't any other way to gather that information out of ILLiad, other than using an ODBC link and an external program.
2 votes -
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
- Don't see your idea?