We keep projects on a "projects" ISIS workspace and media on various
shared workspaces. I set it up that way for a couple of reasons. One
is that not all of our projects have their own dedicated media
workspaces and some projects have their media spread across several
workspaces. A few of our editors seem to spray their media everywhere.
This way, at least the projects are all herded into one place. The
other reason is that people sometimes fill their media workspaces to the
brim before I notice or before they manage their media or ask for more
space. BTW, if you do use a small separate workspace for projects, I
strongly recommend blocking it off so that no one can put media there.
If people inadvertently put media there, it's possible to get it so full
that no one will be able to save their projects.
In a perfect world where everyone always puts stuff where it belongs,
either approach is fine. --J.B.
'Dom Q. Silverio' domqsilverio@gmail.com [Avid-L2] wrote:
>
>
> With Unity, it made economic sense to separate the projects and media
> drive. Often you would mirror the projects workspace but not the media
> workspace.
>
> With ISIS, all workspace are RAID 5 protected. There is still a reason
> to separate them, such as is if you need to vary user permissions.
>
> HTH
>
>
>
>
> On 9/24/2014 6:27 PM, tcurren@aol.com [Avid-L2] wrote:
>> We also create a separate partition for every job with all assets and
>> project on the same partition. This has worked for us for a very long
>> time. (Terrablock)
>
>
>
>
Posted by: John Beck <jb30343@windstream.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (6) |
No comments:
Post a Comment