-
Notifications
You must be signed in to change notification settings - Fork 334
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
feat: generate new meeting summaries for a team #10050
Conversation
.filter((row: any) => | ||
row('meetingType') | ||
.eq('retrospective') | ||
.and(row('createdAt').ge(twoYearsAgo)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have this two year limit so that the mutation doesn't take too long, but we could remove it and just accept that it might take several minutes to complete? Otherwise, when building the Insights UI, we'll need to restrict summaries to the past two years
packages/server/graphql/private/mutations/generateMeetingSummary.ts
Outdated
Show resolved
Hide resolved
await r | ||
.table('NewMeeting') | ||
.get(meeting.id) | ||
.update({summary: newSummary, updatedAt: now}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 overwriting a user-facing value on an ad-hoc basis feels a little dirty. It means the experiments we run will be immediately visible to the user. Probably OK for now if we assume the prompt isn't going to change!
Hey @mattkrick, bumping the review request on this one 🙏 |
good to go! let's try it out & see what we learn |
Fix #10038
This PR lets Parabol super admins generate new meeting summaries for a team(s).
This is required to create a summary of summaries (#10017) as the old meeting summaries don't include quotes or links to the meeting.
Once a Parabol super admin generates new meeting summaries for a team, we'll then be able to get a better summary of summaries output.
I suggest reviewing this PR first, and then the parent: #10017
I'll create a follow-up PR that updates the meeting summary UI to handle the markdown links: #10040
I've added a Notion doc here as a guide to generate insights.
To test
cloud-sql-proxy --address 0.0.0.0 --port 5433 parabol-saas-staging:us-central1:saas-staging-postgresql-clone-for-upgrade
generateMeetingSummaries
for a given team and see the updated summaries. For a team with many meetings, it could take 30-60+ seconds to run.