Wish List: Improve print options for patron registration screen

[Terran McCanna]

Our libraries are making good use of the online patron self-registration form, but many of them have local requirements to store a signed paper copy of the application for a certain length of time. The patron registration form is printable, but it's not pretty, and there's not an easy way to customize it (for our purposes, we'd like a signature block including the text of what they are agreeing to by signing up for an account, and maybe even some additional checkboxes that don't get stored in the database such as "Would you like to sign up for our newsletter?" or "Would you like to register to vote today?")

The simplest and most flexible solution would probably be to change the print function so that it uses a customizable print template set up in the Action Trigger Event Definitions.

We're currently on Evergreen 2.9.1

[Galen Charlton (gmc)]

Just to clarify, it's the *staff-side* patron editor that you want more printing options for, correct?

[Terran McCanna (tmccanna)]

Yes, in the staff client :)

(We customized the form on the OPAC to include our agreement text, but that's not sufficient for all local record-keeping needs.)

[Blake GH (bmagic)]

It looks like the web based staff client will have print patron registration functionality. print.css

/* hide everything but the print div */
head { display: none; } /* just to be safe */
#body div:not([id="print-div"]) { display:none }
div { display: none }
#print-div { display: block }
#print-div div { display: block }
#print-div pre { border: none }

The markup on the page:
 <!-- content printed via the browser is inserted here for
         DOM-ification prior to delivery to the printer -->
    <div id="print-div" eg-print-container></div>

Right now does not have any data, but it's still under development. Presumably, this page will print nicer with angular and should be complete. Thoughts?

[Terran McCanna (tmccanna)]

Print functionality for the patron screen has not yet been developed for the web client as of 2.12.1 - see: https://bugs.launchpad.net/evergreen/+bug/1693036

[Terran McCanna (tmccanna)]

The patch to bug #1693036 resolves the problem for the web client. Closing out this bug as it related to the xul client.