Bug 27020

Summary: Patron self registration from should include ability to add extended patron attributes
Product: Koha Reporter: Lucas Gass <lucas>
Component: OPACAssignee: Lucas Gass <lucas>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: major    
Priority: P5 - low CC: jonathan.druart, kelly, mfuerst
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Bug Depends on: 26119    
Bug Blocks:    
Attachments: Bug 27020: Allow patron attributes of self reg form
Bug 27020: Allow patron attributes of self reg form
Bug 27020: Allow patron attributes of self reg form

Description Lucas Gass 2020-11-13 16:58:56 UTC
Before Bug 26119 your were able to add extended patron attributes to the self reg form, not just the modification form. Bug 26119 added a line that makes it impossible for these attributes to show up on the self reg form.

Many libraries rely heavily on the ability to let patrons choose extended attributes at self reg time.
Comment 1 Lucas Gass 2020-11-13 17:10:47 UTC
Created attachment 113615 [details] [review]
Bug 27020: Allow patron attributes of self reg form

Test plan:
1. Create some patron  attributes types.
2. Make sure you click both Display in OPAC and Editable in OPAC.
3. Make sure  PatronSelfRegistration is on.
4. Register and notice that your patron attribute types do not display.
5. Find an already registered patron and go edit your patron details on the OPAC, you do see the attributes listed here.
6. Apply patch
7. Try registering again, the attributes should display.
8. Finish registering the user and look them up in the staff cleint. See that the parton attributes you choose while registering have saved correctly.
Comment 2 Martha Fuerst 2020-11-13 17:19:13 UTC
We relied very heavily on the ability for patrons to edit these attributes at self-registration before our 20.05 upgrade. Bug 26199 removed functionality for Huntsville-Madison County.

Most importantly, we had been using it for patrons to signal their permission for staff to use public records to attempt to validate their address remotely, so that we could continue to do remote registration validations in a more secure manner.

I do not understand how something that we could do in 19.11 is now something that we can't do in 20.05, when both self-registration and self-modification use the same template.
Comment 3 ByWater Sandboxes 2020-11-13 17:45:19 UTC
Created attachment 113625 [details] [review]
Bug 27020: Allow patron attributes of self reg form

Test plan:
1. Create some patron  attributes types.
2. Make sure you click both Display in OPAC and Editable in OPAC.
3. Make sure  PatronSelfRegistration is on.
4. Register and notice that your patron attribute types do not display.
5. Find an already registered patron and go edit your patron details on the OPAC, you do see the attributes listed here.
6. Apply patch
7. Try registering again, the attributes should display.
8. Finish registering the user and look them up in the staff cleint. See that the parton attributes you choose while registering have saved correctly.

Signed-off-by: Kelly McElligott <kelly@bywatersolutions.com>
Comment 4 ByWater Sandboxes 2020-11-13 22:03:30 UTC
Created attachment 113634 [details] [review]
Bug 27020: Allow patron attributes of self reg form

Test plan:
1. Create some patron  attributes types.
2. Make sure you click both Display in OPAC and Editable in OPAC.
3. Make sure  PatronSelfRegistration is on.
4. Register and notice that your patron attribute types do not display.
5. Find an already registered patron and go edit your patron details on the OPAC, you do see the attributes listed here.
6. Apply patch
7. Try registering again, the attributes should display.
8. Finish registering the user and look them up in the staff cleint. See that the parton attributes you choose while registering have saved correctly.

Signed-off-by: Kelly McElligott <kelly@bywatersolutions.com>

Signed-off-by: Barbara Johnson <barbara.johnson@bedfordtx.gov>
Comment 5 Jonathan Druart 2020-11-14 08:17:44 UTC

*** This bug has been marked as a duplicate of bug 26973 ***
Comment 6 Jonathan Druart 2020-11-16 13:45:06 UTC
Could someone confirm that the patch on bug 26973 fixes properly the issue reported here?