We are currently using traditional project directory folders for large projects with sometimes tens of thousands of documents.
We are planning on migrating the data to SharePoint and the path forward in unclear.
Initially it was recommended to use a library, not numerous folders, to contain the data so that searching of data in improved.
That sounded great. The 1<sup>st</sup> project used to pilot this for other project is divided into 20 different modification packages.
A library category was created for MODS with selectable options of the 20 mod package names and “No Defined” (default value).
Some data items are shared between more than one MOD so this category can have more than one assignment.
When we looked at the directory structure in place we found no consistency in folder names, no consistency in directory structure.
Many folders have 5 or 6 (or more) levels of subdirectories.
Ideally we want no more than 4 or 5 categories of meta data to define all data.
Mapping from chaos into a comparatively small number of categories is daunting.
When searching this forum I find that libraries should be limited to 2,000 items.
There are tens of thousands of items in our pilot project.
Surely someone somewhere has encountered this organizational problem.
I could use some advice from someone who have been there before.
