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

4 results found

  1. Invalid characters in title error when submitted to OCLC

    Workform Mapping should be replacing invalid XML characters.

    Currently workform mapping handles replacement of \r & \n.

    Repro
    1. Create a borrowing request in the client.
    2. Via the database update an Article Title to include "&#x1F"
    3. Close the request form and re-open after the invalid characters are added.
    4. Search OCLC and attempt to send the OCLC request.

    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  ·  OCLC  ·  Admin →

  2. 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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  OCLC  ·  Admin →

  3. OCLC Special Messages: Overdue no longer in use

    Bug# 6924

    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  ·  OCLC  ·  Admin →

  4. Need to remove ESPUpdate table entry for Received when the error is "Received not allowed here"

    If we receive the error we should ensure that the ESPupdate is removed so that it will not attempt to retry since we already know that OCLC will consider it invalid based on it's current state.

    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  ·  OCLC  ·  Admin →

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)