[Bug 40361] New: Require at least one alphabetic character in first name and surname patron record fields
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40361 Bug ID: 40361 Summary: Require at least one alphabetic character in first name and surname patron record fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: hdunne-howrie@westminster.gov.uk QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com We would like to see if possible to add in some data validation to patron records so that name fields would require at least one alphabetic character to be included otherwise the record should not be saved. We have a workaround using some .js we added in so that the save button won't display (with an explanation note to staff) if this criteria is not met, but it occurs to me this isn't a particularly stable way to do data validation and we would like to see this added to the base code. Giving libraries the control over the criteria by which patron record fields can or cannot save would be a massive improvement in ensuring the quality of patron records. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40361 --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- There is BorrowerMandatoryField to make fields mandatory which would require something to be entered before saving. Can you explain, why this is not enough/doesn't work for you? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40361 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #2 from David Cook <dcook@prosentient.com.au> --- (In reply to Katrin Fischer from comment #1)
There is BorrowerMandatoryField to make fields mandatory which would require something to be entered before saving. Can you explain, why this is not enough/doesn't work for you?
I believe that they're saying they want additional data validation rules for their name fields for patron records. -- Server-side data validation of individual fields is a broad topic that has been discussed a bit in Koha, but it's a massive task to make that systematic massive improvement. That said, I do think it's something that needs to be done at some point. One of the hardest parts if coming up with a backend design that enough people agree on. -- In terms of front-end validation, for opac-memberentry.pl and memberentry.pl it looks like we're using the jQuery Validator plugin. It should be fairly easy to use *UserJS to add additional jQuery Validator rules and methods. Since "name fields would require at least one alphabetic character to be included" isn't a universal rule that would apply to everyone, this might be the most practical approach to take. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40361 --- Comment #3 from Hannah Dunne-Howrie <hdunne-howrie@westminster.gov.uk> --- Yes, that's correct. While we can make a field mandatory we are seeing a problem with low quality in name field data. We are seeing accounts created with for example "1" or other numbers added into the name fields instead of actual names. We want to add in some additional data validation rules so we can better control this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40361 --- Comment #4 from David Cook <dcook@prosentient.com.au> --- (In reply to Hannah Dunne-Howrie from comment #3)
Yes, that's correct. While we can make a field mandatory we are seeing a problem with low quality in name field data. We are seeing accounts created with for example "1" or other numbers added into the name fields instead of actual names. We want to add in some additional data validation rules so we can better control this.
By the way, is this for self-registration, OPAC self-modification, staff interface, or all the above? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40361 --- Comment #5 from Hannah Dunne-Howrie <hdunne-howrie@westminster.gov.uk> --- Great question. All of the above! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org