We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 6879

Summary: Reconsider Author/User name fields (combine to one field or at least into two)
Product: OJS Reporter: Juan Pablo Alperin <juan>
Component: GeneralAssignee: PKP Support <pkp-support>
Status: NEW ---    
Severity: normal CC: alec, jean-andre.santoni, jmacgreg
Priority: P3    
Version: 3.1   
Hardware: All   
OS: All   
URL: http://www.w3.org/International/questions/qa-personal-names
Version Reported In: Also Affects: OCS 2.3.x, OMP 1.0

Description Juan Pablo Alperin 2011-09-08 20:56:57 PDT
The First/Middle/Last name fields do not apply across cultures. There is a good summary of different names formats and some suggestions on how to implement a more inclusive name form at: 
http://www.w3.org/International/questions/qa-personal-names

Review this list and consider applying some of the suggestions to all our software. The obvious concern is: how does this impact the metadata formats we must export into (i.e. do they require the split fields?)
Comment 1 Jean-André Santoni 2011-11-09 02:46:08 PST
I agree with Juan Pablo Alperin.

Our users reports bugs about the default search field being the firstname. They would prefer it to be the lastname.

Having a global name field would solve this too.
Comment 2 James MacGregor 2012-01-24 22:48:22 PST
See http://pkp.sfu.ca/support/forum/viewtopic.php?f=9&t=8215&start=0 for discussion on Indonesian authors who only have a single name.
Comment 3 James MacGregor 2013-05-29 15:30:44 PDT
Reassigning to 3.1. Juan, if this should be addressed earlier, please move appropriately.