Spca2014 search queries explained svenson

•

2 likes•486 views

This document provides an overview of search queries in SharePoint, including crawled and managed properties, Keyword Query Language (KQL), FAST Query Language (FQL), result sources, query variables, and query rules. It explains how these components work together to power search experiences on SharePoint pages using the Content Search Web Part (CSWP). Key entities like columns, crawled properties, managed properties, and result sources are mapped to shape search queries and results. Query rules allow promoting certain results or blocking others based on business needs. The document aims to explain the end-to-end search orchestration capabilities in SharePoint.

Search Queries Explained
Mikael Svenson –Principal Consultant
@mikaelsvenson–mikael.svenson@puzzlepart.com –techmikael.blogspot.com

Dev by day –Super Hero by Night
with great power comes great responsibility

I will not cover
•Managed property weights
•Full-text indexes in detail
•Custom rank profiles
•Graph Query Language (GQL v1)

I will cover
•Overview of components involved in a search page
•Crawled and Managed Properties
•Keyword Query Language (KQL)
•FAST Query Language (FQL)
•Result Sources
•Query Variables
•Query Rules
•Orchestration using Content Search Web Part

Overview
Web Part
Result Source (Scope)
Result Type
Item Template
Control Template
Search Index
Search Result Web Part
CSWP is hard set

Crawled and Managed Properties
Column InternalName
Title
CrawledProperty
ows_Title
Managed Property
Title
Column InternalName (taxonomy)
MyLocation
CrawledProperty
ows_MyLocation,ows_taxId_MyLocation
Managed Property
owstaxidMyLocation
Column InternalName (date)
ArticleStartDate
CrawledProperty
ows_ArticleStartDate,ows_q_DATE_ArticleStartDate
Managed Property (type text)
ArticleStartDateOWSDATE
use Date00 / RefinableDate00

What makes a SharePoint column/field searchable?
Managed Property
Crawled Property

What makes a SharePoint column/field searchable?
Crawled Property
Managed Property
Included inFull text-index
Not included inFull text-index
Searchable
NotSearchable
ColumnSearchable
x
✓
x
✗
x
x
✓
x
x
✓
x
x
✗
x
x
✗

KQL -Demo
contoso
contosomarketing
contosoOR marketing
((contosoOR marketing) OR (sales)) NOT bistro
author:julian
author:julianauthor:garth
author:julianAND author:garth
author:garthtitle:sales
size:50..100
write:“thisweek"
write:"lastmonth"
contosoNEAR(2) marketing
contosoONEAR(3) marketing
marketing ONEAR(3) contoso
contosoXRANK(cb=10) marketing

KQL -Demo
GP0|#<guid> All items tagged with term
GPP|#<guid> All child items of term, but not the term
GTSet|#<guid> All terms in term set
All Departments
owstaxIdDeptTaxonomy:"GTSet|#8ed8c9ea-7052-4c1d-a4d7-b9c10bffea6f"
Engineering (only have one level)
owstaxIdDeptTaxonomy:"GP0|#c7284168-2c56-460c-bb37-743a62b4ba57"

FQL –It’s all really FQL
•More operators
•starts-with
•ends-width
•filter
•..http://msdn.microsoft.com/en-us/library/office/ff394606(v=office.15).aspx
•Perhaps not for human input
•Refinement filters by default are FQL –ranking will be different

FQL Demo –It’s all really FQL
•KQL: contosomarketing
•FQL: and("contoso", "marketing")
•KQL: ((contosoOR marketing) OR (sales)) NOT bistro
•FQL: andnot(or(or("contoso", "marketing"), "sales"),"bistro")
•FQL: title:starts-with("knowledge")
•Perhaps not for human input
•Refinement filters by default are FQL –ranking will be different

Result Sources
•Think of them as 2010 scopes with sorting powers
•What should be included or omitted?
•SSA, Tenant, Site Collection, Site Levels
•GUIDs change on import for SearchConfigexport/import

Query Variables –web part on page to filter page tag against people
•{?} notation –exclude if empty
•{} notation –don’t add quotes
•{|} notation –multi-value expansion
•User
•Page
•QueryString
•Custom ones –inject in page or webpart
•User segments -> query rules

Query Rules
•Triggering
•Rewrite
•Reorder –only one
•Groups with stop/continue
•Result Blocks

Search Orchestration
•Create seven result sources (two for triggering)
•Create two query rules –above and below the fold
•Add result blocks per rule
•Edit page, reconfigure CSWP to use above sources
•Use asyncfor the below the fold web parts

Summary
•You are the conductor!
•You are responsible for making the connections between
•Column -> cp-> mp-> result source -> query rule -> web part
•Result type -> display template -> web part

Turning Business Rules into Query Rules
It’s all about..

This document provides an overview of search queries in SharePoint, including: - Crawled and managed properties which make columns searchable - Keyword Query Language (KQL) and FAST Query Language (FQL) for constructing queries - Result sources for defining the scope of searches - Query rules for rewriting and reordering query results - Using the Content Search web part for search result orchestration across a page

How and When to Use FalcorJS

Wiredcraft

C# 9 - What's the cool stuff? - BASTA! Spring 2021

Christian Nagel

Solving text search problems with Ruby on Rails

Andrii Gladkyi

OAF Syllabus

Fusion Oracle

This document provides an overview of Oracle Application Framework (OAF) and covers topics such as the model, view, and controller aspects of OAF applications. It discusses building basic OAF pages and regions, lists naming conventions, and demonstrates how to perform common operations like searches, creates, updates and deletes using OAF. The document also reviews more advanced OAF concepts such as switcher, bundled exceptions, file uploading and integration with workflows. It concludes with sections on deploying OAF projects, personalization, and extending the framework.

Search api d8

Dropsolid

This document provides an overview of search functionality in Drupal 8. It discusses that Drupal 7 had two main search solutions that could not be combined, while Drupal 8 search aims to integrate these solutions and provide a common, flexible search system out of the box. It describes the basic architecture including servers, indexes, backends, trackers, datasources, and processors. It also outlines changes for Drupal 8 like supporting multiple entity types in one index and multilingual/multisite search.

Azure App Configuration with .NET applications

Christian Nagel

This document discusses using Azure App Configuration to centrally store configuration settings for .NET applications. Azure App Configuration provides a managed configuration store in the cloud with different pricing tiers. It integrates with .NET applications using managed identities for authentication. The document also covers refreshing settings without app restarts, mapping environments to different configuration stores, using feature flags, and integrating with Azure Key Vault for secrets management.

State of Search, Solr and Facets in Drupal 8 - Drupalcamp Belgium 2015

Dropsolid

Session: http://leuven2015.drupalcamp.be/sessions/state-search-solr-and-facets-drupal-8 Presenters: Nick Veenhof & Joris Vercammen Description: In this session I'll give you an overview what changed so far in Drupal 8 in regards to the Search eco-system. We will talk about Search API, Apache Solr, Facet API and Elastic Search. Over the course of the last 3 years I've been involved in how Search in Drupal 8 should take form and what needed to change to merge the Apache Solr module with the Search API Solr module. In this presentation I hope to give you some guidance what is still pending and what already was done. I will also try to explain what effort it takes to push and move such projects. Depending on the audience we can go really in-depth or stay general. Please let me know in advance what you expect from this session so I can tailor it to your needs!

This document introduces db4o, an object persistence service for the OSGi framework. It discusses some of the limitations of traditional databases and serialization for storing objects. Db4o allows storing and querying objects directly without needing to map them to tables or write SQL. It supports native queries on objects using closures or predicates. Db4o provides pure Java object persistence with automatic schema management and is optimized for the OSGi environment.

Developers Guide to Cosmos DB

Seven Peaks Speaks

Laravel and SOLR

Peter Steenbergen

Apache Calcite (a tutorial given at BOSS '21)

Julian Hyde

The document provides instructions for setting up the environment and coding tutorial for the BOSS'21 Copenhagen tutorial on Apache Calcite. It includes the following steps: 1. Clone the GitHub repository containing sample code and dependencies. 2. Compile the project. 3. It outlines the draft schedule for the tutorial, which will cover topics like Calcite introduction, demonstration of SQL queries on CSV files, setting up the coding environment, using Lucene for indexing, and coding exercises to build parts of the logical and physical query plans in Calcite. 4. The tutorial will be led by Stamatis Zampetakis from Cloudera and Julian Hyde from Google, who are both committers to

Railsで作るBFFの功罪

Recruit Lifestyle Co., Ltd.

This document discusses using Rails as a backend for front (BFF) layer in a microservices architecture. It describes how Rails was used to build the BFF layer for an e-commerce site called HPB, acting as an API gateway between the client and various backend services. Key points discussed include using Puma to improve throughput, caching APIs to reduce response time, and implementing an API gateway to further optimize network performance between the BFF and backend services.

OData support in Cast Iron 7.5.1

Sarath Ambadas

This document discusses OData support in Cast Iron version 7.5.1.0. It provides an overview of OData, describes how Cast Iron supports exposing and consuming OData APIs, and lists some common OData URL patterns and activities for working with OData in Cast Iron projects. Key points are that Cast Iron 7.5.1 supports OData version 4.0 and exposing OData APIs for GET and DELETE calls, but does not support Cast Iron acting as an OData client or exposing APIs for POST and PUT requests.

State-of-the-Art Drupal Search with Apache Solr

guest432cd6

PHP, the GraphQL ecosystem and GraphQLite

JEAN-GUILLAUME DUJARDIN

Creating a GraphQL API is more and more common for PHP developers. The task can seem complex but there are a lot of tools to help. In this talk given at AFUP Paris PHP Meetup, I'm presenting GraphQL and why it is important. Then, I'm having a look at the existing libraries in PHP. Finally, I'm diving in the details of GraphQLite; a library that creates a GraphQL schema by analyzing your PHP code.

Webinar: What's new in Neo4j 2.0

Neo4j

This document summarizes the key new features in Neo4j 2.0 including: 1) The introduction of node labels which allow nodes to have multiple labels to identify and categorize nodes and improve query performance. 2) Schema indexing which allows indexes to be created for labels based on a property for simple lookups. 3) The MERGE operation which combines MATCH and CREATE to either match existing graph data or create new data if no match is found. 4) Transactions now being mandatory for all database interactions to improve consistency and isolation. 5) Various Cypher query language changes and improvements focused on making queries easier to write and read.

Introduction to GraphQL: Mobile Week SF

Amazon Web Services

AWS Mobile Week at the San Francisco Loft Introduction to GraphQL GraphQL is a query language for APIs and a runtime for fulfilling those queries. It gives clients the power to ask for exactly what they need, which makes it a great fit for modern web and mobile apps. In this talk, we explain why GraphQL was created, introduce you to the syntax and behavior, and then show how to use it to build powerful APIs for your data. We will also introduce you to AWS AppSync, a GraphQL-powered serverless backend for apps, which you can use to host GraphQL APIs and also add real-time and offline capabilities to your web and mobile apps. You can follow along if you have an AWS account – no GraphQL experience required! Level: Beginner Speaker: Rohan Deshpande - Sr. Software Developer Engineer, AWS Mobile Applications

Agile api dev Into the Box 2018

Ortus Solutions, Corp

This document discusses Postman, an API development tool. It provides an overview of Postman's features for building and testing APIs, including its request builder GUI, collections for organizing requests, environments for managing variables, integrated tests, and documentation generation capabilities. The document also explains how Postman can be used in an agile development process to facilitate collaboration and continuous integration through features like mock servers, monitoring, and integration with build pipelines.

BarCamp cloudsearch

kopertop

Chris Moyer, VP of Technology at Newstex, introduced Amazon CloudSearch, a fully managed search service. CloudSearch is powered by the same search engine used on Amazon.com and provides search domains, indexing of documents and metadata, and APIs to search and return results and facets without AWS credentials. It can help with indexing and searching when used alongside DynamoDB for metadata storage. CloudSearch is an expensive but powerful service that saves development time by providing features that would otherwise need to be built.

Tips for Tuning Solr Search: No Coding Required

Acquia

Helping online visitors easily find what they’re looking for is key to a website’s success. In this webinar, you’ll learn how to improve search in ways that don’t require any coding or code changes. We’ll show you easy modifications to tune up the relevancy to more advanced topics, such as altering the display or configuring advanced facets. Acquia’s Senior Search Engineer, Nick Veenhof , will guide you step by step through improving the search functionality of a website, using an in-house version of an actual conference site. Some of the search topics we'll demonstrate include: • Clean faceted URL’s • Adding sliders, checkboxes, sorting and more to your facets • Complete customization of your search displays using Display Suite • Tuning relevancy by using Solr optimizations This webinar will make use of the Facet API module suite in combination with the Apache Solr Search Integration module suite. We'll also use some generic modules to improve the search results that are independent of the search technology that is used. All of the examples shown are fully supported by Acquia Search.

Oracle APEX Nitro

Marko Gorički

This document discusses using APEX Nitro to improve the APEX development process. APEX Nitro allows developers to write CSS and JavaScript locally and have changes automatically synced to their APEX application. It provides features like error handling, minification, concatenation, and preprocessing to boost performance and maintainability. The document reviews how to install, configure, and use APEX Nitro to enhance the front-end development experience.

Speed Up Your APEX Apps with JSON and Handlebars

Marko Gorički

The document discusses various methods for generating JSON from SQL queries in Oracle APEX applications. It compares manually concatenating strings, using the apex_util.json_from_* procedures, the PL/JSON library, the APEX_JSON API package, and Oracle REST Data Services (ORDS). The APEX_JSON package is recommended for most cases as it supports generation and parsing, can be used standalone, has a light footprint, and makes conversion from XML easy. Using a templating engine like Handlebars.js with JSON is also presented as a way to dynamically render HTML from database queries.

Entity Framework Core 1.x/2.x Advanced

Christian Nagel

Entity Framework Core is Microsoft's modern object-database mapper for .NET. It is smaller and more lightweight than the original Entity Framework, supports multiple platforms beyond Windows, and is architecture-independent of relational databases. The document highlights several key features of EF Core such as code first modeling, logging, context pooling, model definition, shadow properties, query filtering, keyless entity types, migrations, relationships like inheritance and references, and support for NoSQL databases like Azure Cosmos DB. Questions are welcomed from attendees about using EF Core for their applications and projects.

Flex/Flash meets HTML5 Family

Sho Ito

This document discusses how Flex can meet HTML5 capabilities through various APIs. It summarizes Flex's ability to leverage the HTML5 Web Storage API, Geolocation API, and Web SQL Database through corresponding ActionScript libraries. The Web Storage API allows storing key-value pairs in the browser through Session Storage and Local Storage. The Geolocation API obtains the user's location. And the Web SQL Database provides an SQL interface for storing data locally. Flex can interface with these HTML5 APIs through ActionScript using ExternalInterface to call JavaScript functions, enabling offline Flash applications using HTML5 features.

A smarter Pig: Building a SQL interface to Apache Pig using Apache Calcite

Julian Hyde

What if Apache Pig had a SQL front-end and query optimizer? What if Apache Calcite was able to use Pig and MapReduce to run queries? In this project, we aimed to answer both questions by adding a Pig adapter for Calcite. In this talk, we describe Calcite's adapter framework, how we used it to write a Pig adapter, and how you can use this SQL interface to Pig for interactive and long-running queries. A talk given by Eli Levine and Julian Hyde at Apache: Big Data, Miami, on May 17th, 2017.

Web crawl with Elixir

이재철

This document summarizes the key steps taken to optimize a web crawler built with Elixir. It describes: 1) Moving from a producer-driven to a demand-driven architecture using GenStage to prevent memory exhaustion from the crawler producing items faster than the database could save them. 2) Adding rate limiting via TokenBucket to avoid exceeding site rate limits when crawling multiple pages concurrently. 3) Using a priority queue and supervision tree to introduce fault tolerance and allow crawling multiple sites in parallel while respecting each site's rate limits.

Meetup#2: Building responsive Symbology & Suggest WebService

Minsk MongoDB User Group

The document summarizes the development of new symbology and suggest web services using MongoDB to replace older services that had performance and scalability issues. Key points: - The services provide financial reference data and suggestions via symbols/codes accessed millions of times daily. - MongoDB was chosen for its document model, performance of 1ms average response time, and ability to store data fully in memory. - The symbology service optimizes data storage to reduce space and enable fast searches through field normalization and compression. - The suggest service uses an inverted index for partial text searches and generates suggestions from the symbology data through Amazon EMR. - MongoDB drivers for .NET provided good performance without bottlenecks.

Spca2014 sp buy orbuild goedhart

Spca2014 search queries explained svenson

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (19)

Similar to Spca2014 search queries explained svenson

Similar to Spca2014 search queries explained svenson (20)

More from NCCOMMS

More from NCCOMMS (20)

Spca2014 search queries explained svenson