Administrator Tips

Here are a few tips for new ShotRunner administrators:

• Since Sequences can have their own Tasks, Notes, etc. consider grouping shots that share similar characteristics together.

• ShotRunner is very flexible. Maybe too flexible. You might want to decide how you want to use it, and create a standards document for your team. For example, you might want to follow a certain naming convention for Elements, or you might want to have artists hold conversations and submit work inside of Elements and Tasks, and reserve the discussions at the Shot and Sequence level for the supervisors, producer, director, etc.

• Think about the shot and task status codes that you would find most useful. For a shot, you are probably going to want to know where it is in the pipeline, for a task, you probably want to know whether it has started, is in progress, is stuck, is in review, etc.

• Think about the difference between an Asset and an Element: An asset is something that is created in pre-production, or is otherwise shared among shots. Like a 3D model. An Element is something that is composited, like a render of that 3D model for a particular shot.

• You can have your artists upload their WIP right into ShotRunner. I think the practical maximum filesize (due to browser limitations) is probably around 50Mb. We are working on a better system that will handle gigabytes.

• Try to log all conversations about the project through ShotRunner. Try to avoid side conversations in email, chat, etc. This will give you better project history, and encourage more current data.