[Koha-bugs] [Bug 12518] New: gather_print_notices.pl doesn't respect hold/reserve pickup location

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

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

            Bug ID: 12518
           Summary: gather_print_notices.pl doesn't respect hold/reserve
                    pickup location
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Notices
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: olli-antti.kivilahti at jns.fi
        QA Contact: testopia at bugs.koha-community.org

Created attachment 29441
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=29441&action=edit
Initial commit from our issue tracker.

gather_print_notices.pl gathers HOLD-letters based on the borrowers'
homebranch.
Our librarians find it hard to send hold notices for Items present in other
branches.

This patch gathers print notices for HOLD-letter_code to the Items'
reserves.branchcode (pickup location) instead.

This is achieved by using a customizable regexp in the
gather_print_notices-script, which picks the barcode from the letter content.

---------------
-- TEST PLAN --
---------------
0. Have a HOLD-letter template with each Items' barcodes somewhere, for ex.
    Barcode: <<items.barcode>>
1. Create a reservation for a borrower with no other message delivery option
than printing. Set the pickup location to other (branch P) than the borrowers
homebranch (branch H).
2. Check the item in and confirm reservation. This enques a letter in the
message_queue-table.
3. run the gather_print_notices.pl -cronjobs with the following parameters
    gather_print_notices.pl <your_notices_directory> --split --holdbarcode
'Barcode: (\S+)<br />'
You will find the letter generated to the branch P, instead of the branch H if
you hadn't used the --holdbarcode -parameter.

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