CE/ORD - WorkSets that are in subdirectories?

Question

I am still trying to wrap my head around worksets. I can get this far: 
 MY_WORKSET_LOCATION = S:/Project Files/ _USTN_WORKSETSROOT = $(MY_WORKSET_LOCATION) 
 I have a few problems, because this isn't quite right. 
 Our projects (which I envision to be our worksets) are actually stored in 
 S:/Project Files/2019/ S:/Project Files/2020/ S:/Project Files/2021/ and so on. 
 This is regardless of client, department, etc. Everybody's projects go into this structure by project number which is year-project so that each project has its own set of subdirectories. I am not going to be able to convince the entire company to change how we store projects because the transportation department is switching to OpenRoads. 
 In addition to this, I'm probably going to have to back into our worksets because that directory structure is going to exist for a couple months before I get involved into the project. All of the administration, contracts, proposals and other front office work that go into that project get set up before the actual CAD starts up. 
 What's the best way to manage this, from a configuration standpoint?

Tim Hickman · Accepted Answer

relative pathing should solve the reference issue. 
 I am not confident enough to work with the DGNWS yet - still has toooooo many issues.

Rod Wing · Answer

I've been through this situation with several clients. 
 The solution we find to work best is to keep the WorkSet .cfg and .dgnws files under the default WorkSpace folder structure, then store the dgn files, plot files, etc. in your company specific project file structure. 
 I first create a WorkSet Template and reference them using _USTN_WORKSETTEMPLATE _USTN_WORKSETDGNWSTEMPLATE 
 The template .cfg file has custom lines I place at the beginning, something like this.... 
 MY_PROJECT_LOCATION = S:/Project Files/ MY_PROJECT_YEAR = YYYY 
 _USTN_WORKSETDGNS = $(MY_PROJECT_LOCATION )$(MY_PROJECT_YEAR)/$(_USTN_WORKSETNAME)/ 
 When you create a new project using the template you have to edit the MY_PROJECT_YEAR variable to reflect the correct year. 
 If all of your new WorkSets are going to be 2021, then just use that value in the template and you don't have to change it until next year.

David Trejo-Rodriguez · Answer

Are these all going to be under the same WorkSpace or is that level being used to setup other resources such as client resources? 
 a possible solution would be to create a workspace for each year that are configured with the same resources. So on the workpage the user would select the year and then the project within that year.

CE/ORD - WorkSets that are in subdirectories?

Top Replies