On Tue, Jan 12, 2016 at 08:48:21AM -0500, Galen Charlton wrote:
Hi,
On Sun, Jan 10, 2016 at 8:44 PM, David Cook <dcook@prosentient.com.au> wrote:
We can’t necessarily rely on all Koha instances running this cronjob, nor can we rely on the frequency. Shouldn’t we be hiding these records from the OPAC as soon as they’re marked as “deleted”?
I’ve opened a bug for this purpose: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537
I am in mild disfavor of this proposal, particularly as implemented in current patch. Using a cronjob to delete records where Leader/05 is set to 'd' is useful when the library has arranged their workflow such that they *know* that Leader/05 = 'd' is being used consistently to signify that a record is no longer wanted. However, for a library that has not hitherto cared about the values in that position, unconditionally suppressing the display of such records could come as an unwelcome surprise.
I'd echo Galen's caution, especially if records are being imported, I've seen cases where trying to do this has revealed that records in use locally have inherited a deleted status from an upstream provider and does not reflect local status. Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com