ILLiad Ideas
536 results found
-
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 -
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…19 votes -
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 -
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 -
Increased Granularity in Web Circ Permissions by User I would like to be able to restrict available actions in Web Circ by user. I would like to restrict our circ desk account from being able to do anything other than check out items. I think essentially I'd like the customization keys to be available on a by-user basis.
3 votes -
Fix the "Illiad Authentication" Checkbox so it Does not Automatically Enable itself when Saving a New User Record Leaving the ILLiad Authentication checkbox unchecked/unchanged when creating a new user will default the user to ILLiad Authentication type.
Leaving the "ILLiad Authentication" checkbox unchecked/unchanged while creating a user in the Client still defaults to ILLiad Authentication when the user is created, even though the option is not checked when saving. This bug has been around for awhile with no fix in sight. Can this please be addressed in a future Illiad release? No one can remember to go back and uncheck that box constantly.This is currently logged as Bug# 12841
16 votes -
Make label position selectable for print processes We would like label templates to not generate placeholder text when there is no data and we would like to indicate on which label printing should begin.
1 vote -
Better tracking of OA/DSP/non-standard article delivery in Borrowing Web Reports Turnaround time Borrowing Web Reports don't have the ability to capture requests filled through OA Addon/DSP. It's important for not just these to be able to be captured and included in statistics, but also for us to separate these and be able to identify these as opposed to other material that's uploaded and delivered. (written by KAK)
3 votes -
Create a read-only/distributable form of dbc files or the SQL Alias Manager With SQL Alias Manager 1.3.2 staff with local admin privileges on their desktop or VM’s are no longer able to successfully Set Default (Local Machine) without also requiring Full Control privileges on the folder where the DBC’s reside.
In a shared environment this is an issue because we wouldn't want everyone to have full read/write access to a shared folder where someone could potentially change a dbc file for every staff member. This wasn't an issue with SAM v1.2.2.
4 votes -
9.1 replacement for Expires table tag to display pdf expiration date The old web pages displayed an 'Expires' date on the table of electronically delivered articles. This let users know how long they had before they would have before the PDF disappeared.
There is no way to include this in the new 9.1 web pages since table tags are no longer supported. It would be great to have something to replace this, using DaysBeforeElectronicDeliveryCleanup and the transaction's tracking entries to determine when it was first Delivered to Web to calculate the expiration date.20 votes -
Enable exclusion of subdomain for integrated SAML - fix broken Logon as User functionality Updating to the new integrated SAML prevents staff from utilizing the Logon as User button in the Client without redesigning the web directories.
The key that had been put in place to assist with circumventing proxy folder redirects - StaffProxyWebURL - will not work for integrated SAML sites when it its value is pointed to subdomains, the way it could with EZProxy.
Locally-hosted Shibboleth sites can set requireSession = false to support the Logon to User feature and LDAP and ILLiad Exclusive sites can use the feature without additional adjustments.
This means that sites who implement the integrated SAML are…
4 votes -
1 vote
-
Transfer User Notes when merging users When an existing user account is merged with an new one, in addition to moving the open requests, we would like any User Notes to be moved as well. We use these notes to track various issues with patron accounts and right now staff are manually copying each note.
17 votes -
Improve functionality of the patron's search results webpage We would like to see improvements to the ILLiad search results webpage. These improvements would benefit all users, but particularly those users with a large number of requests or lengthy user history. Some suggestions provide by users:
A method to reorder results in ascending and descending order.
A method to limit/filter results by various values, such as Document Type.
A method to limit/filter results by date received and/or date finished.
A method to sort requests alphabetically, such as by title or author.Thanks!
4 votes -
Disable "end request routing" I was wondering about the DOCLINE caveat that states a request canceled due to "Cost Exceeds Limit" would "end request routing.”
Is there some way to disable this? I have had to cancel requests that would've cost more than the patron was willing/able to pay, but I hate to think their search would end with us because of that.2 votes -
Prevent the submission of auto-truncated data in request forms Summary by KAK: There isn't anything to indicate to users that their submissions will be truncated when they enter too many characters in request form fields. We've created a workaround by using the WebValidation table for PhotoJournalInclusivePages with a validation of ^$|^.{0,30}$ to represent the field is not required and may only be submitted when its character count is less than 30.
11 votes
- Don't see your idea?