ILLiad Known Issues
143 results found
-
Routing rule errors may be misleading in the logs Routing rules errors are logged as "Invalid match string" errors even when the error is not caused by an issue with the match string.
Bug# 26555
1 vote -
Docline Lending Request Import excludes certain formatted data 'Pages' and 'Issue' values are not properly imported from the 'Citation' section of incoming Docline lending requests if these values are not formatted in a specific way. The page range for the 'Pages' value must be formatted with a hyphen (e.g., 123-126) and the 'Issue' value must be formatted as a single numeric value to properly import.
Bug# 27806
1 vote -
Lending shipping label printing will not apply sort settings Lending shipping labels will not be sorted by the sort settings configured in the Print Configurations form of the ILLiad Client when printed.
Bug# 25067
1 vote -
ILLiadAuthUserRegistrationEnabled customization key does not work if the WebAuthType key is not set to ILLiadAuth Setting the ILLiadAuthUserRegistrationEnabled customization key to No does not disable ILLiadAuth user registration unless the WebAuthType key is set to ILLiadAuth.
This means that if a site is using LDAP, they cannot prevent ILLiadAuth user accounts from being created by setting the ILLiadAuthUserRegistrationEnabled key to No.Workaround: Remove or rename the FirstTimeUsers.html page so that patrons cannot get there to click to get to the NewUserRegistration.html page. Optionally also rename/remove the NewUserRegistration.html page.
Bug# 25019
1 vote -
Copyright data can't be saved for requests in the Awaiting Copyright Clearance - Pipeline queue The "Save CCC Information" button can't be used to save copyright information for requests in the Awaiting Copyright Clearance - Pipeline queue.
Bug# 18914
0 votes -
Odyssey Manager creates blank pdfs Odyssey Manager fails to convert large TIF files of approximately 1 GB to PDF. The log does not indicate a problem but shows the process occurring in just a few seconds. The resulting PDF file is blank.
1 vote -
Unable to modify some ZServer configuration fields in Customization Manager for MARC records If a Z39.50 server configuration is set to use MARC holdings, the availability fields become read-only. If you need to edit the availability fields, please contact your support representative so they can edit directly in database for you. v8.7 and v9.0
1 vote -
Some unicode characters are not properly encoded on OpenURL submissions if the user must log in first. This seems to be a new issues introduced in ILLiad 8.7 when we switched to Delphi XE 8. To reproduce, submit an OpenURL request using the included URL both with and without a session. When you're already logged in, the cyrillic characters are rendered correctly in the author field and a ligature is used in the title. If you don't have an active session and are sent through the logon2 page, those fields will be rendered as ?s or boxes, indicating a problem with the form state encoding. I confirmed this URL worked correctly on ILLiad 8.6.x and earlier.
2 votes -
Request cloning from the staff client will always set the RequestType to Article Repro Steps
1. Open a loan request in the staff client
2. Clone the request. The behavior is the same regardless of cloning to same user or different user and if the request is/is not opened after the process is completed.4 votes -
Invalid characters in title error when submitted to OCLC Workform Mapping should be replacing invalid XML characters.
Currently workform mapping handles replacement of \r & \n.
Repro
1. Create a borrowing request in the client.
2. Via the database update an Article Title to include ""
3. Close the request form and re-open after the invalid characters are added.
4. Search OCLC and attempt to send the OCLC request.1 vote -
UTF-8 characters are not decoded properly in some cases For OpenURL requests, if the patron already has an active websession and do not have to log in the characters are correctly translated.
2 votes -
Request data may be lost when a request is submitted after the user's NVTGC is changed If a user's NVTGC is changed while the user is filling out a request on the ILLiad web pages, the request will still be submitted when the user clicks the Submit Request button, but the data the user entered into the request form will not be saved to the request.
Bug# 27212
0 votes -
Ampersand in username causes error in ILLiad web pages when viewing PDFs If a user has an ampersand (&) in their username, they are unable to view PDFs on the ILLiad web interface and receive the following error:
"Error: You may only view transactions that belong to you."
Bug# 27622
0 votes -
Default entry in WorkFormMapping table is missing closing ">" symbol The default entry in the WorkFormMapping table for WorkFormType "OCLC Article" and OCLCFieldName "volume" is missing the closing ">" symbol in the default value configured in the ILLiadFields column ("<#PhotoJournalVolume").
Bug# 27320
0 votes -
WebView2 dependency of ILLiad Client installer attempts to run even if WebView2 is already installed Attempting to install the ILLiad Client with Powershell and SCCM causes issues during the WebView2 installation even if WebView2 is already installed on the system before installing the ILLiad Client. This issue prevents the client installation from being completed.
Bug# 26820
0 votes -
The Atlas Authentication Portal is missing the log configuration file The Atlas Authentication Portal has support for logging, but is not currently distributed with the necessary App_Data folder and log.config file to enable logging.
Bug# 26220
0 votes -
Z39.50 may duplicate item records for holdings Z39.50 will pull in any hardcoded holding elements in the XML for a holding record, which can cause the first item listed in the record to be duplicated in ILLiad.
Bug# 25965
0 votes -
Submitting an OpenURL request as new RemoteAuth user can lead to a blank form submission In a Shared Server setup, requests submitted via OpenURL by new RemoteAuth users may be blank after the user creates their account and submits the request form.
Bug# 25395
0 votes -
Timestamps may be inconsistent for actions performed via the ILLiad web interface The date-times used on Transaction and other records to record timestamps for actions performed via the ILLiad web interface (e.g., updating Transaction Status) may be inconsistent in value when the server timezone differs from the database timezone.
Bug# 25157
0 votes -
Invalid routing rules cause error during custom routing When a request's transaction status is changed, ILLiad will loop through active routing rules and check for a rule matching the request's TransactionStatus and ProcessType, and then apply the rule when appropriate. However, if that routing rule is invalid because it has null fields (e.g., a null value for TransactionStatus, ProcessType, MatchString, NewTransactionStatus, or NewProcessType), an error will be logged and the routing process will fail.
ILLiad should instead check to ensure the routing rule is valid before applying the rule to the request and, if the rule is invalid, provide detailed information in the ILLiad Client log to state…
0 votes