epugh opened a new pull request, #2452:
URL: https://github.com/apache/solr/pull/2452

   # Description
   
   I am working with other folks, especially Stavros Macrakis 
([email protected]),  to come up with a solution for understanding what users 
are doing in response to search results.  We have great visibility and 
understanding of an incoming query, what we do with it, and then what docs are 
sent back.   We do NOT have a way of tying that search to then what does the 
user do next, and if the following query is connected to the original one.
   
   Many teams lean on GA or Snowplow or custom code for tracking click through, 
add to cart, etc as signals, but nothing that is drop dead simple to use and 
open source.
   
   # Solution
   
   _User Behavior Insights_ is a shared schema for tracking search related 
activities.   There is a basic implementation for 
[OpenSearch](https://github.com/opensearch-project/OpenSearch/issues/12084) and 
this is a version for Apache Solr.
   
   # Tests
   
   Bats test to demonstrate the end to end use of UBI.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [ ] I have reviewed the guidelines for [How to 
Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my 
code conforms to the standards described there to the best of my ability.
   - [ ] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [ ] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended)
   - [ ] I have developed this patch against the `main` branch.
   - [ ] I have run `./gradlew check`.
   - [ ] I have added tests for my changes.
   - [ ] I have added documentation for the [Reference 
Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to