Case Sensitive Duplicated Circulation Modifier Not Honored during Circulation and Hold Policy Creation

Bug #1548321 reported by Erica Rohlfs on 2016-02-22
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

Evergreen Version 2.9

Within Evergreen, users can currently create duplicate circulation modifiers, if the letter case differs. For example, a system could potentially have several different forms of “book” as a circulation modifier: Book, BOOK, bOok, etc.

User confusion aside, Evergreen will not honor the selected circulation modifier variant within the circulation and hold policies. Evergreen will default back to the first circulation modifier created within this combination.

To recreate:
Create two circulation modifiers, Book and BOOK.
Create Book first.
Create a new circulation policy or hold policy (results are the same). Admin -> Local Administration -> Circulation Policies or Hold Policies.
Within the Circulation Modifier dropdown options, select BOOK. Make sure you select the circulation modifier that was created second.
Click on the next field.
Notice that Evergreen reassigned from BOOK to Book (or whichever circulation modifier you created first).

Within the Item Attribute Editor, users have the ability to select either Book or BOOK. When they select BOOK, the selection saves. However, Evergreen will not be looking at a BOOK policy; it will be looking for the Book policy. So, Evergreen will be using a default policy when users attempt to circulate or hold the item assigned to the BOOK circulation modifier.

There is an additional concern regarding this behavior. For systems or consortiums attempting to restructure their circulation modifiers, polices, etc., they cannot conduct this project with the duality of old and new circulation modifiers.

Erica Rohlfs (erohlfs) on 2016-02-22
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers