Document storage structure
Hi guys
We have various applications which produce client documentation on the fly and I need to start storing them on our server (Windows Server 2003).
Is there a standard folder structure that should be followed for this sort of thing or has anyone got any suggestions of the best way to do this?
Thanks
Peter
Re: Document storage structure
It would depend more on your particular business model than anything else.
Do you need it broken down by location, client, date, etc., first? Then by what?
Re: Document storage structure
The company I'm currently at is starting to use SharePoint for this very thing.
You might want to look into that.
Re: Document storage structure
It really depends on what makes the most sense for your situation.
For example, here I use a GUID as the folder name for report documents being generated for clients while the raw data files sent into us from clients are stored in a clientname/yyyy/mm/dd folder structure. The first is almost always viewed only by background processes while the second is viewed about 2/3 of the time by a human.
Re: Document storage structure
Thanks guys
I probably just need product, provider and date. I just wasn't sure if there was a recognised standard way to do this sort of thing.
I have dabbled with SharePoint in the dark and distant past. I'd rather not go there again.
I guess the clientname/yyyy/mm/dd kind of approach will do just fine.
Thanks
Re: Document storage structure
I think SharePoint is very cool. What about it makes you not want to "go there again"?