NHS Guidance: Microsoft Office SharePoint Server 2007 Information Architecture
By peter.stilgoe
This guidance helps healthcare organisations apply a chosen information architecture or taxonomy within a 2007 Office system environment. Microsoft Office SharePoint 2007 Information Architecture describes how to plan and design an information architecture and provides step-by-step instructions showing how to configure Microsoft® Office SharePoint® Server 2007 with these settings.
This guidance is suitable for use by healthcare organisations that currently:
- Have content stored in local drives and file shares
- Archive records manually
- Have a basic Web server with Web master-controlled publishing
- Have not yet deployed Office SharePoint Server 2007, or have recently deployed Office SharePoint Server 2007 and wish to plan a portal structure and information architecture
Solution Accelerator – Scorecards
This solution accelerator acts as a template for configuring a management dashboard to track organisational metrics. It contains four example dashboards ranging from a primary care practice to a healthcare organisation’s CEO dashboard with metrics based on the healthcare targets for 2008. The solution accelerator also includes online guidance explaining how to customise a dashboard for a healthcare organisation’s needs.
This solution accelerator is suitable for use by healthcare organisations that currently use :
- Static paper-based documents to track performance with manually-entered performance metrics
- Static, decentralized, and highly-IT dependent reports
- Standalone spreadsheet-based analysis
More From pstilgoe
Increase your search relevancy by removing views & other irrelevant results from your Sharepoint search
By peter.stilgoe
By deafult Sharepoint search results will include ‘noise’ pages in the search results, such as views, all forms etc etc. If you dont want these to appear in your search results, which most people wont you can exlude them by creating exlude rules in the SSP.
1) Navigate to the SSP.
2) Click search settings under Search.
3) Click Crawl Rules.
Some common noise pages you may wish to include:
*://*webfldr.aspx – This will exclude all explorer view pages if you choice it as a exclude rule.
*://*mod-view.aspx* – This will exclude the Moderation view page if you choice it as a exclude rule.
*://*my-sub.aspx* – This will exclude the page with your items if you choice it as a exlude rule.
*://*allitems.aspx* – This will exclude the allitems page from the search results if you choice it as a exclude rule.
*://*allforms.aspx* – This will exclude the all forms page from the search results if you choice it as a exclude rule.
*://*/lists/* – This will exclude the list from the search results if you choice it as a exclude rule.
*://*DispForm.aspx* – This will exclude the list display form from the search results if you choice it as a exclude rule.
Now run a full crawl & youre done.
More From pstilgoe
Sharepoint Search – How features work part 1
By peter.stilgoe
Word breakers A word breaker is a component used by the query and index engines to break compound words and phrases into individual words or tokens. If there is no word breaker for a specific language, the neutral word breaker is used, in which case word breaking occurs where there are white spaces between the words and phrases. At indexing time, if there is any locale information associated with the document (for example, a Word document contains locale information for each text chunk), the index engine will try to use the word breaker for that locale. If the document does not contain any locale information, the user locale of the computer the indexer is installed on is used instead. At query time, the locale (HTTP_ACCEPT_LANGUAGE) of the browser from which the query was sent is used to perform word breaking on the query. Additional information about the language availability of the word breaker component is available in Appendix B: Search Language Considerations.
Stemming Stemming is a feature of the word breaker component used only by the query engine to determine where the word boundaries are in the stream of characters in the query. A stemmer extracts the root form of a given word. For example, ”running,” ”ran,” and ”runner“ are all variants of the verb ”to run.” In some languages, a stemmer expands the root form of a word to alternate forms. Stemming is turned off by default. Stemmers are available only for languages that have morphological expansion; this means that, for languages where stemmers are not available, turning on this feature in the Search Result Page (CoreResult Web Part) will not have any effect. Additional information about language availability for the Stemmer feature is available in Appendix B: Search Language Considerations.
Noise words dictionary Noise words are words that do not add value to a query, such as ”and,” ”the,” and ”a.” The indexing engine filters them to save index space and to increase performance. Noise word files are customizable, language-specific text files. These files are a simple list of words, one per line. If a noise word file is changed, you must perform a full update of the index to incorporate the changes. Additional information about the noise words dictionary and how to customize it is available at www.microsoft.com.
Custom dictionary The custom dictionary file contains values that the search server must include at index and query times. Custom dictionary lists are customizable, language-specific text files. These files are used by Search in both the index and query processes to identify exceptions to the noise word dictionaries. A word such as “AT&T,” for example, will never be indexed by default because the word breaker breaks it into single noise words. To avoid this, the user can add ”AT&T” to the custom dictionary file; as result, this word will be treated as an exception by the word breaker and will be indexed and queried. These files contain a simple list of words, one per line. If the custom dictionary file is changed, you must perform a full update of the index to incorporate the changes. By default, no custom dictionary file is installed during Office SharePoint Server 2007 Setup. Additional information about the custom dictionary file and how to customize it is available at www.microsoft.com.
Thesaurus There is a configurable thesaurus file for each language that Search supports. Using the thesaurus, you can specify synonyms for words and also automatically replace words in a query with other words that you specify. The thesaurus used will always be in the language of the query, not necessarily the server’s user locale. If a language-specific thesaurus is not available, a neutral thesaurus (tseneu.xml) is used. Additional information about the thesaurus file and how to customize it is available at www.microsoft.com.
Language Auto Detection The Language Auto Detection (LAD) feature generates a best guess about the language of a text chunk based on the Unicode range and other language patterns. Basically, it’s used for relevance calculation by the index engine and in queries sent from the Advanced Search Web Part, where the user is able to specify constraints on the language of the documents returned by a query.
Did You Mean? The Did You Mean? feature is used by the query engine to catch possible spelling errors and to provide suggestions for queries. The Did You Mean? feature builds suggestions by using three components:
· Query log Information tracked in the query log includes the query terms used, when the search results were returned for search queries, and the pages that were viewed from search results. This search usage data helps you understand how people are using search and what information they are seeking. You can use this data to help determine how to improve the search experience for users.
· Dictionary lexicon A dictionary of most-used lexicons provided at installation time.
· Custom lexicon A collection of the most frequently occurring words in the corpus, built at query time by the query engine from indexed information.
The Did You Mean? suggestions are available only for English, French, German, and Spanish.
Definition Extraction The Definition Extraction feature finds definitions for candidate terms and identifies acronyms and their expansions by examining the grammatical structure of sentences that have been indexed (for example, NASA, radar, modem, and so on). It is only available for English.
More From pstilgoe
How the default Document Properties in Office documents used in the default MOSS 2007 SearchCenter search results
By peter.stilgoe
1) MOSS2007 uses the “Comments” field (from Document Properties) as its description.
2) MOSS2007 does not search the keywords assigned to an Office document via Document Properties.
3) For Word, Excel and PowerPoint documents, if you search for a word that appears in the document’s description (aka the “Comments” field), then the description is displayed in the search results with the search term highlighted in bold.
4) For Word, Excel and PowerPoint documents, if you search for a word that only appears in the body of the document, then:
# for Office 2003 documents, a snippet from the body of the document is displayed in the search results, with the search term highlighted in bold. The description is not displayed, even when it exists.
# for Office 2007 documents, the description is displayed in the search results.
5) If you search for a term that only appears in the document’s “Keywords” field, then nothing is found in the search.
6) If an Office document has a title assigned in its Document Properties, then the title is used in the search results. If no title is specified, then the document’s filename (including the file extension) is used instead.
http://www.thismuchiknow.co.uk/?p=41
More From pstilgoe
Suppress Microsoft Office Document Authentication Prompt In SharePoint
By peter.stilgoe
Havnt tried it but apparently works:
More From pstilgoe
Create a XML Test Page for Search Results
By peter.stilgoe
How to create a XML test page for search results:
How to create a XML test page for search results
More From pstilgoe
This page cannot be edited in SharePoint Designer
By peter.stilgoe
If you are getting this error its because you are trying to edit a publishing page. To edit a publishing page you will need to first detach it from its ‘Master Page Layout’, now you can edit it as you wish but any changes to the master layout obviously will no longer apply to this page.



October 30th, 2009
