Custom Search Center in SharePoint 2013

本文介绍如何规划、设置和管理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:

Other blogs and documentation that you may want to read:

### 光流法C++源代码解析与应用 #### 光流法原理 光流法是一种在计算机视觉领域中用于追踪视频序列中运动物体的方法。它基于亮度不变性假设,即场景中的点在时间上保持相同的灰度值,从而通过分析连续帧之间的像素变化来估计运动方向和速度。在数学上,光流场可以表示为像素位置和时间的一阶导数,即Ex、Ey(空间梯度)和Et(时间梯度),它们共同构成光流方程的基础。 #### C++实现细节 在给定的C++源代码片段中,`calculate`函数负责计算光流场。该函数接收一个图像缓冲区`buf`作为输入,并初始化了几个关键变量:`Ex`、`Ey`和`Et`分别代表沿x轴、y轴和时间轴的像素强度变化;`gray1`和`gray2`用于存储当前帧和前一帧的平均灰度值;`u`则表示计算出的光流矢量大小。 #### 图像处理流程 1. **初始化和预处理**:`memset`函数被用来清零`opticalflow`数组,它将保存计算出的光流数据。同时,`output`数组被填充为白色,这通常用于可视化结果。 2. **灰度计算**:对每一像素点进行处理,计算其灰度值。这里采用的是RGB通道平均值的计算方法,将每个像素的R、G、B值相加后除以3,得到一个近似灰度值。此步骤确保了计算过程的鲁棒性和效率。 3. **光流向量计算**:通过比较当前帧和前一帧的灰度值,计算出每个像素点的Ex、Ey和Et值。这里值得注意的是,光流向量的大小`u`是通过`Et`除以`sqrt(Ex^2 + Ey^2)`得到的,再乘以10进行量化处理,以减少计算复杂度。 4. **结果存储与阈值处理**:计算出的光流值被存储在`opticalflow`数组中。如果`u`的绝对值超过10,则认为该点存在显著运动,因此在`output`数组中将对应位置标记为黑色,形成运动区域的可视化效果。 5. **状态更新**:通过`memcpy`函数将当前帧复制到`prevframe`中,为下一次迭代做准备。 #### 扩展应用:Lukas-Kanade算法 除了上述基础的光流计算外,代码还提到了Lukas-Kanade算法的应用。这是一种更高级的光流计算方法,能够提供更精确的运动估计。在`ImgOpticalFlow`函数中,通过调用`cvCalcOpticalFlowLK`函数实现了这一算法,该函数接受前一帧和当前帧的灰度图,以及窗口大小等参数,返回像素级别的光流场信息。 在实际应用中,光流法常用于目标跟踪、运动检测、视频压缩等领域。通过深入理解和优化光流算法,可以进一步提升视频分析的准确性和实时性能。 光流法及其C++实现是计算机视觉领域的一个重要组成部分,通过对连续帧间像素变化的精细分析,能够有效捕捉和理解动态场景中的运动信息
微信小程序作为腾讯推出的一种轻型应用形式,因其便捷性与高效性,已广泛应用于日常生活中。以下为该平台的主要特性及配套资源说明: 特性方面: 操作便捷,即开即用:用户通过微信内搜索或扫描二维码即可直接使用,无需额外下载安装,减少了对手机存储空间的占用,也简化了使用流程。 多端兼容,统一开发:该平台支持在多种操作系统与设备上运行,开发者无需针对不同平台进行重复适配,可在一个统一的环境中完成开发工作。 功能丰富,接口完善:平台提供了多样化的API接口,便于开发者实现如支付功能、用户身份验证及消息通知等多样化需求。 社交整合,传播高效:小程序深度嵌入微信生态,能有效利用社交关系链,促进用户之间的互动与传播。 开发成本低,周期短:相比传统应用程序,小程序的开发投入更少,开发周期更短,有助于企业快速实现产品上线。 资源内容: “微信小程序-项目源码-原生开发框架-含效果截图示例”这一资料包,提供了完整的项目源码,并基于原生开发方式构建,确保了代码的稳定性与可维护性。内容涵盖项目结构、页面设计、功能模块等关键部分,配有详细说明与注释,便于使用者迅速理解并掌握开发方法。此外,还附有多个实际运行效果的截图,帮助用户直观了解功能实现情况,评估其在实际应用中的表现与价值。该资源适用于前端开发人员、技术爱好者及希望拓展业务的机构,具有较高的参考与使用价值。欢迎查阅,助力小程序开发实践。资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值