[Koha-bugs] [Bug 6920] New: deleting bibs messes with budgets

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Sep 26 15:55:03 CEST 2011


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6920

             Bug #: 6920
           Summary: deleting bibs messes with budgets
    Classification: Unclassified
 Change sponsored?: ---
           Product: Koha
           Version: master
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P5
         Component: Acquisitions
        AssignedTo: henridamien at koha-fr.org
        ReportedBy: nengard at gmail.com
         QAContact: koha-bugs at lists.koha-community.org


Example from a library I talked to today:

An order was placed for an item using a brief record (with ISBN). While waiting
for the order to arrive a fuller record was imported from OCLC using the ISBN
match, but the match was not found so duplicates were created.  The library
deleted the brief record because the OCLC one was fuller and this left a hole
in the order and screwed up the accounting.  The next time they chose to merge
the OCLC and brief record together but the same thing happened because the bib
number from the brief record was lost in the merge.

--------------

All libraries are going to delete bib records at some point and if those
records were created using acquisitions then the budgeting is going to be
inaccurate.  It will also leave holes on baskets when viewing them with links
to records that do not exist. We need a way to keep the link between acq and
the catalog without allowing changing in cataloging to mess up orders in acq.  

Another solution is to update the merge tool to look at the acq tables and
change the bib number if records are merged - but that's secondary to the
bigger problem of the bib being able to cause so many problems when deleted.

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.


More information about the Koha-bugs mailing list