Milan Kolar

Yep it is mostly for visual inspection and knowing exactly what the path was originaly when published. We find this kind of data very useful after project is archived for...

You mean stored on the parent asset? Or in a data member asset['data']. the second one makes sense I think. For us its more about having the data, than where...

Right. If you look at the example that's exactly where we store it. In which case the question might be the opposite. Shouldn't `template` be required then and not in...

Truth be told I'd prefer thinking of a different solution, rather than moving the groups under assets. It is not very consistent, especially when you only have some subsets in...

We had a good old school paper brainstorm in the office and thin we have an elegant solution, we'll try to implement. If you have existing groups, we'll treat them...

> Evaluate whether USD is a good candidate for this. Theoretically USD could be by far the best candidate for this purpose. Have you tried it out yet? I've been...

We've taken a stab at this, even though it doesn't exactly cover all the point mentioned in this huge thread 😄 We have a basic framework that let's you specify...

Currenly nothing visually interesting :D . You press a button in avalon menu and voilà... all the required representation get loaded into the scene. No progress bar or ui right...

I would remove the old publisher and keep the new one just called `Publisher` (to keep in liner with the `loader` and `launcher` rather than `load` and `launch`). I agree...

I feel this might be quite a bit of micro managements. Shouldn't it simply process whatever it can, and skip those it can't?