@GreyWolf said:We bring the coding team on board. They say "WTF are the documents?" [w=where]. We all stare glumly at each other.
I would want the repository to be a huge bucket with a relational index, so I can say
SELECT * FROM REPOSITORY WHERE PROJECT_ID="GREYWOLF203" AND VERSION>="0.1"
ORDER BY VERSION
and get back a complete list of links.
I believe that for the typical messy reality, a hierarchical info repository is fundamentally unusable.
The WTF here is the way your people are trying to use SharePoint. It appears as though they have transposed what was a rigid folder structure on a file server to a SharePoint Document Library model, and while SP certainly can do that, it doesn't really work too great. It's best when viewed as an amorphous lump that you just stuff data into. Pull the hierarchy back to site level, so that rather than having "PROJECT_ID" as a document attribute you actually have a site (or at worst a separate Document Library) for each project. Make use of the self-service features so that PMs can create their own sites or Doc Libs on the fly. Then sit back and watch the weeping and grinding of teeth when someone asks for an overall report on something.
