https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39009 --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Julie, can you explain that a bit more? Do you mean the display of the name after saving? And when: where? -- 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=39009 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@bywatersolutions.com Summary|Creating new patron |When creating a new patron, |"Preferred Name" is not |preferred_name is not used |working |in construction of username --- Comment #2 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Libraries have reported concern that the username automatically generated when creating a patron is still generated as [firstname].[surname], rather than [preferred_name].[surname]. -- 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=39009 --- Comment #4 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- (In reply to Steve, OSLRI, USA from comment #3)

In addition to the automatic generation of the username by Koha, I'm also curious about the Aspen integration. I'd want to be sure that Aspen sends preferred_name in lieu of first_name if it exists.

(I'm not super enamoured by "preferred" as I feel that could be insulting in some circumstances, but we can easily use a little JS to rewrite the display of the field name to suit our local climate. So, I won't push that issue.)

Aspen behavior is outside our scope here, though it is important. There's an argument to be made that it will never get easier than it is now to rename those fields so firstname is legal_name and preferred_name is ... something else? legal_name and first_name (where first_name is what's currently named preferred_name) makes a lot of sense to me right up until I try to imagine explaining the change to someone. But, again, maybe it's best to tear the bandaid now? Come to a Koha community dev meeting and see what people say to the idea! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.