[Koha-devel] Hide records on Leader 05 = d in OPAC

Tue Jan 12 03:37:55 CET 2016

I imagine that most cataloguers cataloguing in Koha would just hit "Delete
record" in Koha.

However, if you're cataloguing outside of Koha, you can modify LDR05 to "d",
and then import a batch of MARC records into Koha. When you overlay the
records in Koha, they would conceptually be deleted, so a cronjob could come
and "reap" them later without any additional manual intervention. My work on
<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537>
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537 will prevent
these records from showing up in the OPAC in the interim as well.

That said, there is a question as to why we're saving records with a LDR05
of "d" in the database. In theory, if LDR05=d, we could just delete the
record as soon as we see that. However, there are other considerations to
make such as item-level data, subscription data, etc. That's a bit out of
the scope of my caring at the moment. I'm working on batch importing of
records, so I care about being able to signal to Koha that I want to add
some records, update some records, and delete other records.

As for "undeleting", I don't think anyone is currently working on that, but
I'm sure someone could. Historically, I think the LDR05=d was used to remove
records from the OPAC but still let staff see them for a certain period of
time before they were removed. I think removal may have even been
configurable. I've been working on Koha long enough to not recall 100% how
other ILSes worked in that respect in the past.

For what it's worth, the leader is stored in the deletedbiblioitems.marcxml
as well. I think it's a perfect copy of the record at the point in time of
its deletion.

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St, Ultimo, NSW 2007

From: koha-devel-bounces at lists.koha-community.org
[mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Paul A
Sent: Tuesday, 12 January 2016 11:57 AM
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Hide records on Leader 05 = d in OPAC

At 12:44 PM 1/11/2016 +1100, David Cook wrote:

Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_008A_01D14C6D.DDE56680"
Content-Language: en-au
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).

Brendan, David,

Thanks for your work on this. I have sometimes wondered what the LDR, Pos 05
- Record status d - Deleted "Record has been deleted" actually means.

My question is: how many cataloguers take the time and trouble to modify LDR
pos05, rather than just "hit delete" for a record?

>From a Koha db viewpoint, either the record is in MySQL and therefore
(probably?) should get indexed by Zebra, or it has been deleted by a
cataloguer -- logically gone, terminally, no bytes left on the hard disk --
except that Koha has tables "deletedbiblio", "deletedbiblioitems" and
"deleteditems" which (as far as I can tell) do not contain the LDR,
therefore cannot cross-reference pos05=d (and I'm not certain that there is
a way to "undelete" -- can it be done?)

Best -- Paul

While Im all for that, Im thinking that it would also be a good idea to hide
these records with LDR05 din the OPAC before the cronjob is run.

We cant necessarily rely on all Koha instances running this cronjob, nor can
we rely on the frequency. Shouldnt we be hiding these records from the OPAC
as soon as theyre marked as deleted? 

Ive 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 Id ask folk
if its something theyd be interested in. Wed 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 doesnt send
metadata for deleted records). Id match the existing record in Koha using
the identifier, and then set LDR05 to din accordance with the OAI-PMH
deleted status. Then, that record would disappear from the OPAC, so that end
users dont see this skeleton record. 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St, Ultimo, NSW 2007

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
<mailto:Koha-devel at lists.koha-community.org> 
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/ 

---
Maritime heritage and history, preservation and conservation, 
research and education through the written word and the arts.
<http://NavalMarineArchive.com <http://navalmarinearchive.com/> > and
<http://UltraMarine.ca <http://ultramarine.ca/> >

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20160112/aa4d4595/attachment.html>