[Koha-bugs] [Bug 7001] New: User Configurable Slips

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

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

             Bug #: 7001
           Summary: User Configurable Slips
    Classification: Unclassified
 Change sponsored?: ---
           Product: Koha
           Version: rel_3_6
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Circulation
        AssignedTo: kyle.m.hall at gmail.com
        ReportedBy: srdjan at catalyst.net.nz
         QAContact: koha-bugs at lists.koha-community.org
                CC: gmcharlt at gmail.com


Work To Be Done:
* Hold notification slips and Checkout receipts brought under the Notices
editor
* Associate Notices/Slips with branches, and include a fallback to 'default'
notice type, so there can be both a standard notice layout, and branch-
specific ones
  -  Provide pull down to choose branch and then have
notices under each branch like with circ/fine rules
  -  Use IndependentBranches to prevent edits to notices of other
branches
* Parsing of patron extended attributes into notices
* Allow for notices/slips to be created in and printed with HTML
  -  Right now emails are sent only in plain text
  -  This can either be an automatic process, the script identifies when
the notice is in HTML, or it can be a choice on notice creation (HTML
or Plain Text)
* Ability to include/link/otherwise associate a CSS file with HTML
notices/slips
  -  New system preference NoticeCSS
  -  New system preference SlipCSS

To Test:
* Test on a system with at least two branches
* Create a CSS file for the NoticeCSS
* Create a CSS file for the SlipCSS
* Create a patron at Branch A (Patron A)
  -  Choose to receive at least two enhanced messages (one should be a
hold filled)
  -  Enter at least one extended patron attribute
* Create patron at Branch B (Patron B)
  -  Choose to receive at least two enhanced messages (one should be a
hold filled)
  -  Enter at least one extended patron attribute
* Create at least two notices for each branch (one should be hold filled)
  -  Include branch specific fields as well as information on items and
the borrower
  -  Make sure there are some fields that are different in each notice
  -  Make sure one from each branch has HTML code in it
* Create at least two slips for each branch
  -  One hold slip
  -  Include branch specific fields as well as information on items and
the borrower (include at least one extended patron attribute)
  -  One branch should be in HTML and the other plain text
  -  One checkout receipt
  -  Include branch specific fields as well as information on items and
the borrower (include at least one extended patron attribute)
  -  One branch should be in HTML and the other plain text
* Check out one item to Patron A at Branch A
  -  Print a slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a quick slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a page for that check out
  -  Confirm that data is parsed correctly
* Check out another item to Patron A at Branch A
  -  Print a slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a quick slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a page for that check out
  -  Confirm that data is parsed correctly
* Check out one item to Patron B at Branch B
  -  Print a slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a quick slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a page for that check out
  -  Confirm that data is parsed correctly
* Check out another item to Patron B at Branch B
  -  Print a slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a quick slip for that check out
  -  Confirm that data is parsed correctly
  -  Print a page for that check out
  -  Confirm that data is parsed correctly
* Place a hold for Patron A for pick up at Branch A
* Place a hold for Patron B for pick up at Branch B
* Check in an item on hold from Branch A
  -  Print the hold slip
  -  Confirm that the data is parsed correctly
* Check in an item on hold from Branch B
  -  Print the hold slip
  -  Confirm that the data is parsed correctly
* Check both patrons’ email to be sure that the hold filled email parsed
properly
* Trigger the sending of at least one other notice and confirm that that
email is parsed properly as well

-- 
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.