Add explanatory text to patron self-registration

[Jeff Davis]

It would be cool if there was an easy way to add explanatory text to the patron self-registration form -- for example, a "what this page is for" blurb at the top, or a personal information collection notice above the submit button -- without having to modify register.tt2 directly.

[Diane Disbro (ddisbro)]

Yes! "Must be 18-years-old" and "Enter DOB in format shown" would save staff and patron time. It would also be helpful for individualized texts to be available at the system rather than the consortium level.

[Jessica Woolford (jwoolford)]

+1 for this idea and customizable text per org

[Jeff Davis (jdavis-sitka)]

Working branch user/jeffdavis/lp2028411-self-registration-blurbs-2 has a potential implementation:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jeffdavis/lp2028411-self-registration-blurbs-2

This branch adds a couple of settings to config.tt2 allowing you to add text at the top of the form (ctx.register_intro), immediately above the submit button (ctx.register_submit_notice), or both. Examples are provided but both settings are disabled by default. If we like this approach, I'll add a release note and target to the next release.

Another option would be to use a library setting. I went with config.tt2 because it feels like the right way to control what's displayed in the OPAC, and because it avoids the risk of an injection attack via library settings.

[Jeff Davis (jdavis-sitka)]

Release notes have been added to the branch.

[Jane Sandberg (sandbergja)]

I like it! Here's a signoff branch in the working repo: user/sandbergja/lp2028411-signoff -- thanks, Jeff!

[Bill Erickson (berick)]

Follow-up branch:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp2028411-self-registration-blurbs

Adds a commit to make the new text i18n friendly.

[Jeff Davis (jdavis-sitka)]

I included HTML markup in the example settings because the messages will often need to include markup in the real world -- my use case is a multi-paragraph message containing a link to an external privacy policy. I don't want to bikeshed though, I'm good with whatever gets this committed.

[Jane Sandberg (sandbergja)]

What if we split the difference, including both some HTML and some i18n in the example text, e.g.:

ctx.register_intro = "<p>" _ l("Please fill out the form below.") _ "</p>";