Skip to content

ILLiad Known Issues

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

93 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)

    We’ll send you updates on this idea

  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)

    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)

    We’ll send you updates on this idea

  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)

    We’ll send you updates on this idea

  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)

    We’ll send you updates on this idea

  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)

    We’ll send you updates on this idea

  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)

    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)

    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)

    We’ll send you updates on this idea

  10. Certain fields marked as required in WebValidation table are not labeled as required in default web pages

    The following fields are marked as required by default in the WebValidation table, but are not marked as required in the default web pages on certain forms:

    -The PhotoJournalInclusivePages field is missing a required label on the LendingGenericRequestArticle and EditLendingGenericRequestArticle forms

    -The Department field is missing a required label on the NewUserRegistration and NewAuthRegistration forms

    Bug# 17645

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  11. Default search results text does not meet color contrast requirements

    The default color of the text used for the "No search results" message displayed when no search results are found does not meet color contrast requirements with the default background color of the web page.

    Bug# 17644

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  12. Focus indicators for interactive controls do not meet contrast requirements

    The focus indicator for several interactive controls in the default web pages (e.g., input fields, buttons, etc) does not meet the minimum contrast required by WCAG.

    Bug# 17641

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  13. Keyboard controls cannot be used to dismiss cookie notification popup

    Keyboard controls cannot be used to dismiss the cookie notification popup in certain web browsers.

    Bug# 16534

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  14. Incorrect anchor tags on include_notification_preferences.html may cause accessibility issues

    The "All" and "None" input buttons inside the includenotificationpreferences.html file are nested within <a> anchor tags, which is unnecessary since both elements are interactive by default and may cause these buttons to be flagged by accessibility validators.

    Bug# 16533

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  15. Web pages may not allow zooming in and out on some mobile devices

    The <meta> tag that is included on the include_head.html and LendingLogon.html files may prevent users from zooming in and out on the ILLiad web pages on some mobile devices.

    Bug# 16529

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  16. Empty heading elements are possible in datarow templates

    If a transaction doesn't have value in the Title field, Author field, or any other field encased in a heading element (h4,h5, etc) on a datarow template, then the heading will appear empty in the web pages and cause confusion for screen reader users.

    Bug# 14456

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  17. The colors set for small notes, required text, and <p> tags in the default CSS do not meet color contrast requirements

    The colors set in the default CSS for "small-notes," "req," and <p> tags do not meet the WCAG AA accessibility requirements for color contrast.

    Bug# 14424

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  18. The role="heading" attribute on top level <div> containers may cause issues for screen readers

    The role="heading" attribute on the <div> containers surrounding most web pages can cause strange behavior with screen readers depending on the content of the file.

    Bug# 13849

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  19. Radio button controls on ViewSearchResults.html are improperly formatted

    The width: 100% property in the default CSS for label elements results in improper formatting/alignment for the radio buttons on ViewSearchResults.html.

    Bug# 13557

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
  20. The CreateUser endpoint in the Web Platform does not support delivery locations for new users.

    The CreateUser endpoint in the Web Platform does not support using a valid delivery location for a new user's NVTGC field.

    Bug# 13156

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Feedback and Knowledge Base