What does search allow you to do?
- Search allows you to look for and surface results across Content, Initiatives, and Ideas
- Search allows you to examine a multitude of fields including, but not limited to: Title, Author, Content Body, Attachment Names, Attachments (text search within attachments), standard fields and custom fields.
- Search allows you to find the content you need as quickly as possible
Steps To Initiate Search
- Click the search magnifying glass icon on the top navigation bar, An overlay will open with a search input field.
- Type in your query to find results
- Click on the asset to open it
- Click the X to exit the window
What shows up when you search?
- After typing in your query you will see results start to come in via the type-ahead searching
- Results are arranged by type into three categories: Content, Initiatives, and Ideas
- Search results are codified with appropriate asset type icons
- Snippets will show the matching query pieces in bold
What is the benefit of search?
- You can now search for assets across Content, Initiatives, and Ideas without having to go to separate locations
- The search now includes more exhaustive data points, providing more accurate results
- .zip files that contain text, PDFs, Docs, RTFs, and all other text-containing documents up to 10MB will surface results which was not included in the previous search
- You can leverage type-ahead searching to surface results
- You can expect a very fast and easy to use interface
- You can see Search everywhere in the app instead of in key locations
- Search results include a snippet to provide insight into why a result was returned
Global Search Logic
Use Boolean queries in global search: include AND, NOT, and OR to specify what you’re looking for.
The Kapost global search code is built to deal with "stemming."
For example, "keeled" does bring up "keel" because the stem of "keeled" is "keel." On the other hand, "kee" is just a grouping of characters not related to "keel" so it is not matched.
The Search Logic will use natural English language processing to help make words more discoverable in our search. With that in mind, “kee” is not a word in English so it doesn’t know “kee” and “keel” are related based on English syntax.