August 5th Sprint Review
Sprint Goals:
- Places Search
- Federated Search (WIP)
"Places"
What are Places?
Places are the various content areas of your community. Our updated search will allow you to surface these content areas. These currently include:
- Categories
- Groups
- KBs
On the search page, a new "Places" section will be added where you can find categories, groups & knowledge bases that match your query. You can filter your places by:
- Title
- Description
- Type
Federated Search for Hub/Node
This sprint we also started work on federating search results for hub/node clients. This piece is expected to be completed in our current 2020.017 sprint.
Release Schedule:
Similarly to our Member Search page, Places and Federated Search will be released with our new Elastic Search provider later on this year. This release is being coordinated with Ops.
Comments
-
@ValR al sorry I missed this sprit demo.
How is content displayed when you click on a Place in the search results?
How does Vanilla associate content with a Place? Does search just group content based on related keywords or it it based on a user input such as tags?
The introduction of Places makes me wonder if we should publish an official lexicon of Vanilla objects to help customers better understand our product:
- Vanilla - The overall solution we provide (analogous to the world)
- Community - a top level community that unique set of users and content - (a country) ( We use the term Node but Node is not descriptive.)
- Federation - Functionality across Communities, like search (like the European Union)
- Sub-community - A section of a Node used to group content based on a top level filter such as language or product (a province)
- Category - discussions or articles on a specific topic (a city)
- Content - any user generated content: Discussions, Articles, Events
- Discussions -
- Post - the first post in a discussion
- Comments - comments on a post
- Ideas
- KB - a collection of articles in guide or help desk format
- Groups
- Events
- Places - a collection of content based on a topic
- Direct Messages
- Announcements
- Dashboard
- Hub
- Etc.
I'm sure I got some of this wrong.
1 -
I like this idea because portion of my demos I end up having to explain our lexicon mid-demo which isn’t always ideal.
Linking to examples would be helpful as well.
0 -
I'll work on something for our KB, with help from the other CSM's @Lvez
Do you think there would be value in adding a 'sometimes known as a....' as in, Discussion: Content created inside of a category, which can can contain media, text, and other elements. Inside of a discussion, there can be 'comments'. This is sometimes known as a Topic, or a Thread.
2 -
Yes, it would be good to agree on Vanilla definitions and also add the 'otherwise known as...'
We might also want to work with the product team to remove any ambiguity in our terms. For example, discussion type discussions.
0 -
Thanks for the feedback @Lvez
To answer your questions;
- How is content displayed when you click on a Place in the search results? Clicking on a place in the search results allows you to navigate to that group, category or KB's homepage
- How does Vanilla associate content with a Place? Does search just group content based on related keywords or it it based on a user input such as tags? Places are specific record types - group, categories or KBs for now. When I am viewing Places, I am not looking for content, but for a content area, that is to say an area I can post and consume content. I will be able to discover places when my keywords match the place's title or description.
I agree that a Vanilla lexicon would be valuable and help us drive consistency in the platform and our documentation.
1