Summary: | Patron self-modification values not retained if field blocked in PatronSelfRegistrationBorrowerUnwantedField | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | major | ||
Priority: | P5 - low | CC: | hebah, jennifer.marlatt, laura, lucas |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Andrew Fuerste-Henry
2022-03-18 20:09:52 UTC
I just ran into this and only found the duplicate after writing up my test plan and everything... so adding it here instead: If a field is set as Unwanted for the self registration form, it will not be reported to the library if an address change is requested by a registered user from their account. To test: - BorrowerUnwantedField: Set a field of your choice to "unwanted". Example: sex - Make sure same field is visible in: PatronSelfModificationBorrowerUnwantedField PatronSelfRegistrationBorrowerUnwantedField - Log into your OPAC account - Request a change of said field - Check the change request in the staff interface: field will be missing - PatronSelfRegistrationBorrowerUnwantedField: Update to make field visible - Request another change from the OPAC - Verify field is now visible in the change request The PatronSelfRegistrationBorrowerUnwantedField should not influence the change requests, only PatronSelfModificationBorrowerUnwantedField should. I am updating the severity as this affects the library - user communication and is basically causing an unnoticeable data loss. This is causing problems at our library especially for patrons who rely on emails to alert them to due dates, renewals, etc. Patrons are attempting to add/update their email addresses through the OPAC. The request to update a patron record appears in the staff interface, but the data is not transferred with the request. |