http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 --- Comment #1 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- Created attachment 33085 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=33085&action=edit Bug 13182 - When placing an order from a staged file, check for duplicates, display availability information, choose to overlay matched records. 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 Bg_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.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=12074 -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33085|0 |1 is obsolete| | --- Comment #3 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- Created attachment 33088 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=33088&action=edit Bug 13182 - When placing an order from a staged file, check for duplicates, display availability information, choose to overlay matched records. 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 Bg_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 watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 --- Comment #5 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- Created attachment 33376 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=33376&action=edit Bug 13182 - When placing an order from a staged file, check for duplicates, display availability information. 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 and to know how many Items have already been ordered. Also introduces misc/maintenance/matchAllStagedRecords.pl to recreate import_record matchings based on the given matcher. 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. TEST PLAN: SETUP: 0a. Define a Matcher from admin/matching-rules.pl. We think good starting values are: Search index, Tag , score ISBN, 020a, 1000 Identifier-standard, 024a, 1000 Identifier-standard, 028a, 1000 Title, 245a, 500 Title-uniform, 240a, 500 Personal-name, 110a, 300 Corporate-name, 100a, 300 Matching threshold 800 You can use an existing matcher as well if you have it configured to other than ISBN. 0b. Stage a MARC file. BASIC USAGE: 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 for many orderlines. UNLEASH THE HOUNDS OF ACQUISITIONS: 1. Order a bunch of biblios and items for homebranch A. Make sure that you get the ordered orderlines in your basket. 2. Order a bunch of biblios and items for homebranch B. 3. Order a bunch of biblios and items for homebranch C. 4. Observe that the biblios already ordered into your catalogue are colored and a number is in front of the title. First number is the count of Items for this Biblio in user's logged-in-branch, second is the total number of Items in the catalogue. Hovering mouse pointer over the title displays a tooltip with a breakdown of all Items by homebranch. TODO: Unit tests. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33090|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33377|0 |1 is obsolete| | --- Comment #7 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- Created attachment 33378 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=33378&action=edit Bug 13182 - Overlay an existing Biblio with the acquired import_record 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 Bg_12074 needs it). TEST PLAN 1. Add Items to an order from a staged file. 2. Go and edit the newly added Biblio. Set the field 003 to "TEST ME GENTLY". 3. Add more Items for this same biblio from the same staged_file. 4. While selecting what to add, check the "Overlay?"-checkbox to replace the existing Bibliographic record with the import_record you are ordering. 5. Save the orderline selection. 6. Observe that the existing modified biblio has changed to it's latest revision. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff --- Comment #9 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- This feature is pending proper unit tests but looking forward to some feedback from the community. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 M. Tompsett <mtompset@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33376|0 |1 is obsolete| | --- Comment #11 from M. Tompsett <mtompset@hotmail.com> --- Created attachment 38113 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=38113&action=edit Bug 13182 - When placing an order from a staged file, check for duplicates, display availability information. 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 and to know how many Items have already been ordered. Also introduces misc/maintenance/matchAllStagedRecords.pl to recreate import_record matchings based on the given matcher. 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. TEST PLAN: SETUP: 0a. Define a Matcher from admin/matching-rules.pl. We think good starting values are: Search index, Tag , score ISBN, 020a, 1000 Identifier-standard, 024a, 1000 Identifier-standard, 028a, 1000 Title, 245a, 500 Title-uniform, 240a, 500 Personal-name, 110a, 300 Corporate-name, 100a, 300 Matching threshold 800 You can use an existing matcher as well if you have it configured to other than ISBN. 0b. Stage a MARC file. BASIC USAGE: 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 for many orderlines. UNLEASH THE HOUNDS OF ACQUISITIONS: 1. Order a bunch of biblios and items for homebranch A. Make sure that you get the ordered orderlines in your basket. 2. Order a bunch of biblios and items for homebranch B. 3. Order a bunch of biblios and items for homebranch C. 4. Observe that the biblios already ordered into your catalogue are colored and a number is in front of the title. First number is the count of Items for this Biblio in user's logged-in-branch, second is the total number of Items in the catalogue. Hovering mouse pointer over the title displays a tooltip with a breakdown of all Items by homebranch. TODO: Unit tests. NOTE: Please check rebase I did. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 M. Tompsett <mtompset@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33379|0 |1 is obsolete| | --- Comment #13 from M. Tompsett <mtompset@hotmail.com> --- Created attachment 38115 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=38115&action=edit Bug 13182 - Remove really dead code. NOTE: Please check the rebase I did. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13182 --- Comment #15 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- Thanks for the rebase M. Tompsett! -- You are receiving this mail because: You are watching all bug changes.