-
Notifications
You must be signed in to change notification settings - Fork 482
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2022 from opensearch-project/main
Code of Conduct and Conference Page update.
- Loading branch information
Showing
3 changed files
with
19 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,6 +17,7 @@ This code of conduct applies to all spaces provided by the OpenSource project in | |
* Publishing private information, such as physical or electronic address, without permission; | ||
* Other conduct which could reasonably be considered inappropriate in a professional setting; | ||
* Advocating for or encouraging any of the above behaviors. | ||
* Enforcement and Reporting Code of Conduct Issues: | ||
|
||
**Enforcement and Reporting Code of Conduct Issues:** | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported. [Contact us](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. | ||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported. [Contact us](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
speaker_name: 'jhandler' | ||
speaker_name_full: 'Jon Handler' | ||
speaker_talk_title: 'End-to-End Relevance' | ||
primary_title: 'End-to-End Relevance' | ||
title: 'OpenSearchCon 2023 Session: Jon Handler' | ||
session_track: 'Search' | ||
session_time: '2023-09-27 - 9:50am-10:30am' | ||
session_room: 'Redwood' | ||
presenters: | ||
- jhandler | ||
permalink: '/events/opensearchcon/sessions/end-to-end-relevance.html' | ||
--- | ||
|
||
Search engines give their users an almost-magical way to go from their goals to the information that meets those goals. When the items retrieved match the user's intent, then we say that they are relevant for that user and that query. "Relevance" spans much more than just the function used to rank the search results. Retrieving relevant results includes the presence of the data in the catalog, the way the data is analyzed, the methods used to augment and send the user's query, going beyond text to vector representation, feeding back user behavior, and of course, the ranking function. In this session, we'll take a broad look at how to use OpenSearch ensure that your users find the information that they need to get to where they are going, find the product they want to buy, or retrieve the data they need to solve a problem. |