Different attributes for "user" and "contact" ressource are not properly supported

A user resource has different attributes that a contact resource. When using the Users API (Global Address List), the Object Model should support slightly different attributes, e.g. a Contact has a businessAddress property, whereas a User object does not have a businessAddress property, but a streetAddress,postalCode,state, etc.

I would consider this a feature request.

[teamoo]

I created a comparison of the attributes, maybe this helps when looking at this feature request.

User Resource Attributes	Contact Resource Attributes	attribute selected by default (user resource)	implemented as of 2.0.2
assistantName
aboutMe
accountEnabled
ageGroup
assignedLicenses
assignedPlans
birthday	birthday
businessAddress		x
businessHomePage
businessPhones	businessPhones	x	x
city
categories		x
changeKey
children
companyName	companyName		x
consentProvidedForMinor
country
createdDateTime	createdDateTime		x
department	department		x
displayName	displayName	x	x
employeeId
faxNumber
givenName	givenName	x	x
hireDate
mail	emailAddresses	x	x
fileAs
generation
homeAddress
homePhones		x
id	id	x	x
imAddresses	imAddresses
interests
initials
isResourceAccount
jobTitle	jobTitle	x	x
legalAgeGroupClassification
lastModifiedDateTime		x
licenseAssignmentStates
manager
middleName
mailboxSettings
mailNickname
mobilePhone	mobilePhone	x	x
mySite
nickName
officeLocation	officeLocation	x	x
onPremisesDistinguishedName
onPremisesDomainName
onPremisesExtensionAttributes
onPremisesImmutableId
onPremisesLastSyncDateTime
onPremisesProvisioningErrors
onPremisesSamAccountName
onPremisesSecurityIdentifier
onPremisesSyncEnabled
onPremisesUserPrincipalName
otherAddress		x
parentFolderId		x
personalNotes
profession
spouseName
otherMails
passwordPolicies
passwordProfile
pastProjects
postalCode
preferredDataLocation
preferredLanguage		x
preferredName
provisionedPlans
proxyAddresses
responsibilities
schools
showInAddressList
skills
signInSessionsValidFromDateTime
state
streetAddress
surname	surname	x	x
usageLocation
userPrincipalName		x	x
userType
title		x
yomiCompanyName
yomiGivenName
yomiSurname

All attributes of the contact resource are returned by default, whereas for the user resource, only those attributes marked are returned by default.

*mail attribute is of type String, whereas emailAddresses is of type EmailAddress collection

[janscas]

This basically means that a User object must be created in address_book.py. The GlobalAddressList should then return Users instead of Contacts. This requires a lot of effort at the moment: creating the User, implementing the different methods (save method that knows what to update). Etc.

Basically we must replicate the Contact object with the properties, endpoints, etc from Users.