Skip to content
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

Capture some graphql query parameters for analytics #516

Open
mcannon068nw opened this issue Aug 4, 2024 · 2 comments
Open

Capture some graphql query parameters for analytics #516

mcannon068nw opened this issue Aug 4, 2024 · 2 comments
Assignees
Labels
backend Changes to the backend only priority:medium Medium priority requirement Major feature in development

Comments

@mcannon068nw
Copy link
Contributor

Basic pageviews have already been implemented via #466 but detailed analytics for graphql queries are not currently captured. While how much of the parameter set we should capture is undecided, we should at least capture gene and drug query terms to support grant development.

A method for how we might accomplish this has been generously provided by @acoffman : https://gist.github.com/acoffman/f40c92d8995d6598d479c23d125ff754

@mcannon068nw mcannon068nw added requirement Major feature in development priority:medium Medium priority backend Changes to the backend only labels Aug 4, 2024
@mcannon068nw
Copy link
Contributor Author

To add to this, we should see if perhaps we could find a way to capture ambiguous gene term selections. The idea being if a user uses the ambiguous genes tab, which gene do they select as their intended choice.

This would probably be helpful data for Anastasia to help untangle alias collisions

@mcannon068nw
Copy link
Contributor Author

Per meeting, this will be addressed when we have available developer time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Changes to the backend only priority:medium Medium priority requirement Major feature in development
Projects
None yet
Development

No branches or pull requests

3 participants