Best Practices for Site Hierarchy ?
Hi All;I`m working on Sharepoint 2007 for 6 months and in my company I did a 2003 to 2007 migration and still working on administering 2007. A month ago we got our Sharepoint 2010 Beta and we start to playing with it. With SP 2007 we didn`t change our site hierarchy but with 2010 we want to set things right.With Sharepoint 2007, first we created a site collection from Central Administration and created Sites under it by going to Site Actions > Create > Sites and Workspaces and create the site.> Right now we have 5 main sites under site collection, and under these 5 sites there are lots of subsites and document libraries.But with this organization we are encountering with an issue:> Long file names: In some document libraries we can`t upload or download files because the file path gets too long. I think the main reason for this is, in some document libraries there are lots of Folders inside folders so when server tries to get the file, file path gets too long. Also in front of that it adds sites that document library is in.So I thought that Sharepoint is very capable software that can hold bigger organizations which can have more subsites and departments than us. So there should be a better way of organizing sites.What is your opinion about this ?Are there any resources that you know that briefly explains creating Sharepoint site hierarchy ?
Can Atuf Kansu
February 3rd, 2010 11:37pm
Consider not using folders! Use metadata (columns) to categorize the content. Create views to filter or group the content. Grouping provides many of the benefits of folders without the overhead of folder names in the path, and you can offer the same content grouped in many different ways.And a few tricks...Use short names for libraries and sites:When you create a library give it a very short name ("HRdocs" instead of "Human Resources Documents and Other Resources"), then go the the library's settings page and change the title of the library to "Human Resources Documents and Other Resources". Now the URL is short, but the library name is fully descriptive.This also can be done for sites and subsites, but not for folders.Use short names for documents:Users have be trained to add metadata to the name of a document (HR Employe Manual - June 2009 - Reviewed - Approved - Final) instead of using metadata in the library.Mike Smith
TechTrainingNotes.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2010 12:58am
Hi Mike,Thanks for usefull information, I haven`t thought this before. Using metadata as categorizing files is a good way also it will definitely eliminate long URLs. But the problem we have is, our users usually upload their files in batches with using Explorer View. The reason is their clients gives them CD or DVDs that has documents in folders and they just copy and paste into explorer view in sharepoint. Event I close the explorer view to users and force them to use default multiple file upload control; in that CDs and DVDs there are lots of folders and subfolders which they will have to manually organize them and create meta data, that we can`t ask such a burden from our users.So I need to find a solution for this case, I thinking that maybe I can write a event handler that will control the file upload and when ever there are folders and subfolders it will reorganize the document library by creating coloumns and metadata and delete that folder structure.Can Atuf Kansu
February 6th, 2010 9:10pm


