Activity log for bug #572624

Date Who What changed Old value New value Message
2010-04-30 20:49:42 Ben Shum bug added bug
2010-05-04 14:43:34 Ben Shum 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". 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.
2010-05-04 14:43:36 Ben Shum summary Circulation Policies Configuration - Missing Fields? Circulation Policies Editor - Inserting Default Values
2010-06-11 20:36:55 James Fournie evergreen: status New Confirmed
2010-06-11 20:37:02 James Fournie evergreen: importance Undecided Low
2012-07-18 13:31:53 Jason Stephenson evergreen: status Confirmed Won't Fix