Fig 1: Jerry presenting SharePoint 2010
Fig 2: Audience viewing the SharePoint 2010 features
You can view more pictures by visiting the following URL:
http://cid-14111469622c2da2.skydrive.live.com/browse.aspx/SharePoint%20Pakistan%20User%20Group%20Meeting?ct=photos
Where to start?
Selecting a farm topology?
Single server, Small, medium, large
Capacity planning equation:
R = (P * H) + X
R: request per second
P: pages per second
H: average hits per second
X: search queries
Disaster recovery and fault tolerance strategies
Full or differential backups
Recover accidental deletions
Fault tolerance strategies
Deployment best practices
Infopath forms
Agenda
Enterprise Search Value
Architectural Changes
FAST search linguistic features
Lemmatization
Entity Extraction and Synonyms
Structural Analysis
Dictionaries
New Search experience
Configure, extend, create new
Enterprise Search Value
What’s the true value in Enterprise search?
Impose multiple layers of information architecture on top of structured and unstructured content. It helps you build a 360 degrees view of what’s happening in the company. File shares, hard drives are full of information but no one knows what’s in there. People don’t think about organizing information. People should organize the information. That’s where taxonomy comes in. We replicate information. Companies replicate information. If there is really no easy access to information then you don’t have that information. The problem is that all the documents have to be tagged with the information. This is called meta tagging.
SharePoint Search 2007
Problem with SharePoint Search! It ‘s locked. You can index data from all custom databases but you cannot impose your business rules on top of the business engine. SharePoint has its indexing engine but it is used only for people search.
FAST Search extends SharePoint server
Advantages:
High availability!
Why new search is so great? Why 2007 search was failing so badly? Important part in search engine is preprocessing. When document is normalized, all characters are normalized to the language in which they are searchable. Documents should be properly index to be searched.
Pre-processing
Doc id
Text normalization
Processing
All the magic stuff
Post –processing
Signals to indexer
Common Scenario
Search string: “looking for SP architect”
Query: “looking” and “sp” and “architect”
First result: “set of 4 dunlop sp sport 6000 tires ….”
Search engines remove noise words from the sentences.
Contextual insight
Contextual insight annotates the scope with entity metadata by extracting all the entities it can find to provide the answers. FAST understands paragraphs, addresses, names, company names, phone numbers. It also has natural language processing. Main thing is contextual support. It’s amazing.
Linguistics
Determine the language
Tokenization and normalization
Spelling and spelling variation
Anti-phrasing and stop words
Synonyms, acronyms
Pronunciation
Entity extraction
Lemmatization
Mapping of the word to its base form and base form variation. “Walk” is the base form of word “walking”. And hence this matches in both stemming and lemmatization.
Lemmatization dictionaries
Dictionaries
Nouns
Adjectives
Verbs
Blacklist
Dictionaries in SP 2010
Now you can create your own dictionaries. In SP 2010 you can do it through the UI.
Notes/Interesting topics and points
Fig 1: Bill English starting his session
What is Putability
Definition: The quality of putting content in the correct location with the correct metadata.
The degree to which we put quality information into our information management system
Truths: What goes in, must come out: garbage in, garbage out
What is findability
Definition: the quality of being locatable or navigable
The degree to which objects are easy
Putablity, findability and technology
Most are clueless when it comes to thinking about how information should go into SharePoint
Fig 2: Full room during Bill English’s session
Notes/Interesting points
| InfoPath Tip: Managing older versions | ||
| Here is a small tip to manage older versions of InfoPath forms. This is a very simple tip and the solution is available out-of-the-box but unfortunately, InfoPath developers usually ignore this built-in feature and face problems after deploying the updated forms. You may have noticed that you get "Schema validation errors found" when opening an updated form. In fact, the form fails to open and it is difficult to locate the data sources that cause the problem. This question is asked frequently in the forums where users ask for solutions to fix the problem. Some users manually upgrade the XML of existing forms to make them compatible with the new template. In the "Form Options", inside "Versioning" category, there is an option to manage version upgrades.  The drop down has three options: > Do nothing (existing forms might not work properly) > Automatically upgrade existing forms > Use custom event By default, the first option "Do nothing ..." is selected. Select the second option "Automatically upgrade existing forms" and save changes. Publish your form. This will automatically upgrade the existing forms and you won't have to update their XML manually which can be quite cumbersome if the library contains hundreds or thousands of forms which is a common scenario in big companies. Some times, it is necessary to keep the existing forms as they are and upgrade them manually if need be but that is rare. User can also take advantage of "Use custom event" option. This will add an event handler to the form where you can add your own custom code but this will be useful only if you know what changes you had made in the form. You can read more about it at http://msdn.microsoft.com/en-us/library/microsoft.office.infopath.formevents.versionupgrade.aspx. For example, you can check the version number of the form being opened and the version number of the template and if the form's version is older than the template's version then you can use custom code to handle the situation. For example, the following will give you the version numbers:
Another option is to add checks in the form using code. Suppose you added a new data source in the form. This data source will not be available in the forms based on the older template. You can check for the existence of the data source/node programmatically and handle business logic accordingly. For example, here is some sample code:
You simplly check the existence of the data source by comparing it to "null". If it's not null (node exists), run new logic for the new form else skip the new logic to keep the old forms intact. |
