Friday, April 5, 2013

Search in Sharepoint

Search in SharePoint is a fairly effective tools when searching through the your site collection. For optimized use, it will be recommended that you improvise the use of metadata or other "best bets" to make estimates of what people are searching for on your site.

Normally when people are typing in the URL, it is common for them to be typing so fast that letters are forgotten or misplaced. If you were to type in gogle.com, you'll find that you are redirected to google.com. This is one of the most useful aspects of utilizing "best bets". If you're working on a SharePoint site, you're not going to be working with the URL or domain names, but rather the items which are listed in your search. It would be nice if there were a repository for everything which you needed, but many items, like the word "google" are unique. Therefore, when you're going through the resources which you have, think of the most common misspellings of the word you are working on. You'll be surprised at how much people misspell words, or perhaps not; however, it is not necessary uncommon for the most common spelling of a word to be an incorrect spelling.

The metadata which you can tag on different items will also optimize your search results. This allows for an effective search to locate items which may not have keywords embedded within the site. This might be familiar to many people who are trying to recall an event, but don't recall the event title itself. When you peruse through news headlines, frequently the title is full of keywords that roughly approximate the article itself. Some useful kinds of metadata are dates, terms, or keywords which relatively apply. Even something like the department or region where something was printed or deposited may help you in designing an efficient search engine.

Another common question might be how pages or items are ranked. This is a complicated question which isn't easily answered. The algorithm which Google uses has many different variables which change throughout the day based on the user. Things you should ask yourself when designing your search is whether or not the key words or metadata are given higher rank than actual data which is embedded in the document. Is this sufficient for identifying need? Can this be improved? How can I might this more specific?

The search engine in SharePoint can be difficult to understand, but the overhead is well worth the utility.

Crawling

If you're not familiar with crawling, I wouldn't worry about it unless you are trying to become more acquainted with a technical career. As can be derived from the term itself, the search engine has components which carry out different tasks, one of which searches the document for searched parameters. This may traverse an entire document, assuming that the document is written in readable protocol. The gatherer component saves the properties to an index store and this is what is output to you. This is a simple definition and leaves out a lot of the specifics. If you want to leave about the technical details, I would refer you to technet.


No comments:

Post a Comment