AppsPeopleOzExternalMergedpeopleapiName

People APIInfrastructure

GoogleApi.ContentWarehouse.V1.Model.AppsPeopleOzExternalMergedpeopleapiName

1
out of 10
Minimal
SEO Impact
See go/people-api-howto:names for an overview of name usage in PeopleAPI. The unstructured_name field contains a free form name value. The given_name, middle_name, family_name, etc, fields contain the structured name. For CONTACT mutates, (i.e. when Name.metadata.container is CONTACT), it is recommended for clients to set either the unstructured_name or the set of structured name fields, not both. When only the unstructured_name is set, it is parsed to produce a best-guess set of structured name values for the given_name, family_name, etc. When only the structured name fields are set, the various values are combined to produce an unstructured_name. * When both are set, the unstructured_name is saved as-is and the structured name fields are saved as-is. This may be confusing as they might not "match". For PROFILE mutates, (i.e. when Name.metadata.container is PROFILE), it is required for clients to use the structured name fields as the unstructured field value is ignored on write. The unstructured name fields are generated for convenience on read. For DEVICE_CONTACTS, see b/156020778.

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Apps People Oz External Mergedpeopleapi Name) contains 19 attributes that define its data structure. Key functionality includes: Read-only. A name synthesized based on unstructured_name and the structured name fields. Example: "John Smith" If a language code is passed in the sid...

Actionable Insights for SEOs

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

Attributes

19
Sort:|Filter:
displayNamestring
Default: nilFull type: String.t

Read-only. A name synthesized based on unstructured_name and the structured name fields. Example: "John Smith" If a language code is passed in the side channel using http://cs/symbol:framework.rpc.DeprecatedPropagatedLanguageCode.value or http://cs/symbol:google.rpc.context.OriginContext.accept_language and the name does not have honorific_prefix, middle_name, or honorific_suffix set, the language code will be used to format display_name. If include_account_locale is set on the MergePersonSourceOptions and a language code is not passed in the side channel. The language code from go/uls will be used as the language code for formatting display_name.

displayNameLastFirststring
Default: nilFull type: String.t

Read-only. A name synthesized based on unstructured_name and the structured name fields with the last name first. Example: "Smith, John"

displayNameSourceSocialGraphApiProtoDisplayNameSource →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialGraphApiProtoDisplayNameSource.t

Read-only. The source of the display name.

familyNamestring
Default: nilFull type: String.t
formattedNamestring
Default: nilFull type: String.t

DEPRECATED(b/70571931). Use unstructured_name instead.

givenNamestring
Default: nilFull type: String.t
honorificPrefixstring
Default: nilFull type: String.t
honorificSuffixstring
Default: nilFull type: String.t
metadataAppsPeopleOzExternalMergedpeopleapiPersonFieldMetadata →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.AppsPeopleOzExternalMergedpeopleapiPersonFieldMetadata.t
middleNamestring
Default: nilFull type: String.t
pronunciationsSocialGraphApiProtoPronunciations →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialGraphApiProtoPronunciations.t

This field is stored in contact annotations and merged at read-time. It is available with CONTACT_ANNOTATION container type at read time.

shortDisplayNamestring
Default: nilFull type: String.t

NOTE: this is currently NOT IMPLEMENTED due to changed priorities. Clients usually rely on "first name" instead, when a short name is needed. Read-only. A possibly shorter version of the user's name. - The purpose of this field is to address the needs of UIs where a full display name might be too large to fit. Instead of relying on first_name, which might not be present, short_display_name is preferred. - This is only available for PROFILE and DOMAIN_PROFILE container types. - About the actual content in this field: will be the first name when it's visible to the requester, or the same as display_name, otherwise. A sample scenario where the first name may not be visible is when the limited profile is returned. For more info, see: http://shortn/_9iV7TJ33la

unstructuredNamestring
Default: nilFull type: String.t

The free form name value. For contact mutates it is recommended for clients to set either the unstructured_name or the set of structured name fields, not both.

yomiFamilyNamestring
Default: nilFull type: String.t
yomiFullNamestring
Default: nilFull type: String.t
yomiGivenNamestring
Default: nilFull type: String.t
yomiHonorificPrefixstring
Default: nilFull type: String.t
yomiHonorificSuffixstring
Default: nilFull type: String.t
yomiMiddleNamestring
Default: nilFull type: String.t