Mapping "user" to "author" directly

[BigRoy]

Problem

In the current code during integration the user is mapped as author in the resulting data, this might introduce a slight confusion. As during publishing we're relying on user being present as data whereas after it is author.

See:

config/polly/plugins/publish/integrate_asset.py

Line 240 in e233487

"author": context.data["user"],

Discussion

Should we maybe already collect this information as author from the beginning? Why, or why not?

[mottosso]

Makes sense.

The idea was for a single user to be able to "login" as someone else and publish from there, along with getting that user's working environment including tools and things. It's something I had at Framestore, though I didn't use it very much.

In that case, user to me is whomever is physically logged in to the OS, whereas author is the "virtually" logged in user.

[BigRoy]

In that case, user to me is whomever is physically logged in to the OS, whereas author is the "virtually" logged in user.

Sure, to me the only odd thing is for now that the naming of it changes in the integrator. If we don't do that we have less terminology at the moment to think about.

[mottosso]

Sure, let's patch that up. Let's go with "author"?

[BigRoy]

Yup, that should also make it easier to stay backwards compatible at this point as that was how it currently exists and persists in the database/storage.