ILLiad 8.6 Release Notes

Fixed an issue that was preventing the scripting system from overwriting addons with an updated version if the addon files on the client machine had the read-only attribute set.

The UserValidationType column has been added to the UserValidation table. Two values can be used in UserValidationType: Auth (default) or Load.

• Auth indicates that the User record will be used to authenticate a user. If a user successfully authenticates and their User record does not already exist, a User record will be created with information from the UserValidation data.
• Load is only applicable when using a WebAuthType of LDAP or when RemoteAuthSupport is enabled. If so, the default WebAuthType will be used and the UserValidation data is only used to populate a newly created User record after a user successfully authenticates.

When using PatronAPI Exclusive authentication, users who do not have an ILLiad auth type can now successfully authenticate even though they don't exist in the PatronAPI system.

Fixed a problem that allowed users from a different parent NVTGC to log in using a different shared server site's web pages and a different web auth type.

Fixed an issue that prevented users assigned to a specific delivery location to be redirected to the proper login page if they were using the wrong shared server site's login page.

The following fields have been added to the database:

• The UserRequestLimit, UserInfo1, UserInfo2, UserInfo3, UserInfo4, and UserInfo5 fields were added to the UserValidation table.
• The UserValidationType value was added to the UserValidation table.

The CitedIn, CitedTitle, CitedDate, CitedVolume, and CitedPages fields have all been updated to allow nvarchar(max) values, expanding the previous 40 character limit.

The Electronic Delivery Utility will now send additional request information (when available) in Odyssey Parameters so that Odyssey Standalone users can better identify documents.

• ILLNumber → atlas.odyssey.ill
• Patron → atlas.patron.name
• PhotoJournalTitle → atlas.citation.journal.title
• PhotoArticleTitle → atlas.citation.article.title
• PhotoArticleAuthor → atlas.citation.article.author
• PhotoJournalVolume → atlas.citation.journal.volume
• PhotoJournalIssue → atlas.citation.journal.issue
• PhotoJournalMonth → atlas.citation.journal.month
• PhotoJournalYear → atlas.citation.journal.year
• PhotoJournalInclusivePages → atlas.citation.journal.pages

The following fields are now available to be used as tags in the Email templates:

• <#Special.UserDisavowalReason>
• <#Special.PasswordResetLink>
• <#Special.CancellationNote>
• <#LenderAddress.LibraryNotes>
• <#MergeFrom.Username>
• <#MergeTo.Username>
• <#Transaction.Notes>
• <#Transaction.LastNote>
• <#Staff.Username>

The Cancellation email templates have been split based on request type. The following templates now exist:

• Borrowing Cancellation Article and Borrowing Cancellation Loan
• Doc Del Cancellation Article and Doc Del Cancellation Loan
• Lending Cancellation Article and Lending Cancellation Loan

Fixed an issue that caused the Connection Manager to stop processing requests when there were requests awaiting Direct Request lenders that did not have an ILL number.

The library address printed on both Lending and Borrowing templates will now be pulled from the ShippingAddresses table (which contains OCLC constant data) instead of the LenderAddresses table. See Print Template Addresses for more information.

It is now possible to separate Billing Category based on request/document type, and the ArticleBillingCategory and LoanBillingCategory fields have been created.

• The BillingCategory tag will no longer display correctly in emails, and will need to be updated. This tag has been replaced by the ArticleBillingCategory and LoanBillingCategory fields.
• The Billing Manager will now display both the Article Billing Category and the Loan Billing Category when viewing an invoice. The Billing Category associated with the request will display as the BILLINGCAT merge field on the invoice template.
• The ILLiad client will no longer use the WebDefaultBillingCategory customization key to set the Billing Category for new users. The client will now use the values from the DefaultAccounts table to initialize the ArticleBillingCategory and LoanBillingCategory fields.
• The Patron Request Service will no longer use the WebDefaultBillingCategory customization key to set the Billing Category for new users. It will now use the values from the DefaultAccounts table to initialize the ArticleBillingCategory and LoanBillingCategory fields.
• The Billing Category displayed in the Electronic Delivery Utility is now based on the Billing Category associated with the specific request being processed.
• The Database Manager was updated to support patron searches and filtering by BillingCategory.
• The default Printable Columns that can be used for Users and Lender Addresses have been updated to remove BillingCategory and add ArticleBillingCategory and LoanBillingCategory.
• If the BillingCategory tag is being used as a Param tag, it will be pulled from the LoanBillingCategory field.
• If the BillingCategory field is used and populated on the NewAuth.html, NewUser.html, or ChangeUserInformation.html web pages, the value used will be used in both the ArticleBillingCategory and LoanBillingCateogry fields.

The Connection Manager will now validate each symbol in a lending string before sending to ensure they are all valid suppliers. If any symbol is not a supplier, it will be removed from the LendingString field on the OCLC request and be moved to the Locations field.

The ILLiad Connection Manager will now check Lending requests when mark as Shipped to see if the lending restrictions of Library Use Only or No Renewals have been selected. If they have, these restrictions will be marked automatically on the Borrowing request. Two new customization keys were added to support this functionality: UpdateLendingShippedLibraryUseOnly and UpdateLendingShippedNoRenewals.

When searching OCLC holdings, regional holdings now display in alphabetical order.

Fixed a problem when a Conditional No response was given that moved requests to Awaiting Unfilled Processing even when there were additional symbols in the lending string.

Fixed an issue that sent Lending charges to OCLC with four decimal places instead of two.

Fixed the dead link on the red question mark icon in the Staff Manager.

ILLiad 8.6 now uses the .NET 4.5.1 framework for both the ILLiad server and the ILLiad client. Your ILLiad server and all desktops that run the ILLiad client will need to update to .NET 4.5.1 framework. Your server and client machines may need to be restarted after installation to apply the changes. Because of these changes, Windows XP and older are no longer supported with ILLiad. See Hardware and Software Requirements for more information on supported versions. 

ILLiad now requires more complex passwords for patron accounts (using ILLiad authentication). Passwords must have at least eight characters with at least one lowercase letter, one uppercase letter, and one number. See Password Requirements for more information.

For Shared Server ILLiad sites, Web Validation will now use a parent NVTGC for lookups. Order of lookups for WebFormValidation:

1. User’s NVTGC - (User's exact NVTGC ignoring parent site)
2. Page NVTGC – (hidden HTML parameter for NVTGC)
3. Parent of User’s NVTGC - (Parent of User's exact NVTGC, will only be used if Shared Server Support is on)
4. Database NVTGC – The NVTGC that is being set based on the logon account

Fixed an issue that caused the tab order to be incorrect on the NewUserRegistration.html page.

Fixed three typos on the Web Reports Document Delivery main menu page: the "Most Filled Journals" and the "Elec Del Turnaround Time" heading links had a visible h3> following the words, and "withing" was used instead of "within" in the description for Most Filled Journals.

Users can now choose if they want to receive notifications specifically for electronic delivery items. These notifications are separate from loan notifications.

• All users will be automatically subscribed to electronic delivery notifications at first, but this can now be changed.
• A checkbox has been added to the User form to enable or disable notifications for electronic delivery.
• A checkbox can also be added to your web pages for patrons. See ILLiad 8.6 Web Page Changes for instructions on how to do this.
• The include_notification_preferences.html file has been updated to add this new functionality.

Fixed an issue that prevented saving changes made on a new User form after the first save.

The server addons now allow for a Resubmit Request option.

Changes have been made to better handle simultaneous calls to the ILLiad Web Platform, which will reduce notification failures. These changes should help address notification failures when:

• A request is flagged with the "Notification Failed" Odyssey error
• The electronic delivery notification is sent to the EmailNoAccountAddress

The Odyssey Manager will now retry sending a notification through the Web Platform if the first attempt failed. If the second attempt also fails after 5 seconds, the request will be marked with the "Notification Failed" Odyssey error status.