Monthly Archives: January 2014

SharePoint Will Disappear Very Soon ???

Posted by Jim on January 27, 2014
SharePoint, SharePoint 2013 / Comments Off on SharePoint Will Disappear Very Soon ???

Continue reading…

Service Pack 1 is coming…

Posted by Jim on January 21, 2014
SharePoint 2013 / Comments Off on Service Pack 1 is coming…

thCAD92IFDCommunicated  …… by SharePoint Team, on November 20, 2013 

“Today we broadly announced the upcoming availability of Service Pack 1 for Office, Exchange, and SharePoint early next year. Service Pack 1 represents a major update to SharePoint, establishing a new baseline for support, and provides customers the latest in improvements to performance, stability, and security.  It’s been an exciting year for SharePoint and we’ve been hard at work evolving features and capabilities both Online and on-premises.  As we look forward we’ll continue to deliver rapid innovation through our Office 365 service as well as continued future on-premises versions of SharePoint on our traditional release cadence of 2-3 years.  We look forward to working through future changes in the industry with you, on-premises, Online, and everything in between.”

Original Blog: http://blogs.office.com/b/office-news/archive/2013/11/20/office-2013-service-pack-1-coming-early-next-year.aspx

TIPS FOR THOSE CONTENT “FINDERS”

Posted by Jim on January 10, 2014
SharePoint 2013 / Comments Off on TIPS FOR THOSE CONTENT “FINDERS”

TIPS FOR CONTENT “FINDERS”

I recently was asked to provide some insight into the search finder processing of SharePoint Search. Here are some tips that may help you when using the SharePoint Search engine. Credit to Susan Hanley artical:

 

  1. Use OR to expand your search to include more terms. One of the reasons that you may not get the results you are looking for in search is that you are not giving the search engine enough of a clue to find what you want. It’s a good idea to use more than one word to search. If you don’t get the results you want, try adding more terms to your search. To be certain that the search engine knows how you want to connect the terms, you must separate the words with an operator. For more results, the operator is probably “OR” – and you need to make sure that you capitalize OR. (By the way, this is true for Google as well, though Google will attempt to interpret whether you mean AND or OR, it doesn’t always get it right.) It is always safest to capitalize your search operators.
  2. Use AND to narrow your search results. Most search engines, including SharePoint, assume that two words together with no operator separating them implies AND as the operator. In other words, a search for apples pears is the same as apples AND pears. Get in the habit of including the operator – in capital letters or it will be ignored.
  3. Use double quotes to find exact phrases. If you want to learn about “social media” and don’t want a bunch of results that include documents that include the word social and media – but are not about “social media,” put the term in double quotes – “social media.” This tells the search engine to find the exact phrase inside the quotes.
  4. Capitalization usually doesn’t matter in search – except for Boolean operators. Searching for Dogs is the same as searching for dogs. But, searching for Dogs OR Cats is not the same as searching for Dogs or Cats. In the first case, you will find items referring either Dogs or Cats. In the second, you will most likely find content with both Dogs AND Cats in the content because “or” will be ignored and the default operator is AND.
  5. Use property searches if you know for sure that a particular word is in the title or name of a document. You can use filename:value to search for words in the file name or Title:value to search for a term in the Title. Note: if Title is blank, the Title:value syntax will also look for the value of the file name. If Title is not blank, this query will only look at content in the TItle. This syntax is helpful to know because sometimes, you know for sure that a word is in the name of a document but you can’t remember the entire document name. Using this syntax works in SharePoint Foundation as well as “higher” versions of SharePoint. If you search for filename:festival, you will find any document with the term festival or festivals in the file name. Search appears to be interpreting this phrase as “filename contains the letters in festival.” If you search for filename:festivals, you will only get documents where the exact term “festivals” is in the filename. In other words, “filename contains all of the letters in festivals.” However, just to make things confusing, in SharePoint 2013, searching for filename:festival does NOT return documents where the plural term “festivals” is in the title. You can read more about this in the white paper because this is where things got really confusing and I’m hoping to get some more experts to explain why.
  6. Use a wildcard “*” if you want to be sure to get variations of the term you are looking for or if you are not sure about spelling. Out of the box with SharePoint 2010 search, stemming, the process of comparing the root forms of search terms to the content being searched is available but not turned on for most languages, including English. You can turn it on in the search results web part. I don’t really know why it is disabled by default. Enabling stemming would allow a search for the word run to return values such as runs, ran, and running. Or, more importantly, a search for holiday to return company holidays. If stemming has not or can’t be enabled in your environment, you can get similar – but not the exact same – results using a wildcard (the asterisk *). For example, you could type run* to get results that include runs and running. Or, type in holiday* to be sure you find company holidays. I would certainly work hard to get stemming turned on for search results – it is far more productive to return intuitive results than to make people remember my hints! But, if you can’t make that happen, the wildcard search will help get better results. However, remember that there is a difference with wildcard versus stemming in search results. The run* search will not find results with the term “ran.” I think Microsoft must have seen the light for this feature because in SharePoint 2013, stemming appears to be turned on by default.
  7. Try again. There are two search scenarios that I see over and over again when I’m watching people use their intranets. The first is that they search for something and get no results. “See,” they tell me, “I told you search doesn’t work. I search and I never get any results.” The second is that they get too many results. “See,” they tell me, “I told you search doesn’t work. I search and I get too many results.” While it is totally possible that search is having challenges because of a failure to observe hints 1, 2, and 3, it is also possible that your search needs to be re-written using different terms or a different approach. That’s where hints 4 -10 come in. I know that it would be great if search just knew what we wanted without having to write better queries. I think that the time for this is not too far way. But, for now, it’s often helpful to take another pass at writing the query differently using one of the approaches recommended in this post.

SharePoint Conference 2014

Posted by Jim on January 08, 2014
SharePoint 2013 / Comments Off on SharePoint Conference 2014

spc2014logoSharePoint Conference 2014 is just around the corner now. The Microsoft-sponsored event runs March 3 through 6 at the Venetian Hotel in Las Vegas. Microsoft is firming up the roster of keynote speakers and setting the agendas for about 200 sessions on the increasingly integrated worlds of SharePoint, Yammer, Office, Office 365 and more.

 Marketed as an event to help “connect, reimagine and transform,” there will be some 24 inclusive tracks for the four major audiences of IT professionals, developers, executives and power users.

However for season veterans it will be more of a zoo than a change to develop and grow knowledge in the product. I’m thinking the 2014 or 2015 will be the release conference and that’s the one you want to go to. The 2012 ( prerelease of SharePoint 2013) conference had over 10,000 participants which was more than anyone could have envisioned. Well considering the 2010 (prerelease of SharePoint 2010) conference had only about 2,000 participants.

But it’s all good stuff and anyone interested in drinking the Kool-Aid should mount up and ride off to the Vegas strip and enjoy the show. Social business developers will get plenty of information on creating apps for Microsoft’s recent Yammer acquisition and learn how to integrate it with SharePoint. Business-minded visitors can find many sessions ranging from Developing the Cloud-Hosted Apps with MVC5 to e-commerce solutions for Retail and SharePoint 2013 and Project and Portfolio Management in the Cloud.

One other popular feature of the conference are the many labs, which offer hands-on opportunities to play with the 2013 products and receive technical advice from the experts.