Bug 6879 – Reconsider Author/User name fields (combine to one field or at least into two)

Bug 6879 - Reconsider Author/User name fields (combine to one field or at least into two)

Summary:

Reconsider Author/User name fields (combine to one field or at least into two)

Status:	NEW

Product:	OJS
Classification:	Unclassified
Component:	General
Version:	3.x
Platform:	All All

Importance:	P3 normal
Assigned To:	PKP Support

URL:	http://www.w3.org/International/quest...

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-09-08 20:56 PDT by Juan Pablo Alperin
Modified:	2012-09-21 14:58 PDT (History)
CC List:	3 users (show)

See Also:
Version Reported In:
Also Affects:	OCS 2.3.x, OMP 1.0

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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.