Projectexplorer ?

Andreas,
I have setup an office standard PE tree that sorts
files first by type. i.e. Sheet files, Design Files, Drawing Files, and Extractions.
Then at second level sorts by file content. i.e. Floor Plans, Rcp's, etc.
Then at third level by floor level. i.e. 1st, 2nd, 3rd etc.
Or in the case of elevations i.e. North, South, etc.
Conceptually it works great.
But harvesting on large projects doesn't allow its use. Harvesting to slow
and requires a reharvest for each new session.
I have attached our PE tree for reference.
Tom

Tom/Andreas:

As you mentioned, harvesting of resources on large projects can be cumbersome at times, especially if you are using ProjectWise.  My recommendation would be to use a configuration variable link that points to the project directory.  _USTN_PROJECTDATA is the default configuration variable for this.  That way your users will have direct access to the entire project directory to attach references, open other files (DGNs, DWGs, XLS, DOC, JPG, etc.), place cells, or attach links to other files/models without the overhead time of the harvesting process.  This configuration variable link is reusable since it is keying off of the project selected.  You can also create more granular folder links with the configuration variable folder links to items like cells, specifications, product cut sheets, etc. as you feel necessary.  It is a powerful tool to make the project information available at the users fingertips and not require them to keep a bunch of Windows Explorer windows opened behind the MicroStation window.  I highly recommend incorporating into your team's workflows.  

Regarding

Danny:  Using the configuration variable links rather than harvesting you get the name of the DGN (rather than the model) and you can drill down into the dgn and pick a specific model, saved view, etc.  This might relieve some of your gripe.  I have included a screen capture below that shows how I have configured Project Explorer for the US Army Corps of Engineers workspace.  You can see it provides access to a lot of different types of project content and for the most part avoids harvesting because of the time to harvest on large projects or when using ProjectWise.  Building Models, Drawings, Sheets, and Building Views are the only folders set to harvest and those were left in from the delivered.  The rest is done through configuration variable links and applied filters.  I hope this will give you some ideas that you might find useful and worthwhile.

As a side note to your other post that you linked to:  There is development of (and I have seen images) of thumbnail previews for cells within project explorer that will be coming.  I don't know the time frame, but it's coming.  

Sorry for the huge image, but it's not very useful if its not legible.

-Travis

Travis,

This looks like interesting option if it doesn't require harvesting

and doesn't  use full path for file name. (both a real problem with my setup)

A couple of questions before I dig deeper into this concept.

In your setup are the sub folders automatically indicated

by a top level configuration variable or is a variable set for each sub folder.

A second question. Can the files displaying in the sub floders be filtered

using wild cards. i.e. *.dgn or fp01*.dgn.

TIA

Tom

All the sub-folders automatically populate when using a configuration variable link.  You can not apply filters to the sub-folders that are automatically populated from the top level configuration variable (but you could make the top level configuration variable be $(_USTN_PROJECTDATA)*.dgn to only show DGN's if you wanted).  

That said, if you wanted to be a little more granular with your folder setup you could create an additional structure where you apply filters using wild cards as you asked about.  

My thought on Project Explorer is that it is OK to have the same file be available in more than one PE Folder if it makes it easier for the users to find the information when they are doing specific tasks.  If you take a more granular approach just make sure that you build everything off of a project location variable so you don't have to the do the same thing on each project.  

I hope this helps,

Travis

Travis

Thanks for that

' Using the configuration variable links rather than harvesting you get the name of the DGN'

I was using cfg links but was still getting the model name first (followed by the full file path)

Would seem that this is due to the 'filters' I applied being 'Model:Design' and 'Model:Sheet'.

I've removed these and as you state, you just then get the file name (far more practical). Fortunately this isn't a problem as I use the 1 file = 1 model (for design) and 1 file = 1 Sheet for drawing sheets approach.

I guess in workflows where there are more than 1 model in a file, there might be naming issues. Haven't personally has such problems/issues yet. One to watch out for though I suppose.

Again, as you mention, having a more granular, or extensive folder structure to your project will help with the PE links as you can 'identify' different types of info better or more accurately.

Having multiple models in a single DGN isn't an issue when using a CFG link, because you are able to drill down into the DGN structure to view the models within it.  

-travis

Having multiple models in a single DGN isn't an issue when using a CFG link, because you are able to drill down into the DGN structure to view the models within it.  

-travis

I guess so

But you would have to know which dgn to open/drill down into ...... not always the case if you aren't the one that created those files

If you have a team that's very rigorous about what models are in which files and naming conventions/workflow dos and don'ts then maybe ...... must admit I don't really 'trust' the average user to be that rigorous

You also have to START with good seed files and therefore no references for unused reference files as this will fill your projects explorer

Hello again

Minor little thing I've just come across, ... it would seem you have to add *.dgn (or some other file format extension if that's what you're putting in that folder), to the end of the cfg link, or you get a sub folder in each of the cfg links, so you have to expand that as well as the 'root' link (in PE) ..... Hope you see what I mean (guess it's not a big deal but it gives you one more thing to click on/expand before you see the contained files)

Trying to move a bit forward, but I am stuck here.

Any hints why the OK button is greyed out?  I have defined a dgnlib in my project path, and try to define a configuration variable link.

Hi Andreas,

I think you have to enter the variable in as $(_USTN_PROJECTDATA).

HTH Jan