---- Reported by gmcharlt@gmail.com 2010-02-12 14:16:23 ---- Currently, the batch item modification tool will allow you to set item fields to a positive value (e.g., to change a location), but will not allow you to clear or blank a field. For example, it cannot be used to change a group of items from lost to not lost. The desired behavior is to be able to do all of the following: [1] explicitly set a field to a known value (does this now) [2] explicitly clear or blank out a field (new behavior) [3] ... while not accidentally blanking out fields that are not meant to be changed. ---- Additional Comments From paul.poulain@biblibre.com 2010-02-12 14:30:47 ---- in phpmyadmin, there is a checkbox "SET NULL" to make the difference between '' and NULL I think we could/should use this as well : callnumber : ____________________v [ ] empty Where [ ] can be checked only if the left list is on "nothing" (______) entry. And is not checked by default Other option : use a [ ] keep-as-it-is checkbox (_____v) meaning "empty" ---- Additional Comments From gmcharlt@gmail.com 2010-02-12 15:34:59 ---- (In reply to comment #1) > in phpmyadmin, there is a checkbox "SET NULL" to make the difference between '' > and NULL > I think we could/should use this as well : > > callnumber : ____________________v [ ] empty > Where [ ] can be checked only if the left list is on "nothing" (______) entry. > And is not checked by default Agreed. > Other option : > use a [ ] keep-as-it-is checkbox (_____v) meaning "empty" I prefer the former - the default setting should be to make no change. ---- Additional Comments From nengard@gmail.com 2010-02-12 16:12:00 ---- This is related to: Bug - 3916 -- they don't depend on each other so I didn't put it in that field. --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:23 UTC --- This bug was previously known as _bug_ 4172 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4172 Actual time not defined. Setting to 0.0
Not quite the same thing, but the same result. *** This bug has been marked as a duplicate of bug 6068 ***