Custom Search Center in SharePoint 2013

2024-04-22 09:32

本文主要是介绍Custom Search Center in SharePoint 2013,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

A Search Center is a portal where you can search for content on your organization’s intranet. In this blog series we'll help you plan, set up and manage a Search Center in SharePoint 2013. But before we dive into the details, we’ll give you some background information and a few planning tips and tricks.

 

What’s a Search Center and how do I plan it?

A Search Center is similar to an internet search page like Bing: it has a starting page where you can enter queries. It has search result pages where you can drill into and refine search results, or you can run a new query.

On the internet, you want search to be easy, fast, and give you relevant results, and you should expect the same when you’re trying to find information on your company’s intranet. 

You'll easily get fast and relevant results with the standard Search Center in SharePoint. And if you also have a good understanding of the content on your intranet and know how people will be searching it, you can make your Search Center really shine.

Throughout this blog series, we’ll use examples from a Search Center that we in the content publishing team in Microsoft use to search for articles and other media that we have published on MSDN, TechNet and Office.com. Because we know the content, and because we know what we want to find and how we want to search for it, we’ve been able to set up the Search Center so that it suits our needs well.

This is what an empty Search Center looks like, before you start working on it:

And this is what our content publishing Search Center looks like after we set it up to fit our needs. Here, I've searched for "relevance", just as an example.

 You can see that we get results that show articles that we've published, but you can also see that we have added refiners that are meaningful to us, such as Writer and Editor. We also added several search pages, or search verticals, like Art and Interop. Later, we’ll show you how you can add search verticals and refiners to your Search Center, but before we dive into the practicalities, here are some considerations to help you plan your Search Center.

What kind of content and information is on your intranet?

When you think about your intranet, is there content that people probably want to search differently or separate from other content?

As an example, in our content publishing Search Center we have a separate search vertical to search through the illustrations, or "Art" files, that we use in our articles. So when I want to see if we already have any illustrations of a server farm, I type "server farm" as my query in the search box. On the search results page, I can simply click "Art" to view only the art results for that query.

Is the content tagged with good and consistent metadata?

Setting up your Search Center is much easier if content is well organized and consistently tagged with good metadata. It’s often well worth investing time in content quality before you crawl it, so that people can more easily find what they’re looking for in the Search Center.

In our content publishing Search Center, we work with SharePoint lists. Each content item that we publish, such as an article or an art file, has its own entry on the list. We've made sure that all the entries are consistently tagged with metadata that is important to us, for example to help us determine which product variants an article applies to. For our articles we also have rules around the titles and short descriptions we use. We’re capturing these metadata in site columns and site column values, and we have set up our Search Center so that we can easily use these values to refine on search results and quickly find exactly the information we’re looking for.

Who works with the intranet content?

Some content can benefit from being searched separately or differently than other content. Likewise, it is useful to think about the categories of people who search and how their interests differ. For example, if you work in Human Resources and you search for "vacation", you're probably looking for content related to the company's rules and regulations around holidays. If you don't work in HR and you search for "vacation", you probably want to find a SharePoint site where you can log when you're away or use a tool to request a day off.

You can create search verticals in the Search Center to display subsets of the search results that are of particular interest for certain groups of people, such as teams or departments. Or, you can create separate Search Centers. It all depends on the people who use the intranet in your organization: think about what they are searching for and how you can make it easier for them to find it.

 

Store most of the content in SharePoint

It’s an advantage if the content in your intranet is stored in SharePoint, because the SharePoint content source is different from all other types of content sources when it comes to search.

Site collection administrators have a lot of configuration and management options for content stored in SharePoint, such as adding new managed properties and editing existing ones. If you add a new managed property or make certain changes to it, you have to re-crawl the content. This is where it helps to have content in SharePoint: you can re-index individual SharePoint lists and libraries without having to crawl all SharePoint content.

Also, the SharePoint content source is the only source that you can crawl continuously. When the content changes, a continuous crawl will pick up the change and you don’t have to wait until the next incremental or full crawl completes.

 

A few words about how search works

Before you can show any search results in a Search Center, you have to crawl the content. After crawling, the content and related metadata are processed and stored as managed properties in the search index.
This is what it looks like under the surface:

  1. Our content is stored in SharePoint 2013 lists and libraries. We use site columns to store metadata about each item.
  2. When we crawl the content and the metadata, the information is processed and added to the search index.
  3. In the search index, managed properties represent the content and metadata that we crawled.
  4. The queries that we enter in our Search Center are sent to the search index, where the system tries to find matching results.
  5. Any matching results are displayed in the Search Result Web Part in the Search Center.

In the next blog posts in this series, we’ll walk you through how you can set up your own Search Center, using examples from our own experience with the Search Center for content publishers.

Upcoming blog posts in this series:

  • How to create a Search Center Site Collection and enable crawling of your content
  • How to configure the Search Results Web Part to use a new result source
  • Plan to use refiners on a search results page
  • How to add refiners to your search result page
  • How to add a custom search vertical to your search results page

Other blogs and documentation that you may want to read:

  • How to change the way search results are displayed in SharePoint Server 2013
    Bonus track: How to change the order in which search results are displayed
  • Changing the ranking of search results in SharePoint 2013
  • Build a specialized search experience in minutes with SharePoint 2013
  • Search architecture technical diagrams
  • Overview of search in SharePoint Server 2013
  • Best practices for organizing content for search

这篇关于Custom Search Center in SharePoint 2013的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/925417

相关文章

AI基础 L9 Local Search II 局部搜索

Local Beam search 对于当前的所有k个状态,生成它们的所有可能后继状态。 检查生成的后继状态中是否有任何状态是解决方案。 如果所有后继状态都不是解决方案,则从所有后继状态中选择k个最佳状态。 当达到预设的迭代次数或满足某个终止条件时,算法停止。 — Choose k successors randomly, biased towards good ones — Close

rtmp流媒体编程相关整理2013(crtmpserver,rtmpdump,x264,faac)

转自:http://blog.163.com/zhujiatc@126/blog/static/1834638201392335213119/ 相关资料在线版(不定时更新,其实也不会很多,也许一两个月也不会改) http://www.zhujiatc.esy.es/crtmpserver/index.htm 去年在这进行rtmp相关整理,其实内容早有了,只是整理一下看着方

JavaScript正则表达式六大利器:`test`、`exec`、`match`、`matchAll`、`search`与`replace`详解及对比

在JavaScript中,正则表达式(Regular Expression)是一种用于文本搜索、替换、匹配和验证的强大工具。本文将深入解析与正则表达式相关的几个主要执行方法:test、exec、match、matchAll、search和replace,并对它们进行对比,帮助开发者更好地理解这些方法的使用场景和差异。 正则表达式基础 在深入解析方法之前,先简要回顾一下正则表达式的基础知识。正则

插件maven-search:Maven导入依赖时,使用插件maven-search拷贝需要的依赖的GAV

然后粘贴: <dependency>    <groupId>mysql</groupId>    <artifactId>mysql-connector-java</artifactId>    <version>8.0.26</version> </dependency>

广度优先搜索Breadth-First-Search

目录  1.问题 2.算法 3.代码 4.参考文献  1.问题         广度优先搜索,稍微学过算法的人都知道,网上也一大堆资料,这里就不做过多介绍了。直接看问题,还是从下图招到一条从城市Arad到Bucharest的路径。  该图是连通图,所以必然存在一条路径,只是如何找到最短路径。 2.算法 还是贴一个算法的伪代码吧: 1 procedu

【0323】Postgres内核之 hash table sequentially search(seq_scan_tables、num_seq_scans)

0. seq scan tracking 我们在这里跟踪活跃的 hash_seq_search() 扫描。 需要这种机制是因为如果扫描正在进行时发生桶分裂(bucket split),它可能会访问两次相同的条目,甚至完全错过某些条目(如果它正在访问同一个分裂的桶中的条目)。因此,如果正在向表中插入数据,我们希望抑制桶分裂。 在当前的使用中,这种情况非常罕见,因此只需将分裂推迟到下一次插入即可。

[linux命令] 随笔集 center OS 7 蛋疼的改动 一个菜鸟的奋斗shit~~~

2018年7月24日17:22:30 虚拟机查看ip地址  center OS 7  最小化安装. 查看ip地址:使用ifconfig已经不适用了 , 需要使用 ip addr 可以看到 关闭防火墙命令也不是 stop iptables.service 命令了,  看下百度经验吧7 关闭防火墙系列命令 关闭防火墙: systemctl stop firewalld.service

Android Settings搜索Search方案分析

Android开发会遇到一些自写界面需要允许被搜索,或者三方应用挂靠在Settings,用户也希望能被搜索。 在知道怎么添加之前,得先了解下整个框架,才能更好地加入我们自己的代码。   这里稍微整理了下整个search database数据如何索引加载流程。 Settings搜索界面是由SearchFragment展现,当用户在Settings主页中点击搜索图标,会启动到SearchAc

SIM(Search-based user interest modeling)

导读 我们对电商场景兴趣建模的理解愈发清晰:1. 通过预估目标item的信息对用户过去的行为做search提取和item相关的信息是一个很核心有效的技术。2. 更长的用户行为序列信息对CTR建模是非常有效且珍贵的。从用户的角度思考,我们也希望能关注用户长期的兴趣。但是当前的search方法无论是DIN和DIEN都不允许我们在线对一个超长的行为序列比如1000以上做有效搜索。所以我们的目标就比较明

[LeetCode] 240. Search a 2D Matrix II

题:https://leetcode.com/problems/search-a-2d-matrix-ii/description/ 题目 Write an efficient algorithm that searches for a value in an m x n matrix. This matrix has the following properties: Integers i