ILLiad Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. EditPatentRequest.html contains incorrect error parameter for PhotoJournalTitle field

    The error parameter for the PhotoJournalTitle field on EditPatentRequest.html has an incorrect value of ERRORLoanAuthor in the ILLiad 9.1 web pages. The correct value for this parameter is ERRORPhotoJournalTitle.

    Bug# 14817

    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  ·  Flag idea as inappropriate…  ·  Admin →
  2. SLLogout status line doesn't display in 9.1 web pages

    The text configured in the SLLogout status line key will not display on the 9.1 web pages after the user logs out of ILLiad.

    Bug# 14798

    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  ·  Flag idea as inappropriate…  ·  Admin →
  3. Value persistence (persistedValue) does not work on Safari (WebKit) browsers

    Values will not persist properly when using Safari or any other WebKit-based browsers.

    Workaround: Add the following code to line 52 of atlasUtility.js within the block of code handling persistedValue:

    $(this).find("option[value='" + persistedValue + "']").prop("selected", true);

    Bug# 14597

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Requests are sometimes created with a NULL transaction status

    Requests in ILLiad may sometimes be created with a blank/NULL transaction status that can then cause issues with web reports, routing rules, and custom searches.

    Bug# 14436

    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  ·  Database  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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  ·  Flag idea as inappropriate…  ·  Admin →
  7. WebTNNotesFilter will not apply on Edit pages

    When a request is edited on the web, ILLiad will pull in the latest note regardless of the value in the WebTNNotesFilter key.

    Bug# 14374

    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  ·  Flag idea as inappropriate…  ·  Admin →
  8. The "Route Request to Review" action in the Automated Request Manager (ARM) causes unexpected behavior in ILLiad

    If the "Route Request to Review" action is selected in the configuration settings for the OCLC Automated Request Manager, this can lead to ILLiad unexpectedly closing the affected direct requests.

    Bug# 14342

    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  ·  OCLC  ·  Flag idea as inappropriate…  ·  Admin →
  9. Screenshots submitted through the Feedback form are corrupted when saved

    Screenshots submitted through the Feedback form of the Client will display correctly on the form but will be corrupted after the file is saved.

    Bug# 14332

    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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  10. Copyright web report exports incorrectly

    The Microsoft Excel file produced when exporting results from the Copyright web report populates the results from the Finished Requests table in all three sheets (Finished Requests, Outstanding Requests, and Completed Orders).

    Bug# 14244

    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  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Addons using Chromium may behave poorly on certain high-dpi setups.

    Addons using Chromium may encounter an issue that causes the visible portion of the browser window to temporarily shrink when scrolling if using a high-dpi monitor or a multi-monitor setup with different dpi settings between them.

    Bug# 13103

    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  ·  Addons  ·  Flag idea as inappropriate…  ·  Admin →
  15. Google Search v2.1 Addon Broken

    There is an issue causing version 2.1.0 of the Google Search addon to pull up a blank, white screen, and disable the addon's buttons.

    Bug# 13090

    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  ·  Addons  ·  Flag idea as inappropriate…  ·  Admin →
  16. PDFs appear distorted in Scanning window

    PDFs downloaded from a database sometimes display distorted with dark blobs in the Odyssey Manager Scanning window. The appearance of the PDF returns to normal upon delivery.

    ILLiad 9.1

    Bug# 12857

    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  ·  Odyssey Manager  ·  Flag idea as inappropriate…  ·  Admin →
  17. Leaving the ILLiad Authentication checkbox unchecked/unchanged when creating a new user will default the user to ILLiad Authentication type.

    Leaving the "ILLiad Authentication" checkbox unchecked/unchanged while creating a user in the Client still defaults to ILLiad Authentication when the user is created, even though the option is not checked when saving.

    Workaround: Check and uncheck the box before saving.

    Bug# 12841

    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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  18. Errors saving DBC on Windows 8/Server 2012

    When using Windows Server 2012, an error occurs when saving a DBC file with the Save button in SQL Alias Manager.

    Bug# 12126

    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  ·  SQL Alias Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. DBC passwords containing special characters cause database connection errors

    DBC passwords containing some special characters (such as semicolons) lead to errors when the DLL attempts to connect to the database.

    Bug# 12304

    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  ·  Database  ·  Flag idea as inappropriate…  ·  Admin →
  20. DLL incorrectly displays detailed error information to users

    When an error is encountered, the ILLiad DLL is displaying detailed error information that should not be visible to end-users.

    Bug# 12291

    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  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6

Feedback and Knowledge Base