Skip to content

ILLiad Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

115 results found

  1. PDF Document Processor prevents PDF from being closed until the Client is closed - Error message 'file in use'

    When a PDF has been loaded by a PDF Document Processor (on the scanning form or the electronic delivery form), the filesystem keeps a lock on that file until the ILLiad client is closed. This is because the processor is not closing the file.

    Error Log Message Example: The process cannot access the file 'C:\Program Files (x86)\ILLiad\elecdel\o48034.pdf' because it is being used by another process.

    Bug# 8578

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Staff Client  ·  Admin →

  2. Docline Citation not importing volume/issue numbers.

    The volume/issue and pages blank are not being imported when there are non-numeric values in the Citation field such as supplemental issues and e-page numbers.

    Bug# 6539

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Docline  ·  Admin →

  3. Extra closing div tags in ILLiad 9.1 Default Web Pages

    The web pages with extra div tags include:

    EditArticleRequest
    EditBookChapterRequest
    EditConferencePaperRequest
    EditGenericRequestTesting

    Bug# 6022

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Admin →

  4. Change Password submission does not display status line for passwords successfully changed

    When staff force a password is forced reset from the client for a web user, pressing the submit button successfully changes the password, BUT it reloads the change password page with blank values and without a status message stating the password has been successfully changed.

    v9.1
    Bug# 4795

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Web Interface  ·  Admin →

  5. The Process Copyright batch process form does not allow processing of items in "Awaiting Copyright Processing - Pipeline"

    The batch Copyright Clearance processing form would check to see if the request was at the 'Awaiting Copyright Clearance' status to ensure the request wasn't being processed by someone else simultaneously. When checking for the status of the request, ILLiad should have considered the 'Awaiting Copyright Clearance - Pipeline' status to also be a valid status. Instead, this status was seen as invalid and would prevent latter requests from being processed.

    v9.0
    Bug# 4930

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Decision Support Pipeline  ·  Admin →

  6. Undo Shipped note and history activated due to case sensitivity

    This issue can be identified by the borrowing system error: "Received unexpected undo shipped message for transaction from [lender symbol]".

    The issue occurs if the current lender of the request (in OCLC) is the same that was stored on the request when it was shipped and checked in and, the value in OCLC is stored as lower case but the value in ILLiad is stored as uppercase. This causes the request to not match and prompt the undo shipped note.

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Staff Client  ·  Admin →

  7. Login as... error causes an error popup and sometimes crashes the client

    Workaround: Some sites have reported that changing to another skin and back to original skin allowed Login As to work again.

    The Client Error log may say the following: A thread exception has occurred.
    System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

    Bug#3980

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Staff Client  ·  Admin →

  8. Docline script error causes a blank Account Type box to appear on the Docline Importing tab

    External systems running on the user's machine such as McAfee AntiVirus can affect web traffic. Since Docline is running through the web, users may receive a script error upon login. If the user clicks No or closes the script error, they will receive a blank Account Type box.

    Bug# 4111
    v8.7.3 and Docline 6.0

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Docline  ·  Admin →

  9. Saving a ZSearch with no included servers causes an error

    When dragging the last server from the included listbox to the available servers listbox and then saving, an error will occur.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Customization Manager  ·  Admin →

  10. The EditPatentRequest.html file contains errors preventing proper submission of the form

    The EditPatentRequest.html file contains the following errors preventing proper submission of this form in the ILLiad web interface:

    1. References PatentRequest instead of EditPatentRequest in the ILLiadForm parameter
    2. Contains an incorrect name attribute value in the form element
    3. Missing the hidden input for TransactionNumber

    Bug# 25897

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  11. Lending web pages contain invalid FORMSTATE tags

    The ILLiad Lending Web DLL does not support the <#FORMSTATE> tag, however, this tag is included on LendingGenericRequestArticle.html, EditLendingGenericRequestArticle.html, and EditLendingGenericRequestLoan.html.

    Bug# 25896

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  12. The Profile dropdown is missing a visual separator between menu items in the Lending web pages

    The Profile dropdown in the navigation bar used by the Lending web pages is missing the visual line separator between the menu items in the dropdown and the “Logged in as <username>” information.

    Bug# 25894

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  13. Certain lending web pages do not reference the include_header.html file

    LendingLogon2.html and LendingFirstTime.html do not reference the include_header.html file and instead include a hardcoded header from an older version of the ILLiad web pages.

    Bug# 25879

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  14. ILLiad web forms contain incorrect use of fieldsets

    Many ILLiad web forms contain incorrect uses of fieldsets that will cause accessibility issues as their implementation is non-compliant with WCAG 1.3.1.

    Bug# 24252

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  15. URL generated by CCC Get It Now addon does not escape characters

    The URL generated by the CCC Get It Now addon isn't escaping characters and can fail, one example being if there is a hyphen in the startPage value.

    Bug# 21167

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Addons  ·  Admin →

  16. Tracking entries on the ILLiad web pages may display in the incorrect timezone

    Tracking entries for requests on the ILLiad web pages are not converted to the local timezone and may display at a different time than what is shown in the ILLiad Client.

    Bug# 20739

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  17. Label elements are incorrectly formatted on certain Lending web pages

    The label elements for the LibraryName and BorrowingDeptEmail fields are missing or improperly configured on the LendingNewUserRegistration.html and LendingUpdateAddressInformation.html default Lending web pages, which causes accessibility issues.

    Bug# 20405

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  18. SearchType toggle switch does not properly filter search results

    The SearchType toggle switch on the search web pages (ViewSearchResults.html and LendingViewSearchResults.html) that is unused and commented out in the HTML by default will not correctly filter search results to include active requests only if enabled.

    Bug# 19970

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  19. Small notes are not automatically read by screen readers for certain form fields

    Small notes used for certain form fields on the default web pages will not be read automatically by screen readers. This includes:
    -The Password1 field on NewPassword.html, ChangePassword.html, NewUserRegistration.html, LendingChangePassword.html, LendingNewPassword.html, LendingNewUserRegistration.html
    -The Username field on LendingNewUserRegistration.html

    Additionally, the CurrentPassword field on ChangePassword.html and LendingChangePassword.html contains an unlinked aria-describedby attribute that may be flagged by accessibility checkers.

    Bug# 19935

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  20. Transaction menu button text is not fully visible on certain display sizes

    The text content of the transaction menu buttons does not fully display on small screen sizes or high zoom levels and requires horizontal scrolling to view. In some cases, horizontal scrolling is not enough to read the full button text.

    Bug# 18918

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
← Previous 1 3 4 5 6

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)