<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>I imagine that most cataloguers cataloguing in Koha would just hit “Delete record” in Koha.<o:p></o:p></span></a></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>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 </span><a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'> will prevent these records from showing up in the OPAC in the interim as well.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>David Cook<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Systems Librarian<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Prosentient Systems<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>72/330 Wattle St, Ultimo, NSW 2007<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] <b>On Behalf Of </b>Paul A<br><b>Sent:</b> Tuesday, 12 January 2016 11:57 AM<br><b>To:</b> koha-devel@lists.koha-community.org<br><b>Subject:</b> Re: [Koha-devel] Hide records on Leader 05 = d in OPAC<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>At 12:44 PM 1/11/2016 +1100, David Cook wrote:<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Content-Type: multipart/alternative;<br> boundary="----=_NextPart_000_008A_01D14C6D.DDE56680"<br>Content-Language: en-au<br>Hi all:<br>Recently, <a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11084">http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11084</a> was pushed to master. It adds a cronjob which deletes bibliographic records, if their LDR05 is d(ie status deleted).<o:p></o:p></p></blockquote><p class=MsoNormal><br>Brendan, David,<br><br>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.<br><br>My question is: how many cataloguers take the time and trouble to modify LDR pos05, rather than just "hit delete" for a record?<br><br>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?)<br><br>Best -- Paul<br><br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal> <br><br>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.<br><br> <br><br>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? <br><br> <br><br>Ive opened a bug for this purpose: <a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537">http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537</a><br><br> <br><br>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.<br><br> <br><br>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. <br><br> <br><br>David Cook<br><br>Systems Librarian<br><br>Prosentient Systems<br><br>72/330 Wattle St, Ultimo, NSW 2007<br><br> <br>_______________________________________________<br>Koha-devel mailing list<br><a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br><a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>website : <a href="http://www.koha-community.org/">http://www.koha-community.org/</a><br>git : <a href="http://git.koha-community.org/">http://git.koha-community.org/</a><br>bugs : <a href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a> <o:p></o:p></p></blockquote><p>---<br>Maritime heritage and history, preservation and conservation, <br>research and education through the written word and the arts.<br><<a href="http://navalmarinearchive.com/">http://NavalMarineArchive.com</a>> and <<a href="http://ultramarine.ca/">http://UltraMarine.ca</a>><o:p></o:p></p></div></div></body></html>