[Koha-bugs] [Bug 13182] New: When placing an order from a staged file, check for duplicates, display availability information, choose to overlay matched records.

[bugzilla-daemon at bugs.koha-community.org]

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

            Bug ID: 13182
           Summary: When placing an order from a staged file, check for
                    duplicates, display availability information, choose
                    to overlay matched records.
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Acquisitions
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: olli-antti.kivilahti at jns.fi
        QA Contact: testopia at bugs.koha-community.org

When making acquisitions from one staged file, by many branches as a joint
effort, it is important to be able to make orders from the same import_record.

This places some extra requirements.
1. An status = 'imported' import_record needs to be shown in the stage_file so
other branches can order from it as well. So we can't "hide" a import_record
from the staged_file after an order is placed.
2. Having imported one import_record, that import_record must know it is
matched to the just imported Biblio, so next acquirers know that it is already
in our catalog.
3. We need to know which other branches have already ordered the item so we
wont end up ordering too many copies of one Biblio to the consortium. Thus we
color each row and show the count of Items in the current user's branch and the
total amount of Items in the whole consortium. Additional tooltip listing of
Item counts by Branch is displayed so we know are there any such Items near us.
4. If we know we already have a matching biblio in Koha, we can optionally
overlay the existing Biblio with the new one. (We don't really need it but
looks like Bug 12074 needs it). Also a good hook to attach more advanced
automatic overlaying/transformation mechanisms.

TEST PLAN:

SETUP:

0a. Define a Matcher from admin/matching-rules.pl. We think good starting
values are:
rules, score
020a, 1000
024a, 1000
028a, 1000
245a, 500
240a, 500
110a, 300
100a, 300
Matching threshold 800

0b. Stage a MARC file.

1. Start making an order from a staged_file, stop when you see the
   import_records after you selected the batch to order from at
   acqui/addorderiso2709.pl?import_batch_id=50...
2. If you have matches, they are colored and the Item counts are visible.
   If not, order any item and return to the previous view and reload.
3. Observe that you should now have atleast one match. The match displays the
   amount of items in your branch, in your consortium, and a tooltip from the
   record title, showing a breakdown of items by branch.
4. When you add more orders, you get more order lines, but all orders are for
   the same Biblio, thus you don't get many Biblios, one per order.

TODO: Unit tests.
TODO: Better test plan.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.