Hi all: Recently, http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11084 was pushed to master. It adds a cronjob which deletes bibliographic records, if their LDR05 is "d" (ie status deleted). While I'm all for that, I'm thinking that it would also be a good idea to hide these records with LDR05 "d" in the OPAC before the cronjob is run. 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 It should be a pretty easy change, especially when using special attribute @attr 14=1 to avoid past OpacSuppression problems, but I thought I'd ask folk if it's something they'd be interested in. We'd probably still want to see these records in the Staff Client, as we want to be able to find all records in the database in the Staff Client. I admit that I have a special interest in this where I might be overlaying existing records using a mostly empty skeleton record generated from an OAI-PMH identifier and a OAI-PMH deleted status (OAI-PMH doesn't send metadata for deleted records). I'd match the existing record in Koha using the identifier, and then set LDR05 to "d" in accordance with the OAI-PMH deleted status. Then, that record would disappear from the OPAC, so that end users don't see this skeleton record. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007