ILLiad 9.1 Release Notes

Fixed an issue where resent Odyssey documents are not overwriting previously delivered PDFs. This issue occurs when a specified coversheet filename doesn't exist and a delivered PDF already exists, the updated PDF document will not overwrite the initially sent document in delivered PDFs. Bug# 9673

Fixed several minor issues:

• Multiple class attributes have been merged in the datarow template pages.
• Ampersands have been encoded on several pages.
• Nonbreaking spaces have been removed on several pages.

Fixed an issue that was preventing the "Import All" button from importing requests.

Fixed an issue that was preventing the Lending Updating form from updating requests.

When submitting a borrowing request for an open-access article or an article that appears to be a duplicate request, ILLiad will now pause on the warning message that DOCLINE displays during the automated Search and Fill and Search and Send processes so that the user can see the warning and make changes to the request before sending.

Fixed an issue that was preventing the "Manual Request" feature from working properly.

Fixed an issue where the DOCLINE ID/Lender was not imported into the ILLiad request form when using the "Manual Request" feature.

Released the ILLiad ReShare Addon that integrates ILLiad with the ReShare service to help automate request fulfillment. This addon can be configured and used as a regular Server Addon or as a Decision Support Pipeline Addon. For complete details, including configuration information and the download link, please see ILLiad ReShare Server Addon.

Added a blank custom.js page to the default web pages for site-specific custom JavaScript changes and a blank custom.css page to the default web pages for site-specific custom CSS changes. 

Two changes were made to all relevant default web pages in order to meet accessibility requirements:

• Added the "required" attribute to all default required fields that will function in addition to the pre-existing '<span class="req">(required)</span>' tag on these fields to indicate that they are required.

  Adding the "required" attribute will also add some additional browser validation to your web forms. To learn more about these changes and to find information on an alternative "aria-required" attribute that you can implement instead to meet accessibility requirements, see Required Field Validation Options for Web Forms.
• Added the "formnovalidate" attribute to all Cancel buttons.

Removed the "new-line" CSS class from the default CSS and replaced all <span> elements using the "new-line" class attribute with <div> elements. 

Added value attributes to all hardcoded dropdown options (those defined explicitly in the HTML rather than in the CustomDropDown Table) to ensure that ILLiad will remember the user's selection when editing a request or redoing a field after a failed validation.

Removed non-breaking spaces on the lendingWebAlerts.js and webAlerts.js files and added the "mr-1" class to both these files and the DataRow template files to provide a better format for spacing. 

Updated ThesisRequest.html and EditThesisRequest.html to use the Article fields instead of Loan fields to collect request information in order to fix an issue where Thesis requests were submitted with the Article request type but would populate Loan Info fields in the ILLiad Client. Additionally, an incorrect "required" tag was removed from the Author/Editors field and the 'required' attribute was added to the Title field. Bug# 7323

Fixed an issue where clicking the Cancel button on NewAuthRegistration.html would send an unregistered user back to the same page instead of exiting the ILLiad system. The Cancel button will now send the user to the location specified in the RemoteAuthWebLogoutURL customization key. Bug# 12648

Changed duplicate class attributes on the include_TransactionMenu.html Borrowing and Lending pages to use only one class attribute according to optimal HTML practice. Bug# 10147

Replaced style tags used on several default ILLiad web pages with Bootstrap CSS classes to follow best coding practices and removed an unnecessary style tag on include_notification_preferences.html.

Changed the Update Docline Requests button on the Lending Ribbon to point to the updated URL for Docline Lending Updating. 

Updated ILLiad to use the new Copyright Clearance Center (CCC) web service in order to keep integration with this service functional. The changes made by the CCC to the APIs used in its new web service have required several changes to the CCC configuration settings in the ILLiad Customization Manager and to the copyright search and ordering process and controls in the ILLiad Client.

The following configuration settings have changed in the ILLiad Customization Manager:

• If not already configured, the CCCUsername and CCCPassword customization keys (located under Borrowing | Copyright) will need to contain valid CCC account information for your institution. 
• All CCC orders must now include a billing address, which is drawn from the BillingAddress fields for each ILLiad site configured in the Customization Manager's LocalInfo table. Please ensure that these fields are filled out and that they match the billing address on your CCC Marketplace account.

• If your institution operates in multiple countries, your institutional CCC account may contain multiple Location IDs that will now need to be configured in the ILLiad Customization Manager. Please see the ILLiad Copyright Processing Changes After the CCC Web Service Update article for more information.

  If your institution only operates in a single country, you will not need to configure additional location information after the update

The following changes were made to the copyright search and ordering process in the ILLiad Client:

• Searching now requires valid CCC account credentials to be configured in the ILLiad Customization Manager (i.e., searches cannot be performed anonymously). If your CCC credentials are invalid, you will see an error message stating "Error communicating with CCC." upon attempting a copyright search.
• Removed the option to search by Publisher or by multiple parameters at once from the Copyright search interface.
• Searching will now only return one rightsholder for the item selected automatically by the CCC based on the publication year.
• Items for which it is not possible to determine permissions or copyright costs or for which a special order is required will no longer be returned in search results.
• The Granted status previously returned in Right field for search results has been changed to Licensing Available. 
• Copyright orders containing multiple transactions will no longer be grouped under a single invoice number contained in the Order Header field when submitted. Each transaction will only be assigned a unique Order Detail number when the copyright order is placed and these transactions will be grouped into separate invoices by the CCC for payment based on a frequency setting configured on your CCC account. Please see Copyright Order Handling Changes for more information.
• Removed the Order Status dropdown button and the Cancel Order button from the Borrowing Request form.

• Added new Copyright Order and Order Placed fields on the Borrowing Request form and changed the label of the CCC Number number field to CCC Publication ID for additional clarity.

  If you are using a customized layout in the Client, then you will have to rename the CCC Number field and add the Copyright Order and Order Placed fields manually to the Borrowing Request form using the layout customization feature. For more details, see the "Enabling the new fields" section of the related documentation.

Updated the ISO Service to patch a potential security vulnerability found in the log4j component. 

Updated the ISO Service's log4j component to the latest version (v2.16). 

Fixed an issue where institutions whose SQL servers use both named instances and nonstandard ports would experience connection issues to the database after upgrading their ISO Service.

Updated the ISO Service's log4j component to the latest version (v2.17.1). 

Fixed various accessibility issues on the web pages, particularly those affecting the experience of screen reader users. The list of changes can be found below. For more information on implementing each fix, see Implementing 9.1 Web Page Changes. 

• Added missing header classes to the default CSS and increased the color contrast for several text classes and HTML elements Bug# 14424
• Added a <main> container to surround and indicate the main content for screen readers within most web pages
• Removed the role="heading" attribute from top-level <div> containers and several inner <div> containers to prevent screen reader issues Bug# 13849
• Removed extra closing </div> tags on several pages Bug# 6022
• Reordered the heading elements on web pages (where necessary) so that they are presented sequentially (e.g., h2, h3, h4, etc.) and without skipping levels 
• Changed several heading elements on DataRow template files that were surrounding non-heading content to use <div> containers instead Bug# 14456
• Changed the <div> element used in the include_header.html files to a <header> element in order to provide a header landmark for screen readers
• Corrected an error within the Title field's <label> element on StandardsDocumentRequest.html and EditStandardsDocumentRequest.html
• Updated the copyright year on several web pages to the current year (2022)
• Added a WebPagVersion.txt file to the default web pages indicating the web page version information
• Added web page version information to the include_head.html files

Fixed various accessibility issues on the web pages, particularly those affecting the experience of screen reader users. The list of changes can be found below. For more information on implementing each fix, see Implementing 9.1 Web Page Changes. 

• Added labels to the checkboxes and buttons used to select notification preferences on include_notification_preferences.html to improve navigation of this process for screen reader users.
• Fixed an issue where the Skip to Main Content link would remain invisible when focused on using the keyboard.
• Added missing Skip to Main Content link to the LendingFirstTime.html page
• Changed banners on several web pages to use <header> elements in order to improve the browsing experience for screen readers and to standardize the styling and format for banners across all ILLiad web pages.

Updated the AtlasPDF tool used by the Odyssey Manager to v1.1.3. This version updates the log4net component used by the tool to v2.0.14 in order to match the version used in other ILLiad components.

Fixed an issue where the lender string was not imported to ILLiad borrowing requests created from DOCLINE.

Updated the signing certificate used by the application to fix an issue that prevented the SQL Alias Manager from opening.

Fixed an issue where DOCLINE lending requests would not import into ILLiad.

Changed the default mail merge method used by the ILLiad Client to fix an issue where attempting to print after updating to Microsoft Word version 2211 or above could potentially return an error stating "The OpenDataSource method or property is not available because a macro is currently running."

Updated the ILLiad Client Installer to include the latest version of the SQL Alias Manager (v1.3.3) with the updated signing certificate.

The following new configuration options are available for the ILLiad web interface to prevent bot-driven spam account creation via the New User Registration forms (NewUserRegistration.html and LendingNewUserRegistration.html):

• ILLiad can now integrate with one of three supported third-party captcha providers to add a captcha challenge requirement to the New User Registration form (NewUserRegistration.html). The captcha challenge will provide extra security against bot-driven account creation by requiring new users to solve the challenge in order to submit the form and create their accounts. The following captcha providers and plans are supported by ILLiad (note that a separate account must be created with your chosen captcha provider to implement this feature): 

  • Google reCAPTCHA: reCAPTCHA v2 (both the "invisible" and "checkbox" variants) and reCAPTCHA v3
    • Note that reCAPTCHA Enterprise is not supported by ILLiad
  • hCaptcha: Free "Publisher" plan
  • MTCaptcha: Free plan
• As an alternative to implementing the captcha requirement, user registration can now be completely disabled for accounts created through basic ILLiad authentication (ILLiadAuth) from the New User Registration forms (NewUserRegistration.html and LendingNewUserRegistration.html) using the new ILLiadAuthUserRegistrationEnabled customization key. This option will prevent the creation of spam accounts by completely blocking account creation for users who are not pre-authorized for an ILLiad account via an ILLiad Exclusive, LDAP, PatronAPI, SymphonyAPI, or Remote Authentication configuration. This option should not be chosen if you only allow users to register for accounts through the basic ILLiad account creation and authentication process.

Added the following new customization keys to the ILLiad Customization Manager to support the new bot-driven spam account prevention options:

• ILLiadAuthUserRegistrationEnabled: Determines if new user registrations can be created via basic ILLiad authentication (ILLiadAuth)
• SLUserRegistrationDisabled: The web status line that appears if registration has been disabled using the ILLiadAuthUserRegistrationEnabled key
• CaptchaProvider, CaptchaSecret, CaptchaSiteID: These keys are used to configure the captcha integration for the user registration form
• SLCaptchaFailure: The web status line that appears if a user fails the CAPTCHA challenge during user registration.

Added the CAPTCHA web DLL tag to the ILLiad web interface. This tag is used to display the captcha challenge requirement on the New User Registration form (NewUserRegistration.html) and Lending New User Registration form (LendingNewUserRegistration.html) when a captcha integration has been configured in the ILLiad Customization Manager. 

Users will no longer be able to register for an ILLiad account from the TestWeb directory to prevent bot-driven spam account creation from the ILLiad TestWeb web pages. User registration will be disabled by default for the web pages in the TestWeb directory upon update and cannot be re-enabled.

Expanded the maximum length of the AuthUser and AuthPass fields in the ZServerConfig database table to 100 characters. These fields display as the Username and Password fields on Z39.50 server configuration form in the ILLiad Customization Manager.

Fixed a security vulnerability present in the ILLiad Connection Manager.

Modified NewUserRegistration.html to include the new <CAPTCHA> tag and added the following new files to the default web pages to implement captcha support on the New User Registration form:

• include_captcha_none.html
• include_hcaptcha.html
• include_mtcaptcha.html
• include_recaptcha_v2_checkbox.html
• include_recaptcha_v2_invisible.html
• include_recaptcha_v3.html