Our Info Exchange is becoming over-populated - from the web view, it’s showing 96 folders.  I don’t want to have our clients or anyone sifting through 96 folders. 

I know I can delete folders.  However, being a data hog, I don’t want to lose the information that has been recorded/associated with that folder, which is what I fear will happen when I delete it from Info Exchange.

Can I organize those folders after the fact? Ie, have an expired folder that holds all of the expired folders, thereby unclogging the main web screen?

TIA

Hello JR.
I’m not able to help but as we’re just now about to implement NIX after using NPCS for a year I’m curious about something you’ve mentioned here…
Your clients are seeing 96 folders?  Are these folders representing projects?  Are you not specifying which clients see which projects?  Or you already-are but yet there’s still a litter of folders?
...just curious of your experience, that’s all.

M@

It is only one project.  It seems my firm’s use of Newforma is really more for it’s ftp/large file transfer capabilities than anything else.  Our info exchange is basically littered with folders with titles “2009xxxx sent to Consultant”, or “Owner”, or “Contractor”; just a lot of miscellaneous one-time, expired file transfers.

Again, I know I can delete, but I don’t necessarily want to lose all of the good tracking information Newforma captures with the downloads (in case of the “I never received that file” scenario).

Thought about another way, you’d think there could/would/should be a NIX “best practice” folder tree structure to better utilize the file transfer feature.  For example, when you look at Info Exchange via the web, you would see only 5 main folders (“drawing sets”, “addendums”, “RFI’s”, “Misc”,etc) and within them would be categorized transfers…

Interesting.  So the post expires, but yet it’s visibly still there?  And if you delete those contents you lose all logging relevant to that content?  I sort of imagined that the expiration of a post wasn’t JUST its accessibility but also its existence.  This concept is pretty important to me because I’m just NOW wondering of the need for a NIX Custodian.?  :-|  And this is your dilemma as well, right?

I see what you mean about directory structure.  I guess on the NPCS side the indexing, in a way, supersedes the need of appropriate directory structure but I can imagine what you mean about the NIX.

Without having yet used the NIX (any day now…literally) I sort of imagined it’d automate directory structure partially-based on the Newforma Activity that the post was related to.  Obviously if you’re within Project Files I can imagine a lot of scenarios where that is effectively an impossibility.