ClimateMind / ClimateMind/climatemind-backend

Transform User B events analytics table to analytics table which contain events from both User B and User A

Open
#414 0 comments 0 reactions 0 assignees View on GitHub
enhancement refactoring
Dominant language
Python
Stars
24
Forks
20
PR merge metrics
No merged PRs in 30d

Description

# User story

As an analyst, I want to history log of the state changes occurring in the conversation table (when new state gets written to the conversation table, then that change should be registered as a user A event and thus make a new row in the conversations analytics table, so I know when it occurred

# Acceptance criteria

- [ ] #415
- [x] And any conversation state changes for user A need to be tracked in this conversation_analytics_data
- [x] #416

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing how the conversation table changes are recorded in conversation_analytics_data, then read linked issues #415 and #416 to establish the remaining scope. Done means the analytics table contains both User B events and User A events for conversation state changes, including when a new state is written.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, data, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.