[Koha-bugs] [Bug 21978] Add middle name field

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21978

Mark Rogers <marcos.rogers at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marcos.rogers at gmail.com

--- Comment #13 from Mark Rogers <marcos.rogers at gmail.com> ---
+1 Having a middle name field would be very useful.

I work with a school in Bogotá, Colombia, where most Colombian students and
staff also have a second surname (family name), which is treated much like
middle (given) names are treated in the US and UK, namely, that they aren't
usually used except for legal and disambiguation purposes. Having both "middle
name" and "subsequent surnames" fields would be helpful.

So in the case of someone named José Manuel Pérez Rodríguez, that would be

First name: José
Middle name: Manuel
Surname ("last name"): Pérez
Subsequent surnames: Rodríguez

In general usage, the above person would just be called "José Pérez" while
official documentation would have his name as "José Manuel Pérez Rodríguez" or
"Pérez Rodríguez, José Manuel".

Portuguese names also tend to have multiple surnames, but work opposite Spanish
surnames, from what I understand, i.e. that the last surname is typically used
in the shortened version of their name. Perhaps a solution like Christopher
Brannon's for generic name fields would be best. In order to accommodate
different naming conventions, perhaps a configuration field or two could also
be added to allow for defining:

 - A "display name" (patron account), e.g.
   "name1 name3" (English-speaking and Spanish-speaking)
   "name1 name4" (Portuguese-speaking)
   "name3 name1" (Korea/China/Japan)

 - A "sort name" (in results), e.g.
   "name 3 [name4], name1 [name2]" (Spanish-speaking countries)
   "name3, name 1 [name2]" (English-speaking)
   "name 3 name1" (Korea/China/Japan)

If we wanted even further configuration, we could even allow for multiple
formats to be added as authorized values, with the possibility of setting a
default value for the database, with the option to choose a different "display
name" or "full name" for individual patrons. But perhaps this is too much
customization.

At the very least, having a middle name field and a subsequent surnames field
would be very helpful.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.