Ah, are you referring to in the gray headers in the directory? Something like "Bill 'Bubba' & Karen Smith" or something like that? They're there in the normal listings within the directory, but not the headers, but I can get them in there pretty easily.

I am not sure how other churches would feel about it, but yeah, in the gray headers. It could be "Bill 'Bubbba' & Karen Smith" or simply "Bubba & Karen Smith". Since most people will know the nickname that might help them be found easier, and the whole name with nickname in the listings gives the rest. I am not sure which is best, legal names in gray ann nicknames below, or nicknames in gray and legal and nicknames below. Not a major thing, just looking for feedback - what other churches would find most helpful.

Yeah, I'll try to get a feel for what some other people would prefer as well and see what the consensus is.

We'd love for the nicknames to simply replace first names in the list view when they are present (with the full name and "nickname" in the detail view), as well for middle names/initials to only show in the detail view. It would clean our records up a lot, and I'd even import more data that way (I've been omitting this data because I didn't love the output, and I wasn't looking forward to the manual editing entailed in changing first names to preferred nicknames).

Lee, that would be really easy to implement. If you guys think that the main listing should only show first and last name, and replace the first name if a nickname is present, I can do that...that sounds logical... I just wasn't certain if nicknames were usually added as a replacement for first names that should have priority...sounds like that's usually the case though. And the detailed info card would have everything, like you said. I can make this change pretty soon and see what you guys think.

I would be in favor of the nickname in the directory and listings. I would assume that if a nickname is entered it is because it is the commonly used name - otherwise what would be the point of having it in the database. However, if enough other people disagree then perhaps a checkbox next to nickname for "use a preferred name" or a setting in the church tab that says, "Use nicknames as primary names" or something like that.

Yup, that's exactly what I was thinking...assume it's in there for a reason and if there's significant push-back, add the option like you said.

Hey guys. So I just pushed out a new version of the app that puts these suggestions into practice. Now, if a person has a nickname, that nickname will be used on the directory listing. Also, middle names are now left off of the listing as well. The complete name is still there on the details card though. The same nickname formatting is now used on the iPhone's listing as well.

I just realized, though, that the household directory is not changed, and it uses the person's first name with no nickname. I'll have to get the nickname on those as well in a future release.

Let me know what you think.

It looks good on the MacBook/safari and the iPhone. The details card on the laptop "has it all", the iPhone details screen only shows first and last name. I am assuming the middle and nick names are not there to save screen space. Question... if the iPhone interface is just for reference, should the details show the nickname or first name? I am not sure it makes a big difference since you had to click the nickname to get the details.

Events uses only the first and last name. Not sure if anyone thought about that. Since I have the calendar updating on our church website I am wondering if that should be a nickname or not. It is not a major issue just a question to ponder.

Something people should also keep in mind... none of these changes affects the vCard import. If you bring contacts into your address book by vCard (for Outlook or Apple Address Book) it is going to be a first name, last name format. The nickname comes through with the vCard but neither of the desktop apps use it in the name field, giving stafftool something other programs do not offer.