| Time |
Nick |
Message |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 09:15 |
|
rjackson_isl_hom joined #evergreen |
| 13:59 |
jeff |
I almost want "soft-required" fields in places like the patron editor. |
| 14:00 |
jeff |
"require" data in a field, but allow the field to be empty if the user forces it. |
| 14:00 |
jeff |
useful for something like a DOB field, where there are circumstances where you need to edit an existing patron and you don't know the DOB / don't have the patron in front of you to ask... |
| 14:01 |
jeff |
since there are circumstances where you'd be unable to save a patron AND you might not have the required information, marking a field as required is going to either prevent you from making the edit you need to make, or will encourage guessing / fake placeholder data. |
| 14:03 |
jeff |
but a prompt on save saying "required field DOB is blank: save anyway?" (or some better wording) could be an improvement. |
| 14:03 |
jeff |
and/or a warning color / indicator for those "required but not required" fields. |
| 16:13 |
|
rjackson_isl_hom joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
