Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    CIRC/WebV: Course Reserves capitalised words sorting incorrectly

    • Article Type: General
    • Product: Voyager
    • Product Version: 6.5.4

    Bug Report Form for Issue 16384-7761

    Date: 8/7/09
    Module(s): Circulation, WebVoyage
    Server platform(s) affected: Solaris/all
    PC OS (if applicable): n/a
    Browser & version (if applicable): all supported

    Release(s) replicated in: 7.1.0, 7.0.4, 6.5.4

    Expected results:
    Titles on a Course Reserve list will sort in alphabetical order by default, regardless of title capitalization.

    Actual results:
    Titles on a Course Reserve list sort with capital letters sorting above the same letter in lower-case form, regardless of how the words appear in proper alphabetical order.

    Workflow implications: Titles on a course reserve list may be slightly out of order.

    Replication steps:

    Open up Circulation
    Click on Reserve
    Get rid of the search screen then click on Reserve at the top to Create a New List
    For the sake of fewer steps, click on the items tab.
    Right click and search for a title with specific capitalization (For this example, let's say the title is 'Great age of fresco').
    Right click again and search for another title, this time with a first word that matches the last example, and a second word that should alphabetically fall after the last example -- but is capitalized (In this example, something like 'Great American customer').
    Great American customer will display above Great age of fresco, though alphabetically it should be the other way around.
    Link up some course information to the reserve list. Choose an instructor, department, course, etc.

    Now go to the relevant Tomcat WebVoyage and click on the Course reserve list.
    Search by the course reserve information that you set.
    The titles will appear in the same order as they do in the Circulation Course Reserve list.

    If you test the course reserve in Classic, the same issue happens.

    Fixed in Voyager 8.1.1

    • Article last edited: 3/19/2015