Attach user info to content.

[B-Esmaili]

Is there any way to attach user info to content type? something like user field.allowing us to attach multiple user to instance of a content item.

[Piedone]

To my knowledge, you need to implement this yourself, e.g. from a content part where you store the user's ID and then load it when necessary.

[B-Esmaili]

The hard part is implementing a UserPicker . i have no idea how to implement that.

[Piedone]

I suggest you look around in the AdminController class of OrchardCore.Users. You'll see how users are retrieved so you can then do the same in your own content part.

[deanmarcussen]

We discussed this at the meeting last week https://www.youtube.com/watch?v=hexujWzGV14
and seemed to think it was something we should implement.

The code to look at for similarities on picker design would be the ContentPickerField

Probably the thing blocking implementing this in Orchard Core at the moment (for me) is the use of a int DocumentId property on the User object, as this will not carry over between different systems.

Can anyone in the team comment as to why we use the document id for the User rather than a Guid ?

(semi related #5409)

@kevinchalet I wonder if you had any involvement with the original choice there, or opinions on it?

[B-Esmaili]

Glad to hear that. frankly i was disappointed about lack of this feature and i think it is something to be implement as builtin feature. actually the need for this feature originated from assigning user info to content items in workflow tasks and i think user specific tasks are lacking in workflow for that matter.

[jtkech]

Can anyone in the team comment as to why we use the document id for the User rather than a Guid ?

@deanmarcussen sorry i don't know why the user id is the doc id so tied the the store. Looks good to have an uid added to the UserIndex table and then update the UserStore FindByIdAsync()

[Skrypt]

This issue is getting old. I should probably work on it since I'm concerned by this issue. This should be a requirement before shipping RC2 because afterward migrating all the user data and people module extensions might become more complex.

[B-Esmaili]

RC2 is released but still no milestone specified.Have you done something regarding this?