-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interaction pattern #32
Comments
This conversation overlaps with #27 -- @andrewtavis I think that we should discuss the user flow (interaction pattern) here and then use that result to inform our decision in #27 afterwards. |
Copied from #27 In my mental vision of our project, the list of sources (i.e., Search) is the priority. My hope is that users would read the summary at the top of the search results and then examine the collection of links -- each with a two-sentence summary about how the source page is relevant to the search query. As such, I am leaning towards our end product being a vectorised search with summarisation as a secondary feature. @rti also motivated this earlier with his sentiment that "Wiki people are not interested in a chatbot, but a more targeted search process could impress upon them the utility of LLMs in the Wiki world." |
I can see the value of search as the main functionality and agree that we're definitely not doing chat :) The summary to me just seems like the first thing that people are going to look at as it's easier to digest and "more advanced." It also makes sense to factor in scenarios where it might be the only thing people interact with depending on the wiki, quality of the response and the user. |
Terms
Issue
Which interaction pattern do we want to implement?
Ask
Ask a full question and get a response.
Search
Enter a search string and get a summary.
Chat
Ask questions with followup.
Else
Something else?
The text was updated successfully, but these errors were encountered: