Shawn Nelson
03-27-2008, 09:24 PM
Standards are good, especially open standards. They make work easy from project to project.
I am wondering we, as a community, could standardize on the naming scheme and folder structure for Red field offloading? This way any projects that conformed would all look the same.
For instance, here is my folder structure
[Project]_RawFootage
|-Day_01_[Month][Day]
|--[Mag]
|--[Mag]...
And so forth, though tonight in talking with another DIT I thought it might be good to introduce different sub-folders for different project settings. Such as,
[Project]_RawFootage
|-4k2-1_23-98_R28
|--Day_01_[Month][Day]
|---[Mag]
|---[Mag]...
And I'd be open to tons of feedback to hammer out the best, most straight-forward folder structure, then we could make a PDF, sticky it here and refer people to it. That way projects make sense, 1st units match 2nd units and so forth.
Thoughts? Let's not all try to reinvent the wheel. Community-driven standards make life better for all! :-)
I am wondering we, as a community, could standardize on the naming scheme and folder structure for Red field offloading? This way any projects that conformed would all look the same.
For instance, here is my folder structure
[Project]_RawFootage
|-Day_01_[Month][Day]
|--[Mag]
|--[Mag]...
And so forth, though tonight in talking with another DIT I thought it might be good to introduce different sub-folders for different project settings. Such as,
[Project]_RawFootage
|-4k2-1_23-98_R28
|--Day_01_[Month][Day]
|---[Mag]
|---[Mag]...
And I'd be open to tons of feedback to hammer out the best, most straight-forward folder structure, then we could make a PDF, sticky it here and refer people to it. That way projects make sense, 1st units match 2nd units and so forth.
Thoughts? Let's not all try to reinvent the wheel. Community-driven standards make life better for all! :-)