[ORD/CONNECT] Workset template?

OK, so the issue is with one specific client, but I'm still running into other issues.

The rest of the templates that DO appear to give me CFGs from the proper template aren't creating directories. Now, I don't actually need those directories there but...

As much as I don't want to edit the client configs more than necessary, I did have to add a block to account for they way we store our data. That gets edited after workset creation to the proper project directory, and it includes "placeholders" for files that are about to exist.

#============================================================================
# Template for a new WorkSet
#============================================================================

PROJECT_YEAR = 2022
PROJECT_NUMBER = WS_Test
PROJECT_DIRECTORY = $(SHR_PROJECTSDIR)$(PROJECT_YEAR)/$(PROJECT_NUMBER)/
_USTN_WORKSETROOT = $(PROJECT_DIRECTORY)CADD/Design/
PROJECT_CADD = $(_USTN_WORKSETROOT)

MS_DEF = $(PROJECT_CADD)Base/
MS_DEF > $(PROJECT_CADD)Sheet Sets/
MS_RFDIR = $(PROJECT_CADD)Base/
MS_RFDIR > $(PROJECT_CADD)Sheet Sets/

%if defined (CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME) && exists ($(PROJECT_CADD)ORD/$(CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME))
  CIVIL_ROADWAY_TEMPLATE_LIBRARY        = $(PROJECT_CADD)ORD/$(CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME)
%endif
#----------------------------------------------------------------------------

%if defined (CIVIL_WORKSET_DESIGNSEED) && exists ($(PROJECT_CADD)ORD/$(CIVIL_WORKSET_DESIGNSEED))
  MS_DESIGNSEED                         = $(PROJECT_CADD)ORD/$(CIVIL_WORKSET_DESIGNSEED)
%endif

My thought was that, if the workset creation makes a copy of the workset template directory, that copy could be moved into the project to the proper location, renamed "ORD" and be ready for design with the proper files.

I found it.

#====================================================================================
#set up workset variables
_USTN_WORKSETDGNWSTEMPLATE = $(_USTN_WORKSETSROOT)TDOT_RDWY_TEMPLATE.dgnws
_USTN_TEMPLATEWORKSETNAME = TDOT_RDWY_TEMPLATE
_USTN_WORKSETTEMPLATE 		= $(USTN_WORKSETSROOT)$(USTN_TEMPLATEWORKSETNAME)
#====================================================================================

Workset templates were provided, but not defined. Once I found these variables, I was able to get "proper" worksets.

Since your clients will provide WorkSpace, use what they provide. It will make your life a lot easier. 

That leaves you to navigating between years. You can put a year variable in your WorkSet template. I have clients that do that. After creating the WorkSet, the manually edit the WorkSet cfg to set the year and other custom path variables. A custom WorkSet creation tool would solve that problem.

So...keep the client workspaces but abandon their worksets directory in favor of a "S:\Projects\year\Worksets directory (for read/write access)?

Yeah, with that I'd HAVE to have a custom tool. If "Year" is defined in the workset, it can't be accessed by any process that happens before that, including "Create Workset".

I thought I was on the edge of understanding this well enough to put it all together, but I'm getting more confused again.

Workspace: Client
Worksetsroot: Many (by year, in projects directories) or one(in client workspace directory)
Workset Template: One (client)

Workspace: Year
Worksetsroot: One (by year, in projects directory) or many (in client workspace directory)
Workset Template: Many (client)

Do i have the analysis right?

You don't have to separate your WorkSets by year. They can all be in the same folder with custom variables in the workset cfg directing them to the right path. We had proposed to some DOTs setting up the WorkSpaces-WorkSets by year as well. They thought there would be too much confusion as to what year to look in for the project.

We did some test for them and generated over 2000 WorkSets in a single WorkSpace for them. ORD handled it just fine, and there is a search option to search for WorkSet names so they were happy with that.

I was unaware of the search function in Worksets. That makes this much easier - we'd end up with a list of dozens and dozens of project worksets, but a search simplifies finding the right one.

We wouldn't have any issue with year based breakdowns because that's how our project directory is set up - everyone is used to looking at that sort of list. But the search will work fine.

To confirm...I really only need a "workset template" if I am creating worksets through the MicroStation interface, and I use "workset standards". If I have a pre-existing project directory structure, I only need a workset CFG file because the DGNWS will be created from that "seed" when the workset is first opened. Is that right?

That is correct.

That is correct.

Thank you so much!