What should you do, instead? Eliminate folders altogether. This doesn't simply transplant the data - it also transplants the problem. What tends to happen is this: the file shares get chopped up at the subdirectory level (depending on who owns what, content-wise) and shoved into SharePoint by means of the Windows Explorer View interface (which is fake, but convincing), preserving the trickle-down hierarchical file structure of whatever chunk of the tree the content owner is moving. Any organization that doesn't have at least one such file share lurking about ought to be immortalized on The History Channel. Share and share alikeĪfter years of consulting on content management issues, I'm prone to stating that most organizations birth file shares in places where John Conner would feel right at home - dystopian wastelands fraught with unforeseen peril and sudden eradication. which are also the two that are easiest (and cheapest!) to fix. Let's start with the two biggest problems. SharePoint persists - no one in their right mind would actually roll back those awful file shares - but nothing new gets done. The typical pattern is something like this: 1) the organization has the epiphany that file shares are out of control, and content management is sorely needed 2) SharePoint is deployed throughout the organization 3) files are moved out of file shares and into SharePoint 4) they rapidly spiral out of control.Īdding insult to injury, the failure of SharePoint to solve the content management issue diverts the organization from exploiting SharePoint's other game-changing features. But the implementation that really sucks is the one that actually takes the big messes that existed in the legacy environment and simply recreates them in SharePoint. Since "sucks" is a less-than-technical term, let's give it a focused definition: there are many organizations out there that have implemented SharePoint - with good intentions, surely - but have improved neither their processes nor their culture thereby. The irony is, they could aim much higher, and get a lot more out of their deployment without upgrading to the more expensive version. That's a subjective observation, of course many who deploy SharePoint (especially the license-free version) don't have very high ambitions. The number of SharePoint deployments in the world today has six digits in it, and four-fifths of them suck. You see it all around you, good SharePoint gone bad.
0 kommentar(er)
