Need fullyQualifiedName field for data assets and profile field for users of team.

[Sachin-chaurasiya]

Currently, we are getting only these 4 fields for owns and 5 fields for users

owns:[
   {
      "id": "155ce023-843e-4b4b-a6bc-10d989d4182f",
      "type": "table",
      "name": "users",
      "href": "http://localhost:8585/api/v1/tables/155ce023-843e-4b4b-a6bc-10d989d4182f"
    },
],
users:[
{ 
     "description": "Robert Cole"
    "href": "http://localhost:8585/api/v1/users/03a8a9ac-e29b-4a9a-8ad1-00339b849310"
    "id": "03a8a9ac-e29b-4a9a-8ad1-00339b849310"
    "name": "robert_cole6"
    "type": "user"
}
]

 1. use case: FQN to redirect users from team page to dataset details page 
 2. use case: Profile to show user profile pic beside the username

[sureshms]

Is the description set for the table?

[sureshms]

Adding profiles to EntityRelationship type is a much bigger change. For now, let's not show profile pictures. We need to revisit if we want to use EntityRelationship to return the users of a team or use User type. I will change the name field for all data assets to FQN.