@Date & location display

@date & location display
Info for 'birth' shown as
"St John The Evangelist RC Church, Hillsdale, Bergen County, New Jersey, USA"
Is better presented as:
"NJ,Bergen,Hillsdale,St.John,RC Ch." (less than half as long, no detail lost).
Note: for the USA, the 2 character state abbreviation is probably ok and understood worldwide (same for Canada).

While entry is dynamic when creating a profile (and editing the location), these do apply to fields (pull down for date, ie Jan, Fed, etc and specifics for location). The dynamic aspect of location I think pulls from Google and will auto-fill the fields.

SO .... Your 'justification' is to base it on an ongoing defective precedent?

I'm not sure what defects your talking about, perhaps you could be clearer about the problem. What is wrong and how would you fix it or are you just talking about manual entry standardization by using abbreviation. I don't understand the date concern as Geni uses a pull down for the month in a non-numeric format (so as not to confuse the month/day).

It is easier to do or complete a merge when more detail is provided than not. So I would prefer to be presented with "St John The Evangelist RC Church, Hillsdale, Bergen County, New Jersey, USA" rather than your shortened version "NJ,Bergen,Hillsdale,St.John,RC Ch." And at the moment I am sitting with more than 23000 merge issues.

I reversed the order of data as well as shortened it, you can just reverse the order:
USA,NJ,Bergen County,Hillsdale,St.John The Evangelist RC Church

I consider using only numbers for 'date' to be a defect as it is subject to misinterpretation.
Also the sequence of location info (smallest locale first) can lead to loss of largest locale data being lost when data is truncated by some reports.

The version with alphabetic month names is only ambiguous if you start trying to accomodate multiple languages.

That said, the biggest source of confusion is DD/MM/YY vs MM/DD/YY.
So far, I haven't seen any variants that can easily be mistaken for the ISO 8601 format: YYYY-MM-DD (note 4 digit year and use of dash as separator).

That's what I hope Geni will support in the future.

Good point on multiple languages. I agree on use of diminishing time elements, it can keep going: year-month-day-hour-minute-second-etc.
Hopefully they will adopt that, got my vote.