SPTechWeb Logo
Home About Us  Advertise       
 
 
print Printable version 

Five quick tips to NOT look like a SharePoint newbie




April 23, 2013 —  (Page 2 of 2)

2. Don’t use spaces anywhere. Spaces are the termites of SharePoint. As Orkin would say: Don’t let spaces destroy your home.

First and foremost, don’t ever use them to name a column. Don’t use them to name a list. Don’t use them to name a library. Don’t use them to name a site.

Metadata (Columns) with spaces will at first seem nice. Everything is so readable. Until users ask you to use the Content Query Web Part (for example), and you have to actually do something with these columns, and you realize that a space is really the alias for %20, and you grasp the enormity of the situation and the complexity of what you have created. Termite infection—bomb the house!

There are two things to keep in mind in regards to spaces. One: SQL Server is SharePoint’s database (home), and everything you create gets saved there. The space in the name of the object you created has to be represented as something in the database, hence %20. Two: You can choose to follow my best practice, and after you create your column named “SpacesBad,” you can rename it in SharePoint “Spaces Bad.” The database still knows the column as “SpacesBad.” Win-Win.

3. Use content types. Content types are initially tough to grasp, but once you do, they are invaluable. Content types are not the same as file types; they are about the type of information associated with the file type. This information is the metadata. Instead of a deep-dive explaining what they are (which would be too lengthy), I will give you the positives to utilizing them:
• They have the ability to push a column change in a list/library to multiple sites and have the changes be dynamic
• You can use the Content Type Hub to publish your lists and libraries to other sites collections. Now you can make a change to the metadata in one list content type and have it published across site collections
• You can control auditing on a particular file type, such as legal contracts
• You can institute a workflow across multiple sites based on RFPs that enter into the system
• You can enforce consistent information across sites

4. Do not use the WYSIWYG in the Content Editor Web Part. Just this week I was working with a client who made extensive use of this Web Part. She loved putting in the information and doing links, bolding information on the Web page, and all that good stuff. Then she had to make changes and subsequently got lost in the interface.

I showed her how to use the Content Link. There are two advantages to doing this. The first is that all the HTML is now in a text file that you can manipulate. This leads to the second advantage, which is that you never have to edit the page to make changes to your HTML. This is significant since every time you edit the page, you open the page up to being corrupted in some way.

5. Don’t modify or delete anything SharePoint begets. This is a general rule. You never know when you will need to revert back to the original item. I will give you some examples:
• Assigning Content Types to a library: Typically a library will have “Document” as the main content type. If you want to add yours and not have the user to see “Document,” don’t delete it, just make it not visible.
• You need a new Content Type that is just like “Document” but has a few more metadata columns. Don’t ever modify the original content types; create a child and modify that.
• When it comes to Default.aspx pages or the Master page, do not modify the originals. Make copies and modify those.

This is my starting list when looking at a SharePoint site and determining the capabilities of the folks asking for my help. I would love to know what others in the community have encountered when dealing with SharePoint newbies. I am certain there are some great stories out there from which we all can learn.

Peter Serzo is a published author of the “SharePoint 2010 Administration Cookbook,” a founder of the SouthEastern SharePoint group, a speaker, and SharePoint Architect for High Monkey Consulting. Peter has been in the IT industry for 20 years. He has extensive experience with SharePoint implementing business solutions for several enterprise organizations over the past seven years.

Pages 1 2 


Share this link: https://sptechweb.com/link/44636

Comments


04/24/2013 01:54:59 PM EST

Love this list! To 5, I'd add the created permission groups that are created with a Publishing site. If I had a dime for every time someone "cleaned up" the groups that had access to their site and deleted the Style Resource Readers group and then came back to me with "Hey, why can't people access my site?!?!" I would have... a lot of dimes. Which, quite frankly, doesn't seem all that exciting. But you get my point.

United StatesOwen Baern


04/24/2013 02:10:18 PM EST

ALWAYS Specify/Know what version of SharePoint you are using, and make sure ANY blog post you read specifies which version of SharePoint it applies to. Like - Content Query Web Part and Content Type Hub are ONLY available in SharePoint Server, not in SharePoint Foundation or WSS environments.

United StatesSPGuy


04/24/2013 02:31:11 PM EST

Don't set a low quota on the My Site Host site collection; this is where user profile pictures are stored and if this site reaches its quota users won't be able to upload/update their profile pics.

United StatesNobody special


Add comment


Name*
Email*  
Country     






 
 
This site's content Copyright © 1999 - 2013 by BZ Media LLC, All rights reserved.
Legal and Privacy
• E-mail: