Difference between revisions of "Blog/Boost document findability with tags in O365"

From DIQA-Homepage
Line 177: Line 177:
 
<div>
 
<div>
 
<p>
 
<p>
<div class="row funktionen-row">
 
<!-- --><div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
 
=== Create an Enterprise Search Center ===
 
Launch the automatic tagging process for all documents in a library (or a subset) in the "Tag documents"-dialog. Inspect the tagging progress and check the tagging report after the process has completed.
 
<!-- --></div>
 
<!-- --><div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tag_a_library.PNG|x300px|center|middle]]</div>
 
</div>
 
 
<div class="row funktionen-row">
 
<div class="row funktionen-row">
 
<!-- --><div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
 
<!-- --><div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
Line 197: Line 190:
 
<div class="row funktionen-row">
 
<div class="row funktionen-row">
 
<!-- --><div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
 
<!-- --><div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== Adjust the search schema ===
+
=== Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the contents of your Sharepoint site and click on "subsites".
+
# Open the Sharepoint admin center for your tenant.
# Create a new sub site by clicking on the "New" action link.
+
# Click on the "Search" section
# A form opens where you specify the new sub site.
+
# In the Search section: click on "Search schema"
# In the template field: select "Enterprise/Basic Search Center".
+
# In the "Search schema" settings: activate the tab "Crawled properties"
# Click on "Create" to create the new seach center.
+
# Search for all crawled properties that start with the string "ows_"
 +
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
 +
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
 +
# Save the settings.
 
<!-- --></div>
 
<!-- --></div>
<!-- --><div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|x300px|center|middle]]</div>
+
<!-- --><div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|x300px|center|middle]]</div>
 
</div>
 
</div>
 
<div class="row funktionen-row">
 
<div class="row funktionen-row">

Revision as of 17:20, 29 September 2020

Main Page > Der DIQA Blog > Blog/Boost document findability with tags in O365
Blog

O365: Boost document findability with tags (September 1, 2020)


Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.

You can provide your users with a better search experience if you use search refiners. Users can further refine their search result by clicking on the refiner values, e.g. to retrieve "sales orders" or "invoices", only. Before you are able to create meaningful search refiners, you have to arrange for a couple of pre-requisites which include tagging documents with tags. This guide shows you how to automatically tag documents with their type (e.g. invoice, sales order, cv, inquiry) and how to provide search refiners that contain these document types.

Frustrating search experience without meaningful refiners:

Tagcloud

Entering the search term "order" returns a lot of irrelevant documents (e.g. a CV) and even misses some sales order documents.

Better: filter documents by type, language, etc:

Tagcloud

If you provide search refiners, then the users will be able to precicely filter for all "sales order" documents, for instance.

related products
more articles