The Heat in SharePoint Semantics April 20 to April 26
May 1, 2012
This week SharePoint Semantics shared a plethora of information that can be useful for Microsoft SharePoint novices and experts alike.
In the post, “SharePoint Governance Plan Perceptions Survey Phase One Released by Axceler” we learn that while many companies believe that SharePoint governance is important, almost 40 percent do not have clearly defined governance plans and 9 percent have no plans at all.
Ken Toth excerpts a portion of the article:
“Not only that, 64.9 percent viewed SharePoint as a strategic enterprise platform. It seems more than contradictory that these organizations lack a coherent governance plan, yet view governance as important and SharePoint as a strategic platform. It doesn’t bode well for these companies if they don’t see planning for governance as part of their mission.”
Another noteworthy post that would be beneficial for those using SharePoint in the field is “Improve the SharePoint Experience for Field Personnel Through Best Practices.” According to the summary of the article, there are six best practices for site-based tasks to be completed in the field.
Those best practices are:
“Keep essential information on the same page, display multiple List View Web Parts in a single page view, create a flat site structure and implement enterprise cache management to support offline work, display recent changes to the site, develop search scopes for frequently requested items, and create separate SharePoint sites for different groups of users or products.”
When we are discussing best practices, it is important to also remember that many Sharepoint end users also make the same mistakes. “Top Technical Mistakes to Avoid in Microsoft SharePoint” covers a variety of angles to worth a close look during your deployment process.
When describing the number one blunder the writer highlights the Big Bang Roll Out:
“Someone sends out an email that the new intranet site, My Sites, and collaboration platform are available. Suddenly everyone in the organization comes flooding in, and in the process, they put the entire farm underwater. The servers encounter more load in an hour than they’ll typically encounter in weeks of operation, and a great environment is tarnished by one big email. Rather than doing one big-bang email to everyone, stage your communication over the course of a day or two to even out the load a bit.”
While reading best practice and top mistake articles can help many end users address a multitude of issues that can arise when dealing with Microsoft SharePoint, at times when that just isn’t enough, we recommend that you look into a third party solution like Smartlogic’s out-of-the-box enterprise semantic technology.
Jasmine Ashton, May 1, 2012
Comments
- Subscribe to Beyond Search
Feature archive
News archive
-
My company uses SharePoint for intranet, 700 users. The company website is not run on SP but they are looking to do so. I am in the marketing area and don’t want IT getting too involved in content side of website if they host it on SharePoint. Do you know of any articles that 1. argue for different team to look after SharePoint as intranet platform, and web platform and/or 2. articles that recommend hosting websites off-site with dedicated hosting, due to downtime and security concerns if IT hosts in-house (my concerns!). Re second article topic: is there a simple case for hosting SharePoint intranet and website both internally, due to ease of sharing docs between platforms, for example? tx