Skip to main content

SharePoint 2010 - Real Search Scenario

The main thing in SharePoint development is not how to implement some piece of functionality but is the approach correct. And defining the approach is something very difficult which required experience and time.
It also required reviewing other scenarios and implementation.
So in some posts, I'm going to explain one real scenario that we have in our company  and the approach that we implemented.

The scenario:  creating document management system that will live in many site collections in one web application.

It may sounds simple - but it's not. It's a very very serios and difficult application.
And what I want to share with you is where the SharePoint 2010 Search take part. It helps us in:

      1. Webparts showing cross site collection data
      2. Finding documents and item based to our custom fields and custom content types

And while point 2 sounds absolutely normal - of course search is for searching items, point 1 is very tricky part of implementing such scenario.
I'll describe in detail the two points and the difficulties in the approaches in the next weeks.

However, the search is not in the first steps while building one application. Before that usually the development go through other things: In our project we firs build:
     - custom site definitions - base on the publishing portal; important part if we plan to create sites programmatically;
     - custom contenttypes - extremely important part; help managing the metadata and give us the ability for
            custom Add/Edit forms
            validation of the user input
            easily finding data in search results
      - webparts for retrieving data
      - workflows  - defining the live of the documents

And  then came the search functionality which will be main topic in my next posts.

...

Comments

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration       < wssawc : ClientPeoplePicker          Required ="true"          ValidationEnabled ="true"          ID ="peoplePicker"          runat ="server"   ...

SharePoint 2016: High Availability Farm Topology

MinRole concept was introduced in SharePoint 2016 and it aims to simplify the process of designing the farms. However, I still find ambiguous information about the count of servers in SharePoint 2016 farm. Let's ask ourselves the question - What is the minimum number of servers which allow High Availability MinRole farm? According to technet   we have the following options: Small High Availability (HA) MinRole farm 4 Four servers with two shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 6 Six servers with both dedicated and shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application servers ·    ...

SharePoint User Group Bulgaria

In the past year I invested my free time in activities related to the SharePoint User Group Bulgaria. This is the reason why I stopped writing in this blog. Please start following this new place  www.sugbg.com . I promise you that you will find there truly valuable content.