Suggestions for Assets

Hi Michael, Florian,

These are all great suggestions. I will see if I can implement at least some of them for you quickly.

But first, as is always the case, I need to ask you some questions to be sure I understand what you want.

1. Asset Groups.

This could also be thought of as hierarchical assets. It have so far avoided implementing deep hierarchies because they get very, very complicated, so let me ask some questions:

1a) Will the buildings ever be used on a shot in isolation? That is, when considering how the buildings will be used, is it important to be able to link individual buildings to shots?

1b) Is it important to track the production progress of each building? Is it important to be able to discuss the production of each building separately?

1c) Would adding a task for each building to a "city" asset be sufficient?

1d) Another thing I've wanted to implement is "asset categories" -- so that the asset listing would be broken down into the various types of assets (i.e. a section or tab for '3D models', 'matte paintings', 'scripts', 'HDRIs', etc. Would this be useful?

2. Assign one asset to many shots

This one we can already do. You do this via Elements. Essentially, create an element on a shot, and then set the asset for that element. The element represents the work that needs to go into adapting an asset for a particular shot (animation, lighting, 3d tracking, rendering, etc.) You will be able to see which shots use the asset on the asset page.

I probably need to make this easier to use. Any suggestions?

3. Filter assets on a shot basis

Help me understand what you would like to be able to do here.

4. Filter tasks on a shot or asset basis

You can already go into a shot or asset and see all the tasks for that shot/asset. I am probably not understanding what you want to do here.

5. Filter tasks on object (sub-object)

Can you provide me an example of what you would like to do? I'm not clear on how this would work.

6. Filter tasks on teams/User to get an administrative overview if you are not in the team or that user about a team or user

Would it work if we put a task list on the team page -- it would show tasks for anyone on that team? And a task list on the user page?

7. Table and Thumbnail views for assets

Yes, alternate index views are totally possible.

Thanks,
Cameron

On Mar 1, 2010, at 5:06 AM, Rottke, Michael wrote:

> Hi Cameron,
> to expand Florians suggestions I'd like to add some more asset management ideas that could be useful in the future.
>
> - assign one assets to many shots (that's my favorite, top most on the wishlist)
> - filter assets on a shot basis
> - filter tasks on a shot or asset basis
> - filter tasks on object (sub-object)
> - filter tasks on teams/User to get an administrative overview if you are not in the team or that user about a team or user
> - table and Thumpnails view for assets
> Basically it is making the asset and task management as strong as the sequence and shot management.
>
> Please let me know if you need more information.
> Many thanks,
> -Michael
>
> ________________________________
> Von: Florian@SANOR [***@sanor-film.de]
> Gesendet: Montag, 1. März 2010 12:09
> An: ***@shotrunner.com
> Cc: Rottke, Michael
> Betreff: Suggestion for Assets
>
> Hi Cameron,
>
> i talked to Michael Rottke yesterday and told him about some ideas i have for the assets page on shotrunner. He suggested to give it right to you. Maybe you could establish my ideas?
>
> It wold be very usefull, if one could group assets together to an asset-group. The reason for this suggestion: in our project we have to build a whole city with many differente houses. Every single one of that houses has to be an asset. So now we have to have about 20 or 30 assets just for one thing in production: the houses of the city. This causes the assets list to be very uncomfortable to use, because it will be very long. And perhaps one can set a task to the assets group as well? That would be very nice.
>
> I think, perhaps the solution for that is to subordinate assets to other assets.
>
> Maybe you can think about that suggestion. It would turn our work with assets into a more simpler way.
>
> Thank you for your attention.
>
> Best regards
> Florian
> SANOR Filmproject