[Koha-bugs] [Bug 2141] New: Bib search can retrieve deleted bibs

[bugzilla-daemon at pippin.metavore.com]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2141

           Summary: Bib search can retrieve deleted bibs
           Product: Koha
           Version: HEAD
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Searching
        AssignedTo: jmf at liblime.com
        ReportedBy: galen.charlton at liblime.com
         QAContact: koha-bugs at lists.koha.org


Assuming that Zebra is used, if a bib record is deleted in Koha, there can be a
period of time when the bib is retrieved from a Zebra search even though it is
no longer present in the database.  This twilight period lasts until the
zebraqueue table is processed by rebuild_zebra.pl -z or zebraqueue_daemon.pl.

If a user clicks on such a bib on results list, the OPAC will return a 404. 
This is actually useful, since the same opac-details.pl page is what a user
might use to permalink a bib, but instead of using the default 404.pl template,
one that specifically says that a bib is missing (and was recently deleted)
would make more sense to the patron.

When the same thing happens in the staff interface, Koha carps:

Can't call method "field" on an undefined value at
/home/gmc/koha/dev/C4/Biblio.pm line 944.

A patch is forthcoming that will instead redirect to the default 404.

A special case is when the deleted bib is the only result for the search - in
that case, redirecting to any 404 page is a mistake, as it makes the user think
that the search is broken.  When only one hit is returned, it is probably worth
the RDMS query hit to make sure that the bib exists before redirecting to
details.pl.

The three display issues aside, this bug is a placeholder for the larger issue
of whether it is possible to keep the Zebra search results perfectly in sync
with the DB (at least for deleted bibs) without having to query the RDMS for
every bib in the hitlist.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.