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

Tune analytics concept #241

Open
jwjacobson opened this issue Mar 6, 2024 · 0 comments
Open

Tune analytics concept #241

jwjacobson opened this issue Mar 6, 2024 · 0 comments

Comments

@jwjacobson
Copy link
Owner

Right now each RepertoireTune stores last_played, which is useful for making sure you don't go too long without playing a tune. Each time a tune is "played," the value of last_played is overwritten.

But what if I want to see what tunes I play most often over a given span of time? For example, last night I played Dewey Square and Green Dolphin St. I've been practicing the former regularly to master the melody, whereas I hadn't played the latter in some time. If you look at the two of them now in my account, you wouldn't know the difference; both have a last_played of March 6. I've already added a play_count field which increments by 1, but the other nice thing would be to track when each play occurred.

The most intuitive way to me to implement this would be with an ArrayField called plays. A play is simply the date or datetime when the tune is played, and is appended to the array. last_played becomes a derived field, plays[-1].

This would then allow various visualizations over time (Bob has written an article on using Chart.js), seeing which tunes you play most often, or representations of different sets of tunes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant