Perhaps the most for SharePoint is used as a platform for sharing/collaboration file. Traditional Windows file sharing is a technology of ageing and lacks many of the common attributes that companies are looking for. If you do not know much about Sharepoint has to offer, a good research online, or meet with SharePoint professional to help you understand the benefits of using SharePoint can have. However, this entry is intended to clarify the more specific technical barrier and solutions.
It is not uncommon for people to create a single site, multiple sites, multiple document libraries and then tons of traditional folders. This is not surprising: this is what people are used to. Novice SharePoint users do not know that SharePoint can be developed without the use of traditional folders, non sense institutional. Document library for the beginner it seems closest to the traditional folder. Therefore, people naturally want to fill it with subfolders.
The reality is that traditional folders are the source of many problems in Sharepoint. They create restrictions with search and much Opoznajte performance.
So what is the closet Sharepoint is equivalent to the structure of the old traditional folders? Let me give an example:
If you have a top-level data share called public, and inside was 5 subfolder called finance, ADMIN, HR, sales and marketing. It will be presented as follows:
PUBLIC
ADMINISTRATOR
FINANCE
HR
MARKETING
SALE
Each of those will probably have some of the files and subfolders in them, and these subfolders will probably have subfolders. This is called "nested folders. This is a big no-no in SharePoint. Path, it will appear in SharePoint, if done correctly, like this:
The PUBLIC is a site collection (the top-most node)
The administrator of a subsite of the public
General documents-document library
Finance Branch of the State
General documents-document library
HR State child
General documents-document library
MARKETING subsidiary of the State
General documents-document library
SALES subsidiary of the State
General documents-document library
In other words, each folder is replaced with a single site with traditional in a single document library. Subfolder of the traditional again replaced by a single child node to a single document library. This does not mean that you can't structure a little differently; You could have 5 libraries of various documents under 1 site or another site collection for each Department in your company. This example is just to illustrate the most similar equivalent in SharePoint to a proportion of traditional folders, advanced functionality, without losing the ease of navigation.
Once you understand the structural opportunity and believe me, there are many, many more than that outlined above, you can move forward in translating your old folder structure in SharePoint. If you have a small number of folders, and then manually create the ideal, but once you start getting above 100 shared folder, it starts to become clear that some automation tools are going to be worth the cost. There are several on the market, but they are expensive, even compared with someone manually makes it all work. Two major players really targeted at enterprise customers, and thus they have sufficiently high base price. In addition they charge per GB transferred, and he gets to the astronomically high very quickly.
Less "migrants", I've seen a few thousand dollars and seem incomplete. Because often a little bit of tweaking and a bit of support needed, these companies no-name are hardly worth the headaches and risks. Best value right now seems to be working with SharePoint consultants, who have created their own funds and can make the transfer for you at a much lower price set. In the future, it is likely to be easy and free, but now is very good value would be complete for $ 500-$ 2000 by someone who worked with the possibility of advance planning it out. These migratory flows will actually build the structure of the repository folder in the path I outlined above. Configuration is available, but it takes time, and as always, time is money.
In order to truly master SharePoint lets you must first understand what opportunities exist for the site and document library. After that, you need someone in your organization or consultant who can actually use this knowledge to create and administer the system over time. In most of the smaller organizations, I've seen even when they have this guy in the House, this is usually a good idea to draw a credible consultant SharePoint for the first few months at least. The knowledge that you or your IT administrator with a win, will cost as actual tasks work was carried out on the basis of a SharePoint consultant.
Look for more articles on SharePoint in the future.
Have questions? jmarcato@thirdwaveit.com
http://www.LinkedIn.com/in/johnmarcato
0 comments:
Post a Comment