Circulation Policies Editor - Inserting Default Values

[Ben Shum]

Evergreen version: 1.6.0.2
OpenSRF: 1.2.2
PostgreSQL: 8.3
Linux: Debian 5.0

We've noticed that the staff client's interface for entering new Circulation Policies does not include every field that is currently usable on the database (table config.circ_matrix_matchpoint). In particular, we are looking to find an interface setting for the database field of "ref_flag". This is set by default through the client as false, but we would like to control this entry or have it enter as null instead.

Two other fields that also seem to be missing are "juvenile_flag" and "is_renewal".

Edit (5/4/10): I just noticed that there *is* a reference field for true / false setting. But by default this enters a value of false to the database. We would like to see an option to enter "null" instead.

[Jason Stephenson (jstephenson)]

I'm not entirely sure what problem this bug is attempting to solve. However, in 2.0 b4, it looks like the missing fields appear and the true/false fields default to unset. I think the table definition will turn a null into a false in the database.

Anyway, can someone please confirm this bug in 1.6.1.4 or indicate that it has been fixed?

[Robert Soulliere (rcsoulliere)]

Comparing 1.6.1.4 and 2.0B, I noticed that the "Renewal?" field is not present in 1.6.1.4.

The reference field is present in both versions and defaults to unchecked.

I am not sure about the "juvenile_flag"
Are the fields:
"User Age: Lower Bound"
"User Age: Upper Bound"
equivalent?
These fields are present in both 2.0 and 1.6.1.4.

Robert

Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
<email address hidden>
Telephone: [phone] x3936
Fax: [phone]
________________________________________
From: <email address hidden> [<email address hidden>] On Behalf Of Jason Stephenson [<email address hidden>]
Sent: December 8, 2010 1:38 PM
To: Soulliere, Robert
Subject: [Bug 572624] Re: Circulation Policies Editor - Inserting Default Values

I'm not entirely sure what problem this bug is attempting to solve.
However, in 2.0 b4, it looks like the missing fields appear and the
true/false fields default to unset. I think the table definition will
turn a null into a false in the database.

Anyway, can someone please confirm this bug in 1.6.1.4 or indicate that
it has been fixed?

--
You received this bug notification because you are subscribed to
Evergreen.
https://bugs.launchpad.net/bugs/572624

Title:
  Circulation Policies Editor - Inserting Default Values

Status in Evergreen - Open ILS:
  Confirmed

Bug description:
  Evergreen version: 1.6.0.2
OpenSRF: 1.2.2
PostgreSQL: 8.3
Linux: Debian 5.0

We've noticed that the staff client's interface for entering new Circulation Policies does not include every field that is currently usable on the database (table config.circ_matrix_matchpoint). In particular, we are looking to find an interface setting for the database field of "ref_flag". This is set by default through the client as false, but we would like to control this entry or have it enter as null instead.

Two other fields that also seem to be missing are "juvenile_flag" and "is_renewal".

Edit (5/4/10): I just noticed that there *is* a reference field for true / false setting. But by default this enters a value of false to the database. We would like to see an option to enter "null" instead.

This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message. If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited. If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.

[Ben Shum (bshum)]

Right, this bug was aimed more at the automatic selection of true/false for certain database entries in the circ_matrix_matchpoint table. In the case of "is_renewal" for 2.0, it's correct that you can choose between Unset, True, or False as options. But for the "ref_flag" entry it still automatically forces either True/False based on the checkbox, automatically false if unselected when creating a new circ rule. It would be advantageous to our organization for there to be consistency between the Unset, True, False dropdown option being available for all fields of type.

The second part of this bug was pieces that were considered "missing" from 1.6.0 at the time. These seem to have been largely addressed looking at the 2.0 beta staff client interface. The "juvenile_flag" is a reference to a field in the actual circ_matrix_matchpoint table itself. This appears to be a true/false field for matching purposes but is not reflected as an option in the existing staff client interfaces. It is presumed that this should match on the juvenile flag in user records and allow for more granular circ policy matching.