User Manual

Creating Avid Editing Projects in an Interplay Environment
1150
Creating Avid Editing Projects in an Interplay
Environment
One of the biggest decisions you will make regarding your workflow is the location of the
projects and bins created by the editing applications. A predictable folder structure allows for the
following:
• Creates an easily maintained folder structure in the Interplay database
• Makes it easy for editors and other users in the organization to locate assets that are used by
different projects
• Makes it easier for the Administrator to delete older projects on the Avid editing systems
In a large Interplay environment it is important to locate Avid editing projects in areas that are
easily accessible by the Administrator that has to delete the projects. When you start the editing
application, the system displays the project log in window. From this window, you can create a
project that is either Private, Shared, or External.
The best choices for a shared structure are either Shared or External. These types of projects are
created in a common location, making it easier for the Administrator to locate and delete old
projects.
n
Any user can create or delete a project via the editor. Keep your project structure consistent to
make the Interplay database easy to maintain.
If you are working with projects created on local drives, then note the following:
• A local project resides on the C: drive of the Avid editing system.
• If the connection between the Avid editing system and shared storage is lost, the project and
its contents are unlikely to become corrupt as a by-product.
• You cannot login to the project from another workstation. You (or other users) must go to the
Interplay Projects folder to locate the contents created in this project.
• From an administration standpoint, you must clean these projects up or archive them from
each editing system. At a large site this can become time consuming and needs to become
part of the Administrator’s workflow.
Private
A Private Project is stored locally. It can be accessed only by the user currently logged on to the
editing machine. On a Windows system, a Private Project is always stored under the user’s
Documents directory. An administrator may be able to access this project if they have read/write
permission to the user’s directory.