[Bug 28633] New: Add a preferred_name field and an effective_name method to patrons
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Bug ID: 28633 Summary: Add a preferred_name field and an effective_name method to patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: nick@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com Some institutions store legal names in their directories and for patron imports, but would also like to be able to record 'preferred' names in the patro records. It would be nice to have a field for preferred_name and a method to select the preferred name when it exists, and the firstname when it doesn't Following the item we would suggest 'effective_name' - the additional method can be used in patron-title.inc and in notices to simplify name choice. -- 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=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |nick@bywatersolutions.com |ity.org | -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Lisette Scheer <lisetteslatah@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisetteslatah@gmail.com --- Comment #1 from Lisette Scheer <lisetteslatah@gmail.com> --- Yes, this would be lovely. We use the "Other Name" field sort of like this and train staff to use the other name. I'm currently working on updating our notices with TT to send the other name instead of first name if it is present but that doesn't help on the OPAC side where a patron will still see their legal name. Lisette -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #2 from David Cook <dcook@prosentient.com.au> --- We've certainly had libraries ask for something like this, although it would also need to take into account patron searching, as I've had librarians say they want to be able to search for patrons using their preferred name rather than their legal name. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Trivial patch Status|NEW |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #3 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 123008 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123008&action=edit Bug 28633: DB Update -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #4 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 123009 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123009&action=edit Bug 28633: DO NOT PUSH Schema Changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #5 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 123010 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123010&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferredname' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name now displays on patron details 6 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 7 - Sign in as patron to opac 8 - Confirm preferred name shows 9 - Edit account on opac and confirm field is present -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@bywatersolutions.com Status|Needs Signoff |Failed QA --- Comment #6 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- With the patch applied, patron first names do not appear in the patronbriefintro sidebar on the left or in the "Checking out to [Patron name]" box on the Check out tab, even when preferred name is NULL or blank. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #123010|0 |1 is obsolete| | --- Comment #7 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 123658 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123658&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferredname' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name now displays on patron details 6 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 7 - Sign in as patron to opac 8 - Confirm preferred name shows 9 - Edit account on opac and confirm field is present -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Lisette Scheer <lisetteslatah@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #8 from Lisette Scheer <lisetteslatah@gmail.com> --- Signed off in the Bywater Sandbox. I also checked and you can still search by first name. I do think it's a little strange that the only place to see the first name on the staff client is by editing the patron. Might be confusing if someone is trying to figure out why a patron came up in a search. Excited for this! Lisette -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA CC| |martin.renvoize@ptfs-europe | |.com --- Comment #9 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- I can't see that one can search on the new preferred name.. I think that's a must for this. I also find it a little confusing on the patron page.. I think I'd actually prefer to display 'Legal name' as a distinct and clear field if we're falling through to preferred name for the main display. We also don't appear to catch the the dropdown for 'PatronAutoComplete'. Sorry dude.. I think this is a great start, but it need a little more work ;) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #123008|0 |1 is obsolete| | Attachment #123009|0 |1 is obsolete| | Attachment #123658|0 |1 is obsolete| | --- Comment #10 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 125497 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=125497&action=edit Bug 28633: DB Update -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #11 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 125498 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=125498&action=edit Bug 28633: DO NOT PUSH Schema Changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #12 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 125499 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=125499&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferredname' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name now displays on patron details 6 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 7 - Sign in as patron to opac 8 - Confirm preferred name shows 9 - Edit account on opac and confirm field is present -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #13 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 125500 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=125500&action=edit Bug 28633: (follow-up) Show legal name and add preferredname to searches This patch adds to the DB update a condition to add 'preferredname' to DefaultPatronSearchFields. It also adjust the koha defaults to include it if the pref is empty The 'firstname' is displayed as 'Legal name' on the details page, with id/class to allow ajusting via JS/CSS PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Aply patches and updatedatabase and restart_all 2 - Add a preferredname to a patron 3 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname Add preferredname if not 4 - Perform checkout and patron search using preferredname, confirm patron is found 5 - On patron's detail page confirm 'Legal name' shows 6 - Remove patron's first name, confirm 'Legal name' is no longer present 7 - Enable PatronAutoComplete system preference 8 - Type patron's surname into Checkout or patron search but don't hit enter 9 - Confirm patron is dsiplayed with 'preferredname' in the preview -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #14 from David Cook <dcook@prosentient.com.au> --- I'm not sure what I think about "Legal name" in this context. I suppose if there are any cases where they have something other than their legal name in first name when also using a preferred name it just becomes a data problem which can be fixed... -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Rebecca Coert <rcoert@arlingtonva.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rcoert@arlingtonva.us -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #15 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to David Cook from comment #14)
I'm not sure what I think about "Legal name" in this context.
I suppose if there are any cases where they have something other than their legal name in first name when also using a preferred name it just becomes a data problem which can be fixed...
"Given name"? Or should it just remain 'First name'? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #16 from David Cook <dcook@prosentient.com.au> --- (In reply to Nick Clemens from comment #15)
(In reply to David Cook from comment #14)
I'm not sure what I think about "Legal name" in this context.
I suppose if there are any cases where they have something other than their legal name in first name when also using a preferred name it just becomes a data problem which can be fixed...
"Given name"? Or should it just remain 'First name'?
Personally I think it should remain 'First name', but I'm not an expert on name terminology either heh. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #17 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- A rename here would have quite a lot of consequences for documentation and such. I see a potential issue with confusing people by having a lot of different name variations and options. I think keeping the 'first name' would be good. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #18 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #17)
A rename here would have quite a lot of consequences for documentation and such. I see a potential issue with confusing people by having a lot of different name variations and options. I think keeping the 'first name' would be good.
Another +1 for "first name." -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #125500|0 |1 is obsolete| | --- Comment #19 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 126591 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=126591&action=edit Bug 28633: (follow-up) Show first name and add preferredname to searches This patch adds to the DB update a condition to add 'preferredname' to DefaultPatronSearchFields. It also adjust the koha defaults to include it if the pref is empty The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches and updatedatabase and restart_all 2 - Add a preferredname to a patron 3 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname Add preferredname if not 4 - Perform checkout and patron search using preferredname, confirm patron is found 5 - On patron's detail page confirm 'First name' shows 6 - Remove patron's first name, confirm 'First name' is no longer present 7 - Enable PatronAutoComplete system preference 8 - Type patron's surname into Checkout or patron search but don't hit enter 9 - Confirm patron is dsiplayed with 'preferredname' in the preview -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA CC| |tomascohen@gmail.com --- Comment #20 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Nick, 1. You need to either exclude the attribute from the API (preferredname => undef in Koha::Patron::to_api_mapping) or add a mapping for it, and add it also to definitions/patron.json 2. I suggest you name the column preferred_name to avoid the need for any mapping :-D Failing because it is breaking the API as-is. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #125497|0 |1 is obsolete| | Attachment #125498|0 |1 is obsolete| | Attachment #125499|0 |1 is obsolete| | Attachment #126591|0 |1 is obsolete| | --- Comment #21 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 128968 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128968&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #22 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 128969 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128969&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #23 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 128970 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128970&action=edit Bug 28633: DO NOT PUSH Schema Changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #24 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Coming back to this... sorry for the hiatus. First name works fine and I agree with all the reasoning given, well argued :) A quick test run and I'll SO.. the code all looks good to me :) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #128968|0 |1 is obsolete| | --- Comment #25 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 130000 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=130000&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #128969|0 |1 is obsolete| | --- Comment #26 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 130001 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=130001&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #128970|0 |1 is obsolete| | --- Comment #27 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 130002 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=130002&action=edit Bug 28633: DO NOT PUSH Schema Changes Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #28 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- This works nicely now; To me, the name appears in the right places, looks good and isn't confusing and is searchable where one would expect it to be. So.. signing off on that front. It did make me take a look at some of the other name fields in patrons though, and that, I found, confusing. 'othernames' appears to partially try to do what this patch does (I'd always thought of it as 'middle names', but I note that othernames actually appears at the top of the 'contact information in double-quotes and not aligned with the rest of the information and with no label. I also find it slightly strange that 'lastname' doesn't appear in that contact information block. So.. in short.. I like this patch, but would like to see a little effort go into tidying up the members display data in some future bugs.. perhaps Owen could help there.? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=21978 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #29 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- See also bug 21978 where people are requesting 'middlename' get added as another field too. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Manual, | |release-notes-needed Status|Signed Off |Failed QA --- Comment #30 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I had to do a rebase for a conflict in Patrons.t and recreate the schema files locally. Overall this works really really well already! 1) Tiny typo + description: patron's preferred named 2) Patron search results In patron search results I still see the "firstname" instead of the "preferred name". This seems a little confusing, as this is the only place now showing the firstname. On the other hand, if someone presents an ID and I want to search forthem, I will need to make the connection. Maybe we could display the preferred name additionally to the firstname somehow? 3) Auto-complete for patrons When I type "Cait" the entry doesn't show, only when I type "Katrin". But in the preview, it shows 'Cait' ... So there is a mismatch with what you need to type and what will show. I am not sure how to resolve this, but maybe you have an idea or can explain reasoning? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=30568 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #130000|0 |1 is obsolete| | --- Comment #31 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 133445 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133445&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #130001|0 |1 is obsolete| | --- Comment #32 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 133446 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133446&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #33 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 133447 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133447&action=edit Bug 28633: (follow-up) Account for bug 29695 changes During rebase of this patchset we drop the columns.def and borrowers.json changes introduced. We store this mapping in the module now, so this patch does that. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #34 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 133448 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133448&action=edit Bug 28633: (follow-up) Account for changes with bug 30063 Bug 30063 removes the C4/Utils/DataTables/Members.pm module and instead uses the API and a patron-search include to define the default search fields. This follow-up adds preferred_name into the default fields in that include now the the module has been removed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #130002|0 |1 is obsolete| | --- Comment #35 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 133449 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133449&action=edit Bug 28633: DO NOT PUSH Schema Changes Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #36 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Created attachment 133450 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133450&action=edit Bug 28633: (QA follow-up) Add preferred_name to ysearch This adds preferred_name to the search fields in the autocomplete search system. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off --- Comment #37 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- This is mostly a rebase taking into account bug 29695 and bug 30063. I also added a QA follow-up to allow searching on the preferred name in the autocomplete searches. I'm not entirely sure about the complete replacement of firstname with preferred_name everywhere.. it can lead to confusion in a few places as Katrin suggests... with the discussion on bug 21978 which lead to me opening bug 30568 I think this could play a bigger part here too. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #38 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133451 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133451&action=edit Bug 28633: (follow-up) Display effective name in JS search Also I fix the other header search, and ensure the 'Standard' option wil appear in dropdowns -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #39 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #30)
1) Tiny typo + description: patron's preferred named
I am not sure where you are referring to
2) Patron search results
In patron search results I still see the "firstname" instead of the "preferred name".
Fixed
This seems a little confusing, as this is the only place now showing the firstname. On the other hand, if someone presents an ID and I want to search forthem, I will need to make the connection. Maybe we could display the preferred name additionally to the firstname somehow?
Preferred name is meant to be stronger than 'othernames' - it is how the patron wants to be addressed - I think in the case where there is a difference with an ID they will tell you which name to expect
3) Auto-complete for patrons
When I type "Cait" the entry doesn't show, only when I type "Katrin". But in the preview, it shows 'Cait' ... So there is a mismatch with what you need to type and what will show.
Martin fixed this
I am not sure how to resolve this, but maybe you have an idea or can explain reasoning?
As above, the idea is that a preferred name is intended to the name a patron wants to be called. It is the case where the patron is not using their first name, but may still legally have that name. If a patron is using a nickname, that would be 'othernames' -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #40 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- (In reply to Nick Clemens from comment #39)
(In reply to Katrin Fischer from comment #30)
1) Tiny typo + description: patron's preferred named
I am not sure where you are referring to
I fixed it inline 'named -> name' -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Patch doesn't apply --- Comment #41 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Can you please rebase? Careful with the first conflict - h3 changed to h1 in master and the section was moved a little downwards. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133445|0 |1 is obsolete| | --- Comment #42 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133958 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133958&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133446|0 |1 is obsolete| | --- Comment #43 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133959 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133959&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133447|0 |1 is obsolete| | --- Comment #44 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133960 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133960&action=edit Bug 28633: (follow-up) Account for bug 29695 changes During rebase of this patchset we drop the columns.def and borrowers.json changes introduced. We store this mapping in the module now, so this patch does that. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133448|0 |1 is obsolete| | --- Comment #45 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133961 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133961&action=edit Bug 28633: (follow-up) Account for changes with bug 30063 Bug 30063 removes the C4/Utils/DataTables/Members.pm module and instead uses the API and a patron-search include to define the default search fields. This follow-up adds preferred_name into the default fields in that include now the the module has been removed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133450|0 |1 is obsolete| | --- Comment #46 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133962 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133962&action=edit Bug 28633: (QA follow-up) Add preferred_name to ysearch This adds preferred_name to the search fields in the autocomplete search system. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133451|0 |1 is obsolete| | --- Comment #47 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133963 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133963&action=edit Bug 28633: (follow-up) Display effective name in JS search Also I fix the other header search, and ensure the 'Standard' option wil appear in dropdowns -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133449|0 |1 is obsolete| | --- Comment #48 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133964 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133964&action=edit Bug 28633: DO NOT PUSH Schema Changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #49 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 133965 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133965&action=edit Bug 28633: Fix ysearch sorting This adds an IF conditional to the sorting to sort by preferred name or firstname I add the colmns to data for main patron searhc, but I cannot solve sorting there -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #50 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Sorting in the patron search results is a little off: I have: Katrin Fischer Katrina Fischer Cait Fischer (where Cait is preferred name) I think the last should be the first entry? Otherwise all fixes from last testing appear to be ok. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Juliet Heltibridle <jheltibridle@rcplib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jheltibridle@rcplib.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #51 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Should/can we revive this one? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Laura Escamilla <Laura.escamilla@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Laura.escamilla@bywatersolu | |tions.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katie Bliss <kebliss@dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss@dmpl.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Suzanne <smhodson123extra@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smhodson123extra@yahoo.com --- Comment #52 from Suzanne <smhodson123extra@yahoo.com> --- Wow! There has been a lot of work on this! We are interested in being able to have the patron record show "Preferred Name" in quotation marks in the first position followed by first and middle names and then last name. So, for example, it might show as "Sammy" Suzanne Michelle Hodson, with everything being searchable and all showing up on the patron record side bar. My idea would be to let registering patrons fill in the first and middle name field and also the preferred name field and have them show up in that order on Koha, or let libraries choose how they would like the names to show up or whether to have them hidden, if that is possible. Thanks for the great efforts on this! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 hebah@bywatersolutions.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hebah@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #53 from David Cook <dcook@prosentient.com.au> --- (In reply to Katrin Fischer from comment #51)
Should/can we revive this one?
I still have people asking for this, so it would be great to see it make it. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133958|0 |1 is obsolete| | Attachment #133959|0 |1 is obsolete| | Attachment #133960|0 |1 is obsolete| | Attachment #133961|0 |1 is obsolete| | Attachment #133962|0 |1 is obsolete| | Attachment #133963|0 |1 is obsolete| | Attachment #133964|0 |1 is obsolete| | Attachment #133965|0 |1 is obsolete| | --- Comment #54 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 166792 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166792&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #55 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 166793 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166793&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #56 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 166794 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166794&action=edit Bug 28633: DO NOT PUSH Schema changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #57 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #50)
Sorting in the patron search results is a little off:
I have:
Katrin Fischer Katrina Fischer Cait Fischer (where Cait is preferred name)
I think the last should be the first entry?
Otherwise all fixes from last testing appear to be ok.
I still cannot fix this - patrons without a preferred_name sort before those with one - we need some sort of conditional or function to make this sort correctly afaict, and I can't seem to make that work. If someone with more datatables or API knowledge can help I'd appreciate it. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #58 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Nick Clemens (kidclamp) from comment #57)
(In reply to Katrin Fischer from comment #50)
Sorting in the patron search results is a little off:
I have:
Katrin Fischer Katrina Fischer Cait Fischer (where Cait is preferred name)
I think the last should be the first entry?
Otherwise all fixes from last testing appear to be ok.
I still cannot fix this - patrons without a preferred_name sort before those with one - we need some sort of conditional or function to make this sort correctly afaict, and I can't seem to make that work. If someone with more datatables or API knowledge can help I'd appreciate it.
Thanks for checking Nick. I think what was I was thinking is if we could create a sortable string like it works for dates and similar that matches the display format. But I have no idea how this works in detail. Before we give up on the idea, maybe we could get some more eyes on it. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|Trivial patch |Small patch Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #166792|0 |1 is obsolete| | Attachment #166793|0 |1 is obsolete| | Attachment #166794|0 |1 is obsolete| | --- Comment #59 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 166813 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166813&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #60 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 166814 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166814&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #61 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 166815 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166815&action=edit Bug 28633: DO NOT PUSH Schema changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #62 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 166816 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166816&action=edit Bug 28633: (QA follow-up) Minor style change in dbrev Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #63 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 166817 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166817&action=edit Bug 28633: Make 'effective_name' embeddable This patch makes the calculated value of `Koha::Patron->effective_name` embeddable in the patrons routes. To test: 1. Apply this patch 2. Run: $ ktd --shell k$ prove t/db_dependent/api/v1/patrons.t => SUCCESS: Tests pass! 3. Sign off :-D Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #64 from Andrew Fuerste-Henry <andrewfh@dubcolib.org> --- We should not copy preferred name when duplicating a patron, just as we do not copy over first name. I'm very much tempted to Fail QA on this due to the search results sorting issue. When looking at a mis-sort of three patrons with the name last name it seems like a manageable speed bump, but I'm concerned about the impact on searching within a larger patron base. If any patron with a preferred name is inherently harder to find than a patron without a preferred name, then patrons with preferred names present a burden that staff may come to resent. I may be overthinking this. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Andrew Fuerste-Henry <andrewfh@dubcolib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #65 from Andrew Fuerste-Henry <andrewfh@dubcolib.org> --- After soliciting some more opinions, I am marking this FQA for the search results issue. Inaccurate sorting of patrons by name will cause too much confusion for thi to be usable. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #66 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Andrew Fuerste-Henry from comment #65)
After soliciting some more opinions, I am marking this FQA for the search results issue. Inaccurate sorting of patrons by name will cause too much confusion for thi to be usable.
Hi Andrew, thanks for doing that - asking around. I still hope that the sorting is a solvable issue. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #67 from Andrew Fuerste-Henry <andrewfh@dubcolib.org> --- (In reply to Katrin Fischer from comment #66)
Hi Andrew, thanks for doing that - asking around. I still hope that the sorting is a solvable issue.
Strong agree, I'm very much in favor of this feature and would love to see it move forward! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #68 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- I feel like this should be possible.. there's various 'IS NULL' sorting options in SQL to allow us to set whether we get NULL first or last in sort ordering.. The challenge I see is working out how to expose that via the API.. or do we just hard code somewhere a different default for null sorts? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Lisette Scheer <lisette.scheer@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette.scheer@bywatersolut | |ions.com --- Comment #69 from Lisette Scheer <lisette.scheer@bywatersolutions.com> --- Could sort be based on effective_name? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #70 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 167163 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=167163&action=edit Bug 28633: DO NOT PUSH - Schema changes for sort_name -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #71 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 167164 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=167164&action=edit Bug 28633: POC - Add sort_name for patron This is just a possible solution, add a new "sort" name for patrons - we could expand the calculations here if needed, but essentially we just store the effective name, making it available for SQL sorting -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #72 from Andrew Fuerste-Henry <andrewfh@dubcolib.org> --- Sorting almost works correctly with these patches. The following three patrons show up in this order in a default patron search (ascending name sort): - surname: Acevedo, preferred_name: [blank], firstname: Hank - surname: Acevedo, preferred_name: [blank], firstname: Henry - surname: Acevedo, preferred_name: [blank], firstname: Hosea When I added a preferred_name I got: - surname: Acevedo, preferred_name: Angel, firstname: Henry - surname: Acevedo, preferred_name: [blank], firstname: Hank - surname: Acevedo, preferred_name: [blank], firstname: Hosea And then with a second preferred_name: - surname: Acevedo, preferred_name: Angel, firstname: Henry - surname: Acevedo, preferred_name: [blank], firstname: Hosea - surname: Acevedo, preferred_name: Zeus, firstname: Hank BUT things go weird if preferred_name is NULL -- in KTD the default data has preferred_name null but saves new/edited patrons with a blank instead. In the real world, I imagine patrons could be imported with a NULL value. With NULL preferred_names I get: - surname: Acevedo, preferred_name: NULL, firstname: Henry - surname: Acevedo, preferred_name: NULL, firstname: Hosea - surname: Acevedo, preferred_name: NULL, firstname: Hank -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #73 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- (In reply to Andrew Fuerste-Henry from comment #72)
BUT things go weird if preferred_name is NULL -- in KTD the default data has preferred_name null but saves new/edited patrons with a blank instead. In the real world, I imagine patrons could be imported with a NULL value. With NULL preferred_names I get:
- surname: Acevedo, preferred_name: NULL, firstname: Henry - surname: Acevedo, preferred_name: NULL, firstname: Hosea - surname: Acevedo, preferred_name: NULL, firstname: Hank
I originally thought we could simply add a default value - however, TEXT columns cannot have a default value in MySQL - MariaDB does allow this Either we need to supply the default on storing - or build and internal functions - OR make sort_name a VARCHAR, but it would be storing a longtext so would be problematic - I am not sure why name fields are longtext This may mean sort_name is a unacceptable solution -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov --- Comment #74 from Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> --- Andrew, how are you setting the preferred_names to NULL in your last example? I'm wondering if it's the NULLs per se that are causing the issue, or if the problem is that sort_name isn't getting updated. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #75 from Andrew Fuerste-Henry <andrewfh@dubcolib.org> --- (In reply to Emily Lamancusa from comment #74)
Andrew, how are you setting the preferred_names to NULL in your last example? I'm wondering if it's the NULLs per se that are causing the issue, or if the problem is that sort_name isn't getting updated.
I don't believe there is a way to use the GUI to either create a patron with a NULL preferred name or edit a patron to have one. I believe patron imports are the only way to get a NULL. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #76 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- I think only patron imports directly into the DB and not via any of the Koha tools is the only way this can happen. Personally.. I actually think this is OK for now.. perhaps a scripts to 'fix sort_name' inconsistencies down the line or even a little warning in the about page. But personally I don't think we should hold this bug back any longer? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia@bugs.koha-communit |martin.renvoize@ptfs-europe |y.org |.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #77 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Bear with me if this has been asked before, but do we really need the additional database column? Could we not create it somehow "virtually". I was thinking of something like in SQL: SELECT COALESCE (preferredname, ... ) ? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #78 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Something like `ORDER BY COALESCE(NULLIF(preferred_name, ''), first_name), last_name` you mean? We'll still need to work out how to wrap that for the API... -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #79 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Martin Renvoize from comment #78)
Something like `ORDER BY COALESCE(NULLIF(preferred_name, ''), first_name), last_name` you mean?
We'll still need to work out how to wrap that for the API...
Yes, because I think having it as a real database column might add some technical debt/more stuff to maintain. If we could avoid it with reasonable effort that might be nice. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #80 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #79)
(In reply to Martin Renvoize from comment #78)
Something like `ORDER BY COALESCE(NULLIF(preferred_name, ''), first_name), last_name` you mean?
We'll still need to work out how to wrap that for the API...
Yes, because I think having it as a real database column might add some technical debt/more stuff to maintain. If we could avoid it with reasonable effort that might be nice.
It's the combination of API and Datatables here that I was unable to resolve - the query is being bult by datatables, so I think we would need to intercept the sorting column in the API and convert it to the SQL we need. IMO the column simplifies the code we need in the end, but am happy to see if someone else can solve the API issue -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #81 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- As a new feature we have a little bit more time for this one. Let's try and think it over one more time to see if we have missed something that could make things a little easier. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #82 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- It has been coded and working through issues wince 2021... we can't sit at 'perfect it more' forever ;P That said.. I'll take a look and see if there's a way we can overload at the dbic level for sorting -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #83 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I didn't mean weeks - just a few days, maybe to the end of the week? See if we can find some more brains to pick for an idea. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #84 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- This 'might' be achievable with an extension to the query_fixer stuff. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|martin.renvoize@ptfs-europe | |.com | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #85 from Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> --- Maybe time to come back to this one, and work on API improvements in a separate bug? :) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #166813|0 |1 is obsolete| | Attachment #166814|0 |1 is obsolete| | Attachment #166815|0 |1 is obsolete| | Attachment #166816|0 |1 is obsolete| | Attachment #166817|0 |1 is obsolete| | Attachment #167163|0 |1 is obsolete| | Attachment #167164|0 |1 is obsolete| | --- Comment #86 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173628 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173628&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #87 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173629 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173629&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #88 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173630 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173630&action=edit Bug 28633: DO NOT PUSH Schema changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #89 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173631 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173631&action=edit Bug 28633: (QA follow-up) Minor style change in dbrev Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #90 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173632 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173632&action=edit Bug 28633: Make 'effective_name' embeddable This patch makes the calculated value of `Koha::Patron->effective_name` embeddable in the patrons routes. To test: 1. Apply this patch 2. Run: $ ktd --shell k$ prove t/db_dependent/api/v1/patrons.t => SUCCESS: Tests pass! 3. Sign off :-D Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #91 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173633 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173633&action=edit Bug 28633: POC - Add sort_name for patron This is just a possible solution, add a new "sort" name for patrons - we could expand the calculations here if needed, but essentially we just store the effective name, making it available for SQL sorting -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #92 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173634 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173634&action=edit Bug 28633: DO NOT PUSH: Schema changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #93 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Rebased, I am happy to have anyone else try to work on query fixer, but I think this works in the large sense and can be improved in the future -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173628|0 |1 is obsolete| | --- Comment #94 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173664 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173664&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173629|0 |1 is obsolete| | --- Comment #95 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173665 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173665&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. Additionally it adds a method 'effective_name' to choose the preferred name if present and fall back to firstname The 'firstname' is displayed as 'First name' on the details page, with id/class patron_first_name to allow ajusting via JS/CSS if library wants to highlight/hide the non-preferred name PatronAutoComplete/ysearch is updated to use 'effective_name' method To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173630|0 |1 is obsolete| | --- Comment #96 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173666 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173666&action=edit Bug 28633: DO NOT PUSH Schema changes Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173631|0 |1 is obsolete| | --- Comment #97 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173667 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173667&action=edit Bug 28633: (QA follow-up) Minor style change in dbrev Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173632|0 |1 is obsolete| | --- Comment #98 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173668 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173668&action=edit Bug 28633: Make 'effective_name' embeddable This patch makes the calculated value of `Koha::Patron->effective_name` embeddable in the patrons routes. To test: 1. Apply this patch 2. Run: $ ktd --shell k$ prove t/db_dependent/api/v1/patrons.t => SUCCESS: Tests pass! 3. Sign off :-D Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173633|0 |1 is obsolete| | --- Comment #99 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173669 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173669&action=edit Bug 28633: POC - Add sort_name for patron This is just a possible solution, add a new "sort" name for patrons - we could expand the calculations here if needed, but essentially we just store the effective name, making it available for SQL sorting Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173634|0 |1 is obsolete| | --- Comment #100 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173670 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173670&action=edit Bug 28633: DO NOT PUSH: Schema changes Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #101 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Testing notes: 2 - Update database and restart all, clear browser cache Also need to do a yarn build before restarting; otherwise attempting any patron search will throw an ajax error that preferred_name and sort_name are not allowed. Auto-complete should also use sort_name - it still seems to be sorting by firstname. (Not a blocker) Duplicating a patron shouldn't carry over the original patron's preferred name, but currently it does. (Not a blocker) I also tested searching and patron imports since those were a sticking point previously, using the same data from #c72 (including importing patrons with no preferred name using Koha's import patron tool), and all the sorts worked correctly. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173664|0 |1 is obsolete| | Attachment #173665|0 |1 is obsolete| | Attachment #173666|0 |1 is obsolete| | Attachment #173667|0 |1 is obsolete| | Attachment #173668|0 |1 is obsolete| | Attachment #173669|0 |1 is obsolete| | Attachment #173670|0 |1 is obsolete| | --- Comment #102 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173717 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173717&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def and sets preferred name to firstname -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #103 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173718 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173718&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. On storage (creation or update) the preferred_name is set to the firstname if no value is passed. Patron modifications will set the preferred name to the firstname if the preferred_name field is hidden With this patchset preferred_name will always be set - either to the firstname, or a specified value. PatronAutoComplete/ysearch is updated to use 'preferred_name' To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview 16 - Set 'preferred_name' in all 'Unwanted' preferences 17 - Confirm editing a patron in staff interface sets both fields when firstname updated 18 - Confirm a patron modification sets both fields when firstname updated 19 - Create a patron / perform self registration and confirm both fields set when preferred_name is hidden 20 - Remove preferred_name from Unwanted prefs and confirm preferred_name is set to firstname if nothing passed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #104 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173719 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173719&action=edit Bug 28633: DO NOT PUSH - Schema changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #105 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- New patches based on feedback from Martin - removed effective_name and sort_name in favor of setting preferred_name from firstname if not defined When the field is hidden, it should be largely invisible to users, except in action log changes When visible - it will always be set, so may be duplicated for patrons with no preferred name, but I think it is better to be obvious than to hide what is happening. Patron displays will always use preferred_name, only on patron details/etc would you see both -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #106 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Testing notes: after applying patch and running updatedatabase, also need to run yarn build, then restart_all The test plan works and sorting works as expected, both in auto-complete and in the results table, including with patrons that were added using Koha's patron import tool. However, there is one blocker for me with this version - I think the way the feature is functionally enabled/disabled based on the collective settings of all 3 of the Unwanted prefs is going to be very confusing to users. It is especially an issue that adding preferred_name to all 3 Unwanted prefs will cause existing preferred_name data to be overwritten piecemeal, as patrons happen to get edited for any reason, without warning that this will happen. At the very least, there needs to be a clear warning in the description of each of the Unwanted prefs stating that if preferred_name is marked unwanted in all 3, that existing preferred_name data will be overwritten as patrons are edited. Personally, I think the best solution would be for the first name to overwrite the preferred_name if and only if (preferred_name eq firstname or preferred_name is empty), regardless of how the Unwanted prefs are set. As far as I know, all other fields retain their data unless explicitly deleted, even if they're fully hidden, so I think that behavior would be fine in this case, too. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173717|0 |1 is obsolete| | Attachment #173718|0 |1 is obsolete| | Attachment #173719|0 |1 is obsolete| | --- Comment #107 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173813 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173813&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def and sets preferred name to firstname -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #108 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173814 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173814&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. On storage (creation or update) the preferred_name is set to the firstname if no value is passed. Patron modifications will set the preferred name to the firstname if the preferred_name field is hidden With this patchset preferred_name will always be set - either to the firstname, or a specified value. PatronAutoComplete/ysearch is updated to use 'preferred_name' To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview 16 - Set 'preferred_name' in all 'Unwanted' preferences 17 - Confirm editing a patron in staff interface sets both fields when firstname updated 18 - Confirm a patron modification sets both fields when firstname updated 19 - Create a patron / perform self registration and confirm both fields set when preferred_name is hidden 20 - Remove preferred_name from Unwanted prefs and confirm preferred_name is set to firstname if nothing passed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #109 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173815 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173815&action=edit Bug 28633: DO NOT PUSH - Schema changes -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #110 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 173816 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173816&action=edit Bug 28633 (follow-up) Add note about disabling/hiding preferred name to sysprefs -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173813|0 |1 is obsolete| | --- Comment #111 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173826 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173826&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def and sets preferred name to firstname Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173814|0 |1 is obsolete| | --- Comment #112 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173827 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173827&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. On storage (creation or update) the preferred_name is set to the firstname if no value is passed. Patron modifications will set the preferred name to the firstname if the preferred_name field is hidden With this patchset preferred_name will always be set - either to the firstname, or a specified value. PatronAutoComplete/ysearch is updated to use 'preferred_name' To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview 16 - Set 'preferred_name' in all 'Unwanted' preferences 17 - Confirm editing a patron in staff interface sets both fields when firstname updated 18 - Confirm a patron modification sets both fields when firstname updated 19 - Create a patron / perform self registration and confirm both fields set when preferred_name is hidden 20 - Remove preferred_name from Unwanted prefs and confirm preferred_name is set to firstname if nothing passed Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173815|0 |1 is obsolete| | --- Comment #113 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173828 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173828&action=edit Bug 28633: DO NOT PUSH - Schema changes Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #114 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- Created attachment 173829 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173829&action=edit Bug 28633: (follow-up) Add note about disabling/hiding preferred name to sysprefs Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173816|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38317 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38317 [Bug 38317] Support hiding preferred_name from patron modification screen on OPAC but not staff client (or vice versa) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173826|0 |1 is obsolete| | --- Comment #115 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173930 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173930&action=edit Bug 28633: DB update This adds the field to necessary tables and updates API and columns def and sets preferred name to firstname Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173827|0 |1 is obsolete| | --- Comment #116 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173931 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173931&action=edit Bug 28633: Add preferred name field to patrons This patch adds a new field 'preferred_name' to the patron record. On storage (creation or update) the preferred_name is set to the firstname if no value is passed. Patron modifications will set the preferred name to the firstname if the preferred_name field is hidden With this patchset preferred_name will always be set - either to the firstname, or a specified value. PatronAutoComplete/ysearch is updated to use 'preferred_name' To test: 1 - Apply patches 2 - Update database and restart all, clear browser cache 3 - Load a patron in staff module 4 - Confirm you see and can add a preferred name 5 - Confirm the preferred name and first name now displays on patron details 6 - Remove first name from patron record and confirm it no longer shows 7 - Edit sysprefs BorrowerMandatoryFields and BorrowerUnwantedFields to confirm you can make new field required or hidden 8 - Sign in as patron to opac 9 - Confirm preferred name shows 10 - Edit account on opac and confirm field is present 11 - Verify DefaultPatronSearchFields contains 'preferredname' if your pref had firstname 12 - Perform checkout and patron search using preferred_name, confirm patron is found 13 - Enable PatronAutoComplete system preference 14 - Type patron's surname into Checkout or patron search but don't hit enter 15 - Confirm patron is displayed with 'preferred_name' in the preview 16 - Set 'preferred_name' in all 'Unwanted' preferences 17 - Confirm editing a patron in staff interface sets both fields when firstname updated 18 - Confirm a patron modification sets both fields when firstname updated 19 - Create a patron / perform self registration and confirm both fields set when preferred_name is hidden 20 - Remove preferred_name from Unwanted prefs and confirm preferred_name is set to firstname if nothing passed Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173828|0 |1 is obsolete| | --- Comment #117 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173932 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173932&action=edit Bug 28633: DO NOT PUSH - Schema changes Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173829|0 |1 is obsolete| | --- Comment #118 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173933 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173933&action=edit Bug 28633: (follow-up) Add note about disabling/hiding preferred name to sysprefs Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #119 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173934 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173934&action=edit Bug 28633: DBIC Schema Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #120 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173935 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173935&action=edit Bug 28633: (QA follow-up) Tidy Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #121 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 173936 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173936&action=edit Bug 28633: (QA follow-up) Fix test plans Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA --- Comment #122 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Some odd rebase issues, but I fixed those in QA follow-ups. All looking great here, thanks for all the work Nick. Passing QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #123 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- This is going to break selenium tests, please fix ASAP. t/db_dependent/selenium/patrons_search.t -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|Manual |additional_work_needed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #124 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, I am going to push this anyway, but: 1) Tests need to be fixed. (blocker) 2) I would prefer a follow-up that hid this field for updating installations. As we show in the OPAC this would make it less disruptive. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to main Version(s)| |24.11.00 released in| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #125 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Pushed for 24.11! Well done everyone, thank you! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #126 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 174419 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174419&action=edit Bug 28633: (follow-up) Set preferred name and adjust counts for tests -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Tomás Cohen Arazi (tcohen) <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #174419|0 |1 is obsolete| | --- Comment #127 from Tomás Cohen Arazi (tcohen) <tomascohen@gmail.com> --- Created attachment 174420 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174420&action=edit Bug 28633: (follow-up) Set preferred name and adjust counts for tests Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #128 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Picked follow-up for main: Bug 28633: (follow-up) Set preferred name and adjust counts for tests -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #129 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, with the patch applied the test doesn't pass yet. I have: Running tests (1) * Proving /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t KO! STRACE: /usr/share/perl5/Try/Tiny.pm:123 in Selenium::Remote::Driver::catch {...} /usr/share/perl5/Selenium/Remote/Driver.pm:361 in Try::Tiny::try (eval 2045):1 in Selenium::Remote::Driver::__ANON__ (eval 2047):2 in Selenium::Remote::Driver::__ANON__ (eval 2019):17 in Selenium::Remote::Driver::_execute_command /usr/share/perl5/Selenium/Remote/WebElement.pm:260 in Selenium::Remote::WebElement::_execute_command /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t:430 in Selenium::Remote::WebElement::clear /usr/share/perl/5.36/Test/Builder.pm:374 in main::__ANON__ /usr/share/perl/5.36/Test/Builder.pm:374 in (eval) /usr/share/perl/5.36/Test/More.pm:809 in Test::Builder::subtest /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t:463 in Test::More::subtest /usr/share/perl/5.36/Test/Builder.pm:374 in main::__ANON__ /usr/share/perl/5.36/Test/Builder.pm:374 in (eval) /usr/share/perl/5.36/Test/More.pm:809 in Test::Builder::subtest /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t:467 in Test::More::subtest # Looks like you planned 7 tests but ran 1. # Failed test 'filter by date of birth' # at /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t line 463. # Looks like you failed 1 test of 28. # Failed test 'Search patrons' # at /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t line 467. Error while executing command: stale element reference: The element reference of <input type="text"> is stale; either the element is no longer attached to the DOM, it is not in the current frame context, or the document has been refreshed at /usr/share/perl5/Selenium/Remote/Driver.pm line 411. at /usr/share/perl5/Selenium/Remote/Driver.pm line 356. # Looks like your test exited with 11 just after 1. /kohadevbox/koha/t/db_dependent/selenium/patrons_search.t .. Dubious, test returned 11 (wstat 2816, 0xb00) Failed 2/2 subtests -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #130 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- I don't believe those come from this - it's unrelated code, Tomas is looking -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@gmail.com --- Comment #131 from Jonathan Druart <jonathan.druart@gmail.com> --- I am on it. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #132 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 174472 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174472&action=edit Bug 28633: Fix patrons_search.t This does not belong here, but raised to me here, so attaching on this one. This feels like it's coming from bug 33484, but those tests were passing after it has been pushed. This patch fixes the following error: Error while executing command: stale element reference: The element reference of <input type="text"> is stale; either the element is no longer attached to the DOM, it is not in the current frame context, or the document has been refreshed at /usr/share/perl5/Selenium/Remote/Driver.pm line 411. Since bug 33484 the row with the filters is redrawn on table redraw. So we need to search for the input every time the table is redrawn. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|additional_work_needed | --- Comment #133 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Picked the last patch "Fix patrons_search.t" for main. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the| |This patch adds a new release notes| |column to the borrowers | |table, 'preferred_name'. | |This will be visible in | |staff and opac patron | |information forms by | |default. This column takes | |precedence in display and | |will show where patrons are | |displayed throughout Koha. | |If not populated or field | |is hidden, the firstname | |will be copied into the | |preferred_name field fir | |display. Use of 'firstname' | |in notices and other | |templates will continue to | |display the firstname, | |switching to | |'preferred_name' will | |display the new field. | |When | |hiding this field, it | |should be hidden in all | |interfaces to avoid any | |discrepancies or confusion. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add a preferred_name field |Add a preferred_name field |and an effective_name |to patrons |method to patrons | Keywords|release-notes-needed | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |new feature -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add a preferred_name field |Add a preferred name field |to patrons |to patrons -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the|This patch adds a new |This patch adds a new release notes|column to the borrowers |column to the borrowers |table, 'preferred_name'. |table, 'preferred_name'. |This will be visible in |This will be visible in |staff and opac patron |staff and OPAC patron forms |information forms by |by default. This column |default. This column takes |takes precedence in display |precedence in display and |and will show where patrons |will show where patrons are |are displayed throughout |displayed throughout Koha. |Koha. If not populated or |If not populated or field |field is hidden, the first |is hidden, the firstname |name will be copied into |will be copied into the |the preferred name field |preferred_name field fir |for display. Use of |display. Use of 'firstname' |'firstname' in notices and |in notices and other |other templates will |templates will continue to |continue to display the |display the firstname, |first name, switching to |switching to |'preferred_name' will |'preferred_name' will |display the new field. |display the new field. |When |When |hiding this field, it |hiding this field, it |should be hidden in all |should be hidden in all |interfaces to avoid any |interfaces to avoid any |discrepancies or confusion. |discrepancies or confusion. | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas@bywatersolutions.com Status|Pushed to main |Needs documenting --- Comment #134 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- New feature, no 24.05.x backport. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@davidnind.com Text to go in the|This patch adds a new |This new feature adds a new release notes|column to the borrowers |"Preferred name" field to |table, 'preferred_name'. |patron information. This is |This will be visible in |visible in staff and OPAC |staff and OPAC patron forms |patron forms by default. |by default. This column | |takes precedence in display |Notes: |and will show where patrons |1. The "Preferred |are displayed throughout |name" field takes |Koha. If not populated or |precedence, and is |field is hidden, the first |displayed where patron |name will be copied into |names are displayed |the preferred name field |throughout Koha. |for display. Use of |2. If the |'firstname' in notices and |"Preferred name" field has |other templates will |no value, or it is hidden, |continue to display the |the first name will be |first name, switching to |displayed. |'preferred_name' will |3. Notices: Use |display the new field. |of 'firstname' in notices |When |and other templates will |hiding this field, it |continue to display the |should be hidden in all |first name, using |interfaces to avoid any |'preferred_name' will |discrepancies or confusion. |display the patron's | |preferred name. | |4. Hiding | |fields: When hiding this | |field, it should be hidden | |in all interfaces to avoid | |any discrepancies or | |confusion | |(BorrowerUnwantedField, | |PatronSelfModificationBorro | |werUnwantedField, | |PatronSelfRegistrationBorro | |werUnwantedField, | |PatronSelfModificationManda | |toryField, | |PatronSelfRegistrationBorro | |werMandatoryField). -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the|This new feature adds a new |This new feature adds a new release notes|"Preferred name" field to |"Preferred name" field to |patron information. This is |patron information. This is |visible in staff and OPAC |visible in staff and OPAC |patron forms by default. |patron forms by default. | | |Notes: |Notes: |1. The "Preferred |1. The "Preferred |name" field takes |name" field takes |precedence, and is |precedence, and is |displayed where patron |displayed where patron |names are displayed |names are displayed |throughout Koha. |throughout Koha. |2. If the |2. If the |"Preferred name" field has |"Preferred name" field has |no value, or it is hidden, |no value, or it is hidden, |the first name will be |the first name is |displayed. |displayed. |3. Notices: Use |3. Notices: Use |of 'firstname' in notices |of 'firstname' in notices |and other templates will |and other templates will |continue to display the |continue to display the |first name, using |first name. Use |'preferred_name' will |'preferred_name' to display |display the patron's |the patron's preferred |preferred name. |name. |4. Hiding |4. Hiding fields: |fields: When hiding this |When hiding the preferred |field, it should be hidden |name field, hide it in all |in all interfaces to avoid |interfaces to avoid any |any discrepancies or |discrepancies or confusion |confusion |(BorrowerUnwantedField, |(BorrowerUnwantedField, |PatronSelfModificationBorro |PatronSelfModificationBorro |werUnwantedField, |werUnwantedField, |PatronSelfRegistrationBorro |PatronSelfRegistrationBorro |werUnwantedField, |werUnwantedField, |PatronSelfModificationManda |PatronSelfModificationManda |toryField, |toryField, |PatronSelfRegistrationBorro |PatronSelfRegistrationBorro |werMandatoryField). |werMandatoryField). |5. | |Patron autocomplete: Add or | |remove fields to search | |using the | |DefaultPatronSearchFields | |system preference - if your | |current installation uses | |firstname, then this should | |automatically be updated to | |include preferred_name (and | |is in the default settings | |for new installations). --- Comment #135 from David Nind <david@davidnind.com> --- See the chat discussion about the sample data used by KTD - it is currently only displaying the surname in patron search results, patron page, and wherever the patron name is displayed in Koha. Chat discussion: https://chat.koha-community.org/koha-community/pl/xqhc3c8g7tdu38fyp971z4oiqa I'm also unsure about patron autocomplete and DefaultPatronSearchFields in KTD, as it doesn't include preferred_name by default when it is started up. The assumption is that the database update will take care of things for existing installations, unless I have misunderstood: - Preferred name field added to patron information - Patron autocomplete: preferred_name added to DefaultPatronSearchFields -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #136 from Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> --- Created attachment 175177 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=175177&action=edit Bug 28633: (follow-up) Update sample data with preferred_name This patch updates the sample_date, as used in koha-testing-docker, with the new preferred_name field. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs documenting |Pushed to main -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Martin Renvoize (ashimema) <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |additional_work_needed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #137 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Could you move the patch to a separate bug please? Only reason: that way I don't need to remember to remove this "new feature" form release notes for 25.05 manually in 6 months :) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #138 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Katrin Fischer from comment #137)
Could you move the patch to a separate bug please? Only reason: that way I don't need to remember to remove this "new feature" form release notes for 25.05 manually in 6 months :)
... or I will do it in a few mins. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38622 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38622 [Bug 38622] Fix Koha sample data to include preferred_name -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38623 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38623 [Bug 38623] Suggestion management page does not show preferred name -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #139 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Katrin Fischer from comment #138)
(In reply to Katrin Fischer from comment #137)
Could you move the patch to a separate bug please? Only reason: that way I don't need to remember to remove this "new feature" form release notes for 25.05 manually in 6 months :)
... or I will do it in a few mins.
Moved to bug 38622. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to main Keywords|additional_work_needed | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38734 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38734 [Bug 38734] Default notice templates should use preferred_name -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38735 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38735 [Bug 38735] New installations should include preferred_name in DefaultPatronSearchFields by default -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |Needs documenting --- Comment #140 from David Nind <david@davidnind.com> --- Changed status back to needs documenting - this is an enhancement, and changes the interface. So changes to the manual are required, including screenshots. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Cheryl <clackman@fargolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clackman@fargolibrary.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #141 from Jonathan Druart <jonathan.druart@gmail.com> --- "First name" is displayed on the patron detail page, but it's confusing, see https://chat.koha-community.org/koha-community/pl/6rza7668wby6mpodr8anhr9tre A solution would be to display it only if different than the preferred name (there is a diff suggested in the thread) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |inkeri.hakulinen+bugz@helsi | |nki.fi -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |39245 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39245 [Bug 39245] Preferred name should give option to replace more than first name -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |40484 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40484 [Bug 40484] Add a way for staff to view firstname in patron search results -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Fridolin Somers <fridolin.somers@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |39576 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39576 [Bug 39576] 'Last patron' results should display preferred name -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #142 from David Cook <dcook@prosentient.com.au> --- This change doesn't play so nicely with older third-party tools... The logic on which name to display when/where is a bit weird and can lead to no first name or preferred name showing anywhere but c'est la vie. I'll figure something out... -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Kalle Karlsson <kalle@imcode.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kalle@imcode.com --- Comment #143 from Kalle Karlsson <kalle@imcode.com> --- We've encountered an issue with this in one of our clients Koha instances. They have an automatic import of borrowers set up. For some borrowers, borrowers.preferred_name is not filled in. Hence, in the GUI only the surname is shown. If they manually save the record this is resolved. Naturally, the problem does not occur if they created the borrower manually. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Blou <philippe.blouin@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |philippe.blouin@inlibro.com --- Comment #144 from Blou <philippe.blouin@inlibro.com> --- (In reply to Kalle Karlsson from comment #143)
We've encountered an issue with this in one of our clients Koha instances. They have an automatic import of borrowers set up. For some borrowers, borrowers.preferred_name is not filled in.
We have the same issue. It's very problematic to our users, a lot of institutions use "automated updates". We can't go through all of them to change that. For reference, here's joubu's diff. We probably will open a new bz diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt index 5f592679263..b30904e1a26 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt @@ -134,7 +134,7 @@ <div class="rows"> <ol> - [% IF ( patron.preferred_name && patron.firstname ) %] + [% IF ( patron.preferred_name && patron.firstname && patron.preferred_name != patron.firstname) %] <li id="patron_first_name"> <span class="label patron_first_name">First name: </span> [% patron.firstname | html %] -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |41780 See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41780 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41780 [Bug 41780] Show firstname if preferred_name is empty in moremember.tt -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |39587 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39587 [Bug 39587] Patron surname missing from contact information list on patron details tab -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #145 from David Cook <dcook@prosentient.com.au> --- (In reply to Blou from comment #144)
(In reply to Kalle Karlsson from comment #143)
We've encountered an issue with this in one of our clients Koha instances. They have an automatic import of borrowers set up. For some borrowers, borrowers.preferred_name is not filled in.
We have the same issue. It's very problematic to our users, a lot of institutions use "automated updates". We can't go through all of them to change that.
For reference, here's joubu's diff. We probably will open a new bz
diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt index 5f592679263..b30904e1a26 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt @@ -134,7 +134,7 @@
<div class="rows"> <ol> - [% IF ( patron.preferred_name && patron.firstname ) %] + [% IF ( patron.preferred_name && patron.firstname && patron.preferred_name != patron.firstname) %] <li id="patron_first_name"> <span class="label patron_first_name">First name: </span> [% patron.firstname | html %]
So I agree with this logic in terms of the status quo pre-25.05, but... that won't work very nicely with bug 39587 which adds "Surname" to the Contact information. I'm going to add bugs for adding "Middle name:" and "Preferred name:" labels to the Contact information as well just to make it really clear which name is which. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |41986 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41986 [Bug 41986] Names in "Contact information" need more clarity -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 --- Comment #146 from David Cook <dcook@prosentient.com.au> --- (In reply to Blou from comment #144)
(In reply to Kalle Karlsson from comment #143)
We've encountered an issue with this in one of our clients Koha instances. They have an automatic import of borrowers set up. For some borrowers, borrowers.preferred_name is not filled in.
We have the same issue. It's very problematic to our users, a lot of institutions use "automated updates". We can't go through all of them to change that.
For reference, here's joubu's diff. We probably will open a new bz
Take a look at the patch I'm about to post on bug 41986. I think it should solve everyone's problems. -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org