Yeah, if we have two alternatives that might be confusing, why not
combine them and create a frankenstein option that will _definitely_
be confusing! ;)
I'm for displayName... when people say "user name" they usually mean
what we call "user login ID", so that would be more confusing.
-David
On Apr 30, 2009, at 2:03 PM, Jacques Le Roux wrote:
displayUserName ?
Jacques
From: "Andrew Zeneski" <andrew.zene...@hotwaxmedia.com>
Our Crowd server uses displayName (as well as sn, givenName and
mail) but that is probably because it is backed by LDAP. Display
name gets auto populated with First/Last name, but is editable.
userName sounds too much like a string to use for login, where
displayName would mean the name to display in the system. If we
add this field, we should edit createPersonAndUserLogin server to
set the value to First/Last if its empty as well. Then use this
field in the header instead of the party fields.
Andrew
On Apr 30, 2009, at 3:20 AM, Jacques Le Roux wrote:
That seems a good reason, what is used in Crowd ? I suggested
userName because it's related to userLogin. What about
displayUserName ?
Jacques
From: "Adrian Crum" <adrian.c...@yahoo.com>
displayName is used in LDAP? Sweet! In that case...
+1 for displayName
-Adrian
--- On Wed, 4/29/09, Andrew Zeneski <andrew.zene...@hotwaxmedia.com
> wrote:
From: Andrew Zeneski <andrew.zene...@hotwaxmedia.com>
Subject: Re: Adding description field(s) to the UserLogin entity
To: dev@ofbiz.apache.org
Date: Wednesday, April 29, 2009, 10:59 PM
displayName is a common field used in LDAP systems. Which is
really the only reason I suggested it. Usually its the
first/last name together but its totally arbitrary.
On Apr 30, 2009, at 1:55 AM, awdesh parihar wrote:
> Hi
> > +1 for name suggested by jacques , we can also go we
displayUserName.
> ----
> Awdesh Parihar