AppsPeopleOzExternalMergedpeopleapiBestDisplayName

People APIInfrastructure

GoogleApi.ContentWarehouse.V1.Model.AppsPeopleOzExternalMergedpeopleapiBestDisplayName

1
out of 10
Minimal
SEO Impact
The best suggested name to use for the Person from the available source fields, which may include FileAs, Name, Org, Email, IM, Phone, ... Rough source container priority order is Contact, then Profile, then Place.

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Apps People Oz External Mergedpeopleapi Best Display Name) contains 3 attributes that define its data structure. Key functionality includes: The container the suggested name was sourced from

Actionable Insights for SEOs

  • Understanding this model helps SEOs grasp Google's internal data architecture

Attributes

3
Sort:|Filter:
containerTypestring
Default: nilFull type: String.t

The container the suggested name was sourced from

displayNamestring
Default: nilFull type: String.t

The display name. This name is intended to be the best name to display for this Person. It may be built from a variety of fields, even if those fields are not explicitly requested in the request mask. Generally, the display name is formatted in 'first last' format. If the name appears to be a CJK name (as determined by a heuristic), the 'last first' format will be used. There may be other cases that the 'last first' format is used which are not documented here. See the code at: http://google3/java/com/google/focus/backend/client/DisplayNameFormatter.java?l=659&rcl=351360938

displayNameLastFirststring
Default: nilFull type: String.t

The display name, always in 'last first' format. This field does not depend on the format of display_name and will always be in 'last first' format.