ILLiad Ideas
529 results found
-
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.
25 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…
11 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.
2 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 -
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…
3 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
33 votes -
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 -
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 -
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/.
29 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 -
Exporting Customization Manager Tables Would like the ability to export tables from the customization manager into an excel xls, xlsx, or csv file so that changes can be made.
And then ideally allow the changed file to be uploaded into the customization manager to change the table too.
Tables like the Routing table would really be easier to manage and edit like this.
15 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.
3 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).
3 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 -
Ability to COPY and PASTE in User notes field This will allow us to copy and paste notes when we are merging accounts or when we need to copy and paste notes to multiple accounts (within families, etc.)
3 votes -
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.
26 votes -
I would liek ot be able to truncate text in field for printing. Sometimes the title is long and pushes my book strap on to a second page. I want to truncate the length of the title in some of my print templates so labels print consistently. I would also like to be able to change the color of the font based on the data in a merge field to call attention to a users NVTGC for example.
4 votes -
Allow RapidR borrowing renewals to be sent in batch by the Send OCLC Renewal Requests button Currently, the Send OCLC Renewal Requests button will send out renewals for all requests in the status of "Renewed by Customer to MM/DD/YYYY", but it only works on requests with a SystemID of OCLC. Now that RapidR allows renewals within ILLiad, it would be helpful to be able to batch send requests to Rapid using the same button, so that renewals can be sent out regardless of the System ID.
The query that populates the ESPUpdate table is currently:
"SELECT t.TransactionNumber, t.ILLNumber, t.SystemID FROM Transactions t JOIN Users u ON (t.Username = u.Username) " +
"WHERE ((t.TransactionStatus LIKE N'Renewed by…17 votes
- Don't see your idea?