About “Owner” and "Author" property

[hyzx86]

1. Many places have an assignment procedure for this field, can we use a location unified processing?
   

2. Looking at the Author's assignment process, it seems that it is allowed to be empty, But this field is not set to allow null in the ContentItemInterface , (PR :Author field perhaps is null #15457)

3. The Author and Owner store different values, one is the userName and the other is the User ID, which seems to have no special significance, do we need to refactor? Make it unified?

4. We already have support for me field in the Graphql api, and I've also submitted functionality for UserPickerField (PR: Add GraphQL support to UserPickerField #15389) It is better to be able to provide direct support directly on the Owner and Author fields, as UserPickerField does

5. So, for now it seems necessary to create a UserInterface for the user type just like the ContentItemInterface

[hyzx86]

Hi @gvkries , Perhaps you have some thoughts on these suggestions?

[MikeAlhayek]

The Author and Owner store different values, one is the userName and the other is the User ID, which seems to have no special significance, do we need to refactor? Make it unified?

The idea behind the Author is so you can render it without having to fetch user info every time on the content item listing.

[sebastienros]

Owner needs the id since it's used for technical reasons (permissions mostly).

[hyzx86]

Owner needs the id since it's used for technical reasons (permissions mostly).

My idea was to extend ContentItemInterface to allow to query the item's Autor and Owner directly in Graphql for CustomUserSettings like displayName
Should we add a field like AuditInfo ?