Skip to content

MoM ‐ DBMS Team

Jump to bottom
Srishti Shetty edited this page Jul 18, 2026 · 23 revisions

Welcome to the DBMS Team wiki!

Purpose:
This document serves as a structured record of our weekly meetings, capturing key discussions, attendees, decisions, and action items. By maintaining a clear and organized log, we ensure transparency, accountability, and continuity across our team’s activities.

Scope & Accessibility: The minutes of each meeting will be documented and uploaded to the respective repository’s Wiki tab for easy reference. This documentation is publicly visible to maintain openness and facilitate collaboration.

Guidelines for Documentation:

Date & Time: Wednesday (Weekly) - 09:00 AM PST - Pacific Time (USA)

Minutes of Meeting Saayam for All - Database Team

Date: 07/15/2026 Attendees: Pallavi (Lead), Srishti (PM), Mohith, Uday, Suhas, Vanshika, Pavan

  1. Mohith • PR #243 updated with requested changes and test cases. • Assigned Tables 31–40(volunteer rating to user signoff). • To prepare SQL scripts and test cases based on Wiki schema changes. • ETA: This weekend.
  2. Uday • PR #244 submitted with test cases. • Assigned Tables 11–20(volunteer details to request table). • To prepare SQL scripts and test cases. • ETA: This weekend.
  3. Vanshika • Assigned Tables 21–30. • To prepare SQL scripts and test cases from proposed schema changes. • ETA: This weekend.
  4. Pavan • Assigned Tables 41–48. • GitHub access/issue assignment pending from Pallavi. • To prepare SQL scripts and test cases. • ETA: This weekend.
  5. Suhas • Updated User Table based on review comments. • Added test cases and raised the corresponding PR 241, review pending from pallavi • Assigned Tables 0–10 (action to user details). • ETA: Complete remaining SQL scripts and test cases by this weekend.
  6. Pallavi • Reviewed PRs and assigned remaining database migration tasks. • Instructed members to prepare SQL scripts and test cases based on the Wiki schema changes. • Requested deliverables as separate files attached to PR comments. • Confirmed all assigned work must be completed by this weekend for the microservices implementation.
  7. Srishti (PM) • Clarified the status of ~39 open GitHub issues for ScrumBan/MVP tracking. • Reminded members to update GitHub issues and mention correct issue numbers in weekly timesheets. • Scheduled a follow-up review meeting for Sunday, 9:00 AM PST.

Project Meeting Notes Project: Sequence Generator Date: July 1 2026 Attendees: • Mohith • Pallavi • Uday • Vanshika • Vikashini • Suhas • Priya Shah Discussion Summary Sequence Generator The team discussed the overall approach for the Sequence Generator, with a focus on simplifying the migration process and standardizing implementation across regions. Suhas • Revised the implementation approach. • Removed the descending approach and half-point logic. • Confirmed the Virginia region implementation does not require a prefix. • No migration scripts are required for existing users. Uday • Do not implement prefixes. • Use one common solution across all regions. • Use sequence numbers with 12 leading zeros. • Six files require updates. • A cleanup script will be needed. • Pallavi will provide the required dynamic tables. Mohith • Working on the Organization and HR tables. • Pallavi needs the Organization table by 07/02/2026. • Pallavi will review the HR tables. Vanshika • Working on the Stockholm region application. • Progress is positive. • Pallavi has updated the issue. • Continuing work related to DOB. Vikashini • Working on database cleanup. Vishaka • Will provide deliverables to Pallavi by Saturday. Open Items No communication with Gauthami for approximately one month. Follow-up may be required. Action Items Owner Action Due Date Status Mohith Complete Organization table 07/02/2026 In Progress Pallavi Review HR tables 07/02/2026 Pending Pallavi Provide dynamic tables TBD Pending Team Update 6 files TBD Pending Team Execute cleanup script After dynamic tables Pending Vanshika Continue Stockholm region work Ongoing In Progress Vikashini Complete database cleanup Ongoing In Progress Vishaka Submit deliverables to Pallavi Saturday Pending Team Follow up with Gauthami TBD Open Key Decisions • No prefixes will be used. • No migration scripts are required for existing users. • One common implementation will be used across all regions. • Sequence numbers will use 12 leading zeros. • Six files require updates before implementation.

Date: 06/24/2026 Attendees: Pallavi (Lead), Srishti (PM), Mohith, Pavan, Uday, Dhanush, Suhas, Tanvi

  1. Mohith

• Issue #218 – HR Tables; PR 232 submitted. Most implementation completed. • Working on volunteer application and internal application table updates. • Pallavi advised maintaining internal applications as a separate table/feature and updating the same PR. • Discussed trigger implementation and table structure changes. • Coordinating with Ashirvad regarding CI/CD updates; Revanth currently handling related activities. • To connect with Vanshika regarding HR table implementation details. • Priority: P1 | ETA: June 30, 2026.

  1. Pavan

• GitHub access still pending; Pallavi to follow up with HR. • Pallavi will create an issue to review database architecture and update ER diagrams. • To review Wiki documentation, update table relationships, and identify missing relationships.

  1. Uday

• Issue #239 – Sequence Generator Refactoring assigned. • To redesign request sequence generators and define separate regional ID ranges to prevent collisions across regions. • Review ADR and Wiki documentation before implementation. • Priority: High | ETA: 24 hours.

  1. Dhanush

• Working on Issue #224 – Request Table Schema Changes and Issue #222 – LLM Chat Storage (req_more_info). • Pallavi reviewed the updated requirement for Issue #224 and confirmed changes need to be made directly in the Request Table. • Test cases have been completed; scripts are pending for validation and implementation. • Pallavi acknowledged receipt of the LLM-related updates and will review the submitted changes. • Requested to prepare scripts and test cases to validate schema changes, Request Table updates, triggers, and overall functionality. • Priority: Request Table updates to be completed first. • ETA: June 27, 2026 (Friday) Action Item: Complete scripts and validation test cases for Issues #224 and #222 and share updates before the weekend.

  1. Suhas

• Assigned User ID Sequence Generator enhancement for Virginia, Ireland, and Stockholm regions issue • To evaluate both prefix-based and mathematical/range-based approaches and submit recommendations/scripts. • Regional allocations discussed (working ranges): • Virginia Region (STD Users): 1B – 10B • Ireland Region (EU Users): 1B – 10B • Ireland Region (STD/US Users – DR Support): 20B – 30B • Stockholm Region (EU Users): 20B – 30B • Stockholm Region (STD/US Users): 40B – 50B • Maintain a 10B gap between regional ID ranges to avoid collisions and support future expansion. • Ireland region should support creation/storage of Virginia users during disaster recovery scenarios. • Ensure no overlap between regional user ID ranges and maintain unique ID generation across regions. • Coordinate with Uday to align sequence generator logic and regional allocation strategy. • Srishti added for tracking and follow-up. • Priority: High | ETA: 24 hours.

  1. Tanvi

• Working on Country CSV validation task. • To validate JSON vs CSV country data, ISO codes, country IDs, EU member flag, region mapping, and Has State field. • Phone code validation not required. • Will support Suhas if needed on sequence generator implementation. • Requested to review database documentation updates in the Wiki - https://github.com/saayam-for-all/database/wiki/*-Changes-to-the-Database,-Waiting-for-Microservice • Priority: High

Discussion & Action Items • CI/CD documentation expected to be completed before the next meeting. • Multiple high-priority items require completion within 24 hours. • Pallavi continuing database documentation updates and API-related database changes.

Date: June 19, 2026 Team: Database Sector Prepared By: Priya Shah, Project Manager Executive Summary The team reviewed progress on active issues, ongoing development work, cleanup scripts, and documentation efforts. Key focus areas included Issue 210, Issues 222 and 224, cleanup script development, AWS Wiki documentation, and attribute testing activities. Several items remain pending review or follow-up actions. Mohith • Working on Error 227 with Vishaka. • Responsible for HR Table updates and maintenance. Vishaka • Completed Issue 210 file updates; awaiting Pallavi's review. • File remains in Excel format and uses the same ID structure as the JSUM file. • Rajmi will attach the finalized file. • Working on designer-related issues. • Submitted AWS Wiki content; pending validation. • Awaiting productivity credentials from Pallavi. Dhanush • Issue 224: Development complete; script submitted to Pallavi. Test cases pending. • Issue 222: Documentation submitted; additional changes required. • Reviewing trigger updates, implementing trigger logic, and incorporating encryption requirements. Uday • Continuing cleanup script development. • Virginia 3 cleanup script completed. • Submitted required script for referenced link. • Two questions posted on ticket and awaiting responses. Suhas • Updating and testing attributes. • Weekend update expected. • Dynami is also supporting this effort. • Team advised to coordinate through the group channel. Vikashni • Working on cleanup-related tasks. • Managing user table activities and additional PM assignments. Action Items

  1. Pallavi to review Issue 210 file.
  2. Rajmi to attach Issue 210 file.
  3. Pallavi to provide productivity credentials.
  4. Dhanush to write test cases for Issue 224.
  5. Team to respond to Uday's ticket questions.
  6. Suhas to complete attribute testing.

Date: 06/10/2026 Attendees: Tanvi (Lead), Srishti (PM), Vikashini, Uday, Pavan, Mohith, Vishakha, Vanshika, Arup

  1. Vikashini • Issue #179 – Development completed; unable to create PR due to "26 commits left" issue. Waiting for repository access/permissions. Follow-up with Pallavi pending. • Issue #214 – Database cleanup script mostly completed. Dynamic data cleanup script remains pending from Suhas. Documentation shared with Suhas but no update received. • Action Item: Follow up with Suhas via GitHub issue/comments for transparency. If no response, task may be reassigned or taken up directly by Vikashini & Uday.

  2. Uday • Issue #214 – Working on database cleanup activity alongside Vikashini. • Clarification required regarding identification of dynamic vs static data. • Action Item: Coordinate with Vikashini to complete pending dynamic data cleanup requirements. • Available to pick up additional tasks after completion.

  3. Pavan • GitHub and database access still pending. • Action Item: Raise access request in the team communication channel and follow up with the responsible team.

  4. Mohith • Issue #209 – Requested PR modifications completed. Updated code submitted and review pending from Pallavi. • Issue #218 – Working jointly with Vishakha. Internal applications and volunteer application work completed. • Action Item: Discuss remaining requirements with Vishakha and submit updated PR/code changes by Friday.

  5. Vishakha • Issue #218 – HR table-related scripts uploaded. Awaiting review and feedback. Working with Mohith to finalize remaining requirements. • Issue #210 – Updated country CSV file uploaded. Review pending. • Action Item: Resolve pending comments and obtain approval from Pallavi.

  6. Vanshika • Issue #215 – AWS architecture diagram and Wiki content completed and submitted. Approval pending. • Issue #180 – Script validation and testing in progress. Encountering dependency-related errors and additional script issues during execution. • Action Item: Capture errors/screenshots, discuss with Tanvi/Pallavi, update ETA in GitHub issue. • Priority: Validate script functionality and resolve testing blockers.

  7. Arup • Issue #207 - Search functionality implementation largely completed from database side. • Reviewing GenAI team documentation related to search implementation and providing feedback on technical concerns. • Fuzzy search implementation completed from database perspective. • Issue #36 / #42 – Follow-up required on AWS User Group creation and Pulumi script integration with RDS instances. • Action Item: Check status with Pallavi/DevOps team and continue Pulumi implementation once infrastructure prerequisites are available.

Discussion & Action Items • Srishti to follow up with Suhas regarding pending dynamic cleanup script work. • Uday and Vikashini to collaborate on Issue #214. • Pavan to expedite access requests through the team communication channel. • Mohith and Vishakha to connect and finalize Issue #218 updates by Friday. • Vanshika to document testing errors and update ETA for Issue #180. • Arup to verify AWS User Group creation status and coordinate Pulumi deployment activities. • Srishti to prepare and upload pending MoMs and follow up on contributor activity and timesheet validation.

Date: 05/27/2026 Attendees: Pallavi(Lead), Srishti(PM), Mohith, Dhanush, Vishakha, Vikashini, Joshitha, Uday, Pavan, Tanvi, Vanshika

  1. Mohith • Issue #218 – HR tables & organization schema updates in progress • S3 keys in volunteer table is necessary, need to go for TEXT datatype for this • Need to create new PR for the code • Need to update organization PR like attribute names, modify same SQL file, raise PR to test branch & not from main, and remove unnecessary transaction commands, ETA: Thursday • After Organizations PR changes done, need to start working on HR tables PR, can pause for 2 days • Dependency: Global ID/User ID schema decisions pending

  2. Srishti • Speak with Niriksha regarding issue #218 • Take update from Vishaka on EOD Thursday on HR table • Handling MoMs and contributor follow-ups of all other issues • Ireland region issue check on documentation after draft completed

  3. Dhanush • Issue #222 – Audit DB Tables for Temporary LLM Chat Storage in progress • Schema shared in issue comments • Composite key vs primary key discussion pending

  4. Vishaka • Issue #210 – (Resolve the Countries CSV file issues) Countries table Excel updates completed, review pending by Pallavi • Working on HR/application tracking script with Mohith #218 • Need to include page tracking, step tracking, search count, open count, and time spent tracking by EOD Thursday PST

  5. Vikashini • Dynamic cleanup script in progress • Issue #179 – PR to test branch showing unrelated table changes • Coordinating with Suhas regarding repo access • ETA: Before weekend

  6. Joshitha • Stockholm region setup scripts completed • Local testing outputs/screenshots pending before validation • Need to run the script locally against stockholm_dev_saayam_rdbms with test passwords to verify 4 test cases & check

  7. Tanvi • Reviewing disaster recovery documentation • Discussion pending on Virginia/Ireland sequence generators • Pallavi will create draft & then discuss on ireland region issue

  8. Uday • GitHub access provided • Asked to review all database issues & say what interests him & then work on that

  9. Pavan • GitHub/database access still pending • Assigned onboarding/wiki review until access approval

  10. Vanshika (text update) • Working on one implementation issue • Test scripts pending

Date: 04/22/2026 Attendees: Pallavi(Lead), Srishti(PM), Mohith, Vikashini, Sahil, Shrivatsav, Ritika, Tanvi, Joshitha, Vishakha

  1. Overall Tasks in Progress (Pallavi Update) • Stockholm region is set up; need to create PIR data (user & personal data tables) • Credentials shared for Laya, but permission issues need to be checked by someone from team • HR tables to be created on the platform for timesheets, absentee tracking, user groups, and volunteer details, including data flow from main tables to S3 • Tanvi to handle Virginia & Ireland updates and finalize scripts • Search functionality issue with GenAI assigned to Arup; queries already addressed on Slack • Pallavi to get extension permissions from Krishna and provide access to Mohith • Need a resource to write wiki page for database schema documentation • CI/CD pipeline in progress; Mohith’s suggestions reviewed, team sync planned, and code coverage to be integrated • 6 PRs pending review

  2. Srishti • Issue #21 – database side PRD review done by Pallavi, Ownership unclear for other teams (FE/BE/QA) • Contact with Rashmi, Ramya team leads Pallavi suggested • Next: Follow up via leads, recheck requirements of BA issue #21 so that nothing missing from database side, share MoM, track timesheets

  3. Mohith • Organization table & schema setup completed • Issue #209 in progress • Issue #206 (CI/CD) → Recommendations shared, meeting scheduled 4/23/2026 9am PST • Pending: Test cases • Needs support for pg_stat_statements extension • Next: Recheck and raise queries if needed

  4. Vikashini • Audit 2 test cases in progress • Blocker: Incorrect branching (fork instead of main) • Pending: Audit 3 • Next: Fix branching, coordinate with Mohith, add comments

  5. Sahil • YML script for DB code coverage completed (awaiting review) • Based on primary key logic • Pending: PR rejection logic • Next: Extend logic, integrate into CI/CD

  6. Shrivatsav • Working on documentation and diagrams #206 • Next: Add main branch → DB flow, discuss in meeting scheduled 04/23/2026

  7. Ritika • Next: Participate in CI/CD discussion, join meeting scheduled 04/23/2026

  8. Tanvi • Highlighted Saumya needs a next task • Next: Support PR reviews and issue handling

  9. Joshitha • Assigned Stockholm region setup • Next: Validate setup, create DB/schema, integrate PIR data, review regions • Dependency: Await credentials

  10. Vishakha • Audit 2 support completed • Pallavi will assign next issue start working from tomorrow • Next: Work on test cases

Actions Required from Pallavi (Lead)

• Share credentials (Ireland & Stockholm) with Joshitha & Tanvi • Assign a few issues to Joshitha & Tanvi and remove yourself from those; they will handle PR reviews • Review Sahil’s YML script along with other 5 PRs pending review, total 6 • Provide pg_stat_statements extension to Mohith after checking with Krishna • Update the Stockholm region issue with clear details/instructions for Joshitha • Assign tasks to Vishakha, Saumya, and Suhas by EOD (04/22/2026, PST) • Start member removal process with Srishti (PM) • Review tracker (priorities, ETA) once prepared by Srishti • Attend CI/CD pipeline discussion meeting (Issue #206) tomorrow 4/23/2026 9am PST

Date: 04/15/2026 Attendees: Srishti, Mohith, Vishakha, Vikashini, Tanvi

  1. Mohith • Status: o Issue #206 (CI/CD) → Recommendations shared, awaiting review o Issue #209 → In progress (PR raised, new branch created) • Blocker: Issue #161 → Requires pg_stat_statements extension for testing • Next Steps: o Complete scripts + test files for #209 (ETA: Friday) o Continue Git updates • Dependencies: Pallavi (extension + review) • Extensions: pg_stat_statements (Issue #161)

  2. Vishakha • Status: Issue #160 - creating snippets for audit 2 → Completed • Next Steps: Need a new task • Dependencies: Pallavi (review + task allocation)

  3. Vikashini • Status: o PR issue #211 persists despite creating branch from main o Test cases created and shared (review pending) • Blocker: o Unable to proceed further due to unresolved PR issue o Confusion on branch creation (repo vs fork) • Next Steps: o Resolve PR issue o Reach out to Pallavi directly for resolution • Dependencies: Support required for PR issue resolution + guidance)

  4. Tanvi • Status: Working on Virginia & Ireland integration scripts • Blocker: Pending sync with Pallavi for execution • Next Steps: o Finalize scripts o Connect next week for execution • Dependencies: Pallavi (execution alignment)

Actions Required from Pallavi (Lead)

• Enable pg_stat_statements extension, audit 3 (Issue #161 - Mohith) • Review: o CI/CD recommendations (#206 - Mohith) o Issue #160 - creating snippets for audit 2 • Assist in resolving: o PR issue #211(Vikashini) • Connect with: o Tanvi (integration execution alignment) • Assign tasks to: o Vishakha

Date: 4/8/2026 Attendees: Srishti, Joshitha, Gowthami, Tanvi, Mohith, Sahil, Vikashini, Suhas

  1. Joshitha • Status: Working on Stockholm instance setup • Blocker: Dependency on Krishna & Pallavi • Next Steps: Continue follow-ups; update Git issue with status • Dependencies: External coordination (Krishna)

  2. Gowthami • Status: o Issue #211 (Mapper Tables) → In progress (ETA: 2 days) o Audit Test Cases #163 → Completed (pending upload) o Help categories #90, review pending • Blockers: None • Next Steps: o Complete Issue #211 and raise PR to test branch o Upload audit test cases for review o Provide progress updates in Git • Dependencies: Pallavi review needed for 2 issues & help needed in #211 issue

  3. Tanvi • Status: Working on Virginia & Ireland integration scripts • Blocker: Pending sync with Pallavi for execution • Next Steps: o Schedule discussion with Pallavi o Proceed with script execution post alignment o Follow up on ERD updates (draw.io edits) • Dependencies: Pallavi (execution alignment), Vanshika (ERD updates)

  4. Mohith • Status: o #159, #161 → Completed o #206 (CI/CD) → Recommendations shared, awaiting review o #209 → In progress • Blocker: o Issue #161 → Requires pg_stat_statements extension for testing • Next Steps: o Continue work on #209 o Update based on CI/CD feedback o Proceed with alternative approach if extension is delayed • Dependencies: Pallavi (extension + review) • Extensions: pg_stat_statements (Issue #161)

  5. Sahil • Status: Code coverage script + automation completed; shared in GitHub • Blockers: o Pending Pallavi review o Possible permission constraints for workflow changes • Next Steps: Proceed after review and confirmation on permissions • Dependencies: Pallavi (review + permission clarity)

  6. Vikashini • Status: o PR issue persists despite creating branch from main o Test cases created and shared (review pending) • Blocker: Unable to proceed further due to unresolved PR issue • Next Steps: o Resolve PR issue o Complete review and proceed with next steps (test case validation) • Dependencies: Support required for PR issue resolution

  7. Suhas • Status: No issues assigned; onboarding in progress • Next Steps: Await issue assignment • Dependencies: Pallavi (task allocation), GitHub access requested

Actions Required from Pallavi(Lead)

• Enable pg_stat_statements extension, audit 3 (Issue #161 - Mohith) • Review: o CI/CD recommendations (#206 - Mohith) o Code coverage script (#185 - Sahil) o Audit Test Cases once uploaded (#163 - Gowthami) o Help categories (#90 - Gowthami) • Assist in resolving: o PR issue #211(Vikashini) • Connect with: o Tanvi (integration execution alignment) o Stockholm dependency (Joshitha / Krishna) • Assign tasks to: o Suhas

Date: 4/1/2026 Attendees: Pallavi, Srishti, Vikashini, Mohith, Vishakha, Vanshika, Tanvi, Joshitha

  1. Srishti • Recording and creating MOM for this meeting as PM. • Shared update on search functionality - Issue #90 (combined with GenAI team). • Pallavi asked to check if Arup reviewed the document she sent and confirm the plan ahead. • Arup to review ER data; Srishti to update in Slack and the relevant issue for continuity.

  2. Vikashini Issue #179 • Had trouble creating a PR, had pulled from test branch instead of main, with manual changes to supporting language column names. • Pallavi: Never pull from test branch - always pull from main. Test branch has unnecessary commits. • Current PR to be cancelled. Vikashini to fix the branch, create a new one from main, and raise a fresh PR targeting test. Audit 2 (with Vishakha) • Posted test case scenarios in the shared document; audit query is finalized and optimized. • Pallavi: Do not post actual database numbers in public GitHub issues. • Pallavi: Do not commit the transaction during audit script testing - only capture outputs, then close without committing. • To complete test cases within 2 days.

  3. Mohith Audit 3 • Excluded Step 3 (snapshot table check) as discussed; wrote test cases for remaining steps 1, 2, 4, total 10 snippets. • Needs to cross-check views; may require a PG statement extension - permission previously managed by Mohan. • Pallavi to review test cases; will explore snapshot table vs view alternatives and update in the issue. Issue #206 - CI/CD Pipeline • Added to the database repository CI/CD pipeline proposal for review. • To go through the final proposal and add any additional suggestions in the comments. • Saturday meeting scheduled (makeup for last week) to sync on further issues.

  4. Vishakha • Working on Audit 2 alongside Vikashini. • Pallavi: Provide actual scripts, not just subheadings in the documentation - a full script is needed. • Pallavi: Remove herself from the onboarding task issue as that work is complete.

  5. Vanshika DOB PR Issue • Raised PR to main instead of test branch; only included the update command. • Pallavi closing this PR. Vanshika to raise a new PR with 3 files: DDL command, users table changes, and a test case all targeting the test branch. Issue #45 - ERD • Assigned to complete ERD work (issue #45) with Tanvi's permissions. • Pallavi to share database credentials so Vanshika can verify the ERD against the actual database and reflect it in the draw.io diagram.

  6. Tanvi • ERD (Issue #45) partially complete; remaining parts to be done by end of this week. • Pallavi: Post the draw.io file link (not PNG) in the issue so Vanshika can make edits. • To grant Vanshika edit permissions on the draw.io file.

  7. Joshitha • Needs Pallavi's help for Stockholm work - to connect personally today. • BA team: Clarified 2 MVP issues raised by the BA team; database-side work is done. • Health category: Joshitha was only asked about user categories, not health. Pallavi to confirm with Gowthami whether health category inquiry is a separate item. • Pallavi has raised issues and committed; may assign Joshitha and Tanvi to the issue for review & feedback. • Plan: Connect today evening for Stockholm instance creation → Ireland and Virginia region changes with Tanvi → Saturday call for QA instance creation.

MOM: Database & GenAI Search Sync

Date: March 13, 2026 Participants: Arup, Srishti (DB); Varshini, Aakash, Kavana (GenAI)

Meeting Goal: Syncing on universal search progress to ensure both teams are aligned and to avoid any duplication of work.

Current Progress & Technical Split:

  1. Database Team (Arup): Stage 1 (Setup & Foundation) is complete. Currently in Stage 2 (Schema replication & testing). Arup has implemented Fuzzy Search (using pg_trgm) so searching "Arun" correctly finds "Arup."
  2. GenAI Team: Working on "Universal Search" and "Confident Search" (Exact matches like IDs should redirect users to the specific page).
  3. The Plan: DB team handles Dashboard-level/Fuzzy search (Names/Skills); GenAI team handles Global/Confident search (IDs/Transactions).

Key Takeaways:

• Varshini (GenAI Lead) offered to let one of her team members assist Arup to accelerate the fuzzy search implementation. • The teams discussed creating a Parent Issue to link DB Issue #184 and AI Issue #90 for easier tracking. • Arup raised a UX question: Should an exact ID match automatically redirect the user or just display the result?

Next Steps & Decisions Needed from Pallavi:

• Entity Mapping: We need to finalize the list of entities (Users, Orgs, Skills, etc.) and decide exactly which ones use Fuzzy vs. Confident search so we can divide the work. • Resource & Workflow: Do you approve of Arup collaborating with a GenAI team member to speed things up? Also, should we move to a Parent Issue format to keep both teams synced? • Collaboration Logistics: We need to define which specific days and what method (e.g., creating a forked search branch) both teams will use to work together.

Git links:

GenAI - https://github.com/saayam-for-all/ai/issues/90 Database - https://github.com/saayam-for-all/database/issues/184

Date: February 25, 2026 Lead: Pallavi Total Attendees: 10

  1. Mohith

New joinee, completed onboarding. Self-assigned a starter issue in Git. Pallavi will assign him a task(issue). Instructed to use database credentials from Parameter Store when required, steps she will share to retrieve credentials.

  1. Srishti

Asked for Stockholm project progress (as asked in Monday PM meeting by Sharanya) to Pallavi. Updated database meeting time on Git contact page to wednesday from monday. Pending confirmation from Arup; update/comment to be added in Git after alignment today.

  1. Gowthami

Continuing work on Code Coverage – Pillar 2. If category changes are made, unit tests must validate health category tables. Required to demonstrate code coverage unit tests to Rao. Working on Audit 1 and Audit 5 (February).

Focus: Data integrity and validation. All February changes must reflect in Audit 5. Reference audits (2025) shared by Pallavi. Expected progress by this weekend. Pallavi to share additional references in assigned Git issue.

  1. Vikashini

Working on Audit 2 and Audit 3. Uploaded queries/scripts to Git. Audit 2:

Integrated scripts. Required corrections:

 Refer to `pg_stat`.
 Add filtering for all database users (request, volunteer, special team, etc.).
 Avoid limiting only to admin user.
 Use credentials from Parameter Store.

Recheck all subsections. Audit 3:

Step 2 and Step 4 completed. Additional Task:

Review users and user_additional tables. Identify language1, language2, language3 attributes. Write DML scripts linking them via foreign key references. Pallavi to share full database user list. LLM can be used for logic support if needed.

  1. Jasmitha

Working on Sentiment table (DDL script). Emergency contact related tasks:

Requirement changed to S3 storage. Database changes on hold. Issue 16 (Local emergency phone numbers) – On hold (S3 based). Issue 182:

Validate EU-affiliated countries list (27 countries). Correct incorrect flags (e.g., London incorrectly marked True). Optimize EU flag validation query in database. Deadline: 2 days. Coordinate with Tanvi for Ireland region validation.

  1. Joshitha

Shared documentation (PDF) on instance creation. Next focus: Replication setup.

Replicate only users and user_additional tables. Ireland → Stockholm. Filter unnecessary tables. Instance creation targeted by weekend. Pallavi to coordinate DMS activation with DevSecOps. Working on Audit 4:

Write script to validate data type issues before finalizing audit. Priority: Stockholm replication over Audit tasks. Srishti to update Sharanya regarding documentation completion and replication progress.

  1. Tanvi

Issue 123 (Timezone handling):

Confirmed microservices save default UTC. Decision: Add default GMT at attribute declaration level (not triggers). Parts 2, 3, 5 completed. Part 4 pending; to complete today. Issue 183 – External IDP tracking:

Create 20-character Provider ID attribute. Add external login provider column in users table. Store provider details (e.g., Gmail, LinkedIn, Facebook, Instagram). Ireland region replication:

Sync Virginia → Ireland → Stockholm. Clean integration issues. Write DML scripts for Virginia region. Sync discussion with Pallavi on Friday.

  1. Sahil

Working on Issue 183 – Court coverage / Zoom functionality validation. Created script under Pillar 1 to validate table. Required to create generalized validation script:

Primary keys Foreign keys Indexes Constraints Checks To begin Pillar 4 – Integrity & Security coverage. Code coverage to combine all 4 pillars. Update Wiki page with use cases.

  1. Vanshika

Completed onboarding. To support Tanvi on Virginia region tasks. Pallavi to assign structured issue.

Attendees: Pallavi Chitrada, Ashutosh Khobarkede, Sharanya Gowda

Topics Discussed: Reviewed the project tracker, updated outstanding issues, and accurately categorized them for improved tracking and resolution.

Action Items: [List of action items with assigned owners and deadlines, if applicable]

Date: 08/18/2025 Attendees: Pallavi (Team Lead / Database Head) Sharanya (Project Manager) Harathi (New Volunteer) Gopi (Database Contributor) Ashutosh (Project Manager)

Topics Discussed: The meeting opened with a brief onboarding update. Pallavi confirmed that several new volunteers, including Harathi, had completed their onboarding tasks and are awaiting assignments. She emphasized the need for all team members to complete the onboarding form to help track active contributors. Current work focuses on issues #35 and #36, which involve collecting and structuring country and state data. Pallavi clarified the repository workflow — the primary development branch (pallavi-chitra) is awaiting review and approval from Mohan before merging into the main branch. Database credentials and IAM access are temporarily on hold until the updated master credentials are finalized. A major portion of the discussion addressed database automation. The team agreed on developing automated scripts for inserting CSV data related to help requests, organizations, and metadata tables. Clarifications were provided regarding “population scripts,” confirming they refer to structured CSV files, not code. The schema for help categories will be refined to handle multiple data types, such as lists for preferred meal types. Additionally, Pallavi introduced the use of Pulumi scripts for managing multiple environments and encouraged members to familiarize themselves with it. She also reiterated the importance of using the group chat for updates and queries to ensure better coordination.

Action Items: All Members: Complete onboarding and status forms; use the group chat for coordination. Pallavi: Finalize and share the wiki page with credentials and tool documentation. Mohan: Review and approve the pallavi-chitra branch for main merge. Gopi & Team: Develop automation scripts for CSV data population; update country, state, and city files. Arjun: Implement automation for the organization table. Project Managers: Finalize schema decisions for help categories and metadata. Volunteers: Explore Pulumi scripts for environment setup and future deployment tasks.

Date: 08/12/25

Attendees: Pallavi Chitrada, Tanvi Mahajan, Anusha Gurugubelli, Arup Chauhan, Gowthami Abbaraju, Jasmitha Sri Akurathi, Joshitha Uppalapati, Siddhant Survase.

Topics discussed: ● Tanvi Mahajan's Progress (Issue 95): Tanvi has completed the script preparation for the Ireland region and uploaded the document to the development branch. She is currently working on the next task, which is ensuring uniformity in datetime attributes. She was instructed to raise another Pull Request (PR) to the main branch but not accept it. Tanvi was also advised to compare the script with the actual database, specifically checking for trigger functions that might not be in the main branch. She was told to prioritize the integration issue and try to resolve it by Wednesday because production is scheduled for the 19th.

● Arup Chauhan's Progress (Pulumi Script): Arup is working on the Infrastructure as Code (IaC) Pulumi script and has created a local script for testing. He needs credentials for AWS VPC and a subgroup to proceed with complete testing. He was advised to join the DevOps team group and drop a text message about needing permissions.

● Anusha Gurugubelli's Progress (Audit Scripts): Anusha and Gowthami have both written scripts. Anusha's alternative script only runs in PGAdmin using PostgreSQL syntax. The speaker plans to cut some work with them and will create three subcategories for audit issues: security and access audit, operational/resource handling audit, and data integrity and validation audit. Anusha asked for an update on the schema diagram documentation, which the speaker will pick up.

● Gowthami Abbaraju's Progress (Audit Scripts and Health Categories): Gowthami is ready to work on the subcategories for audit scripts once they are created. She was told that the health categories have changed and that the same issue will be reopened with the necessary changes.

● Jasmitha Sri Akurathi's Progress (Wiki Pages): Jasmitha is working on wiki pages for enum tables and was asked to post the link in the issue comments. ● New Tasks for Jasmitha Sri Akurathi: She was assigned two new tasks: updating the existing "comments" table using ALTER commands to link it with the "request" table, and creating a new "about us" table.

● Missing Attendees: Pratamesh, Ankita, and Snail were not at the meeting, and Siddhant Survase will follow up with them. The speaker also asked about Chitendra Gudu and Gopichand, who had not been heard from.

● Joshitha Uppalapati's Task (Save and Continue): Joshitha is currently handling the "save and continue" issue. The speaker said they would handle this issue and complete it by tomorrow, and advised her to start a new request from Wednesday. Her new task is to check the relationships of the "organization" table with the "users" table, as a CSV file was deleted and a new mapping table is needed.

Action items: ● Tanvi Mahajan: Raise another PR to the main branch for Issue 95 but do not accept it. Recheck the script with the actual database, especially for any missing sequence functions. Write a message to the group listing any functions present in the database but missing from the main branch. Compare the script with the database and push any changes to the development branch. Prioritize the integration issue and aim to resolve it by Wednesday. Create a new Draw.io diagram for all 43 tables, make it public, and give access to the 11 people working on DB.

● Arup Chauhan: Create a new branch for the IaC Pulumi script. Join the DevOps team group. Post a message in the DevOps group requesting permissions for the VPC and security group ID needed for testing. Block a time slot in the calendar for the weekly meeting link.

● Anusha Gurugubelli: Continue working on the audit script. Post the current documentation for the schema diagram in the comment section.

● Gowthami Abbaraju: Stay after the call to connect with the speaker regarding the health categories issue.

● Jasmitha Sri Akurathi: Post the link to the wiki pages for enum tables in the issue comments. Work on the ALTER commands to update the "comments" table to link it with the "request" table. Create the "about us" table. Complete the new table scripts and submit them to the test branch by today or tomorrow, before the scrum.

● Joshitha Uppalapati: Check the relationships of the "organization" table with the "users" table. Receive credentials for the database from the speaker.

Date: 15/12/2025 Attendees: Pallavi Chitrada, Arup Chauhan, Jashmita Sri Akurathi, Joshitha Uppalapati, Tanvi Mahajan, Prathamesh Raut, Vikashini Sabarinathan, Siddhant Survase

Topics discussed: ● MVP and Infrastructure The group discussed the 1.0 MVP being based on the development stage, which necessitates getting the Virginia and Ireland regions ready. They will need to go over to the infrastructure and create a QA environment after the 1.0 MVP. ● Pulumi Scripts Arup Chauhan gave an update on receiving credentials for the AWS VPC and testing, and mentioned that he needs to study the Pulumi script part. He plans to finish the Pulumi script part by Friday. Pallavi Chitrada inquired about whether database definition language (DDL) and data manipulation language (DML) scripts need to be in a Pulumi script format. Arup Chauhan confirmed that Pulumi can orchestrate and manage databases, such as creating or updating an RDS instance. ● QA Instance Pallavi Chitrada clarified to Arup Chauhan that the next subtask is creating a QA instance, which is the same as the development instance but needs to be created for both regions. In the development stage, they are using a public setup, but QA, staging, and production environments will be private. ● Emergency Contact Data Jashmita Sri Akurathi shared the latest Excel file and discussed a sorting error in the country names. Pallavi Chitrada explained that the numbering in the current list should match the order in the countries table, using country ID as a foreign key and state ID as a foreign key for the US. ● Volunteer Application Trigger Joshitha Uppalapati discussed an update to a trigger for volunteer applications. Pallavi Chitrada corrected the logic, stating that insertion into the volunteer details and user skills tables should only happen when the application status is "approved" or "accepted," and the row should be deleted from the volunteer application table after insertion. They also discussed adding a second link for a government ID path in the volunteer_details table. ● Database Updates and Naming Convention Tanvi Mahajan mentioned working on the ER diagram and addressing an inconsistency in date column naming (update date vs. updated date) across tables. The team decided to use last_updated_at with a timestamp without a time zone for consistency. ● ER Diagram Task Tanvi Mahajan has completed about 10 tables for the ER diagram. Pallavi Chitrada asked Vikashini Sabarinathan to take over the remaining 15 tables for the ER diagram. ● Database Connection Demonstration Pallavi Chitrada demonstrated how to connect to the database using PGAdmin, including setting up the connection with the host, database name, port, username, password, and setting the SSL mode to "required". ● Project Timeline The plan is to complete all changes in the Virginia region by Wednesday, have a final lookup on Thursday, change the Ireland region on Friday, and wait for API calls on Saturday and Sunday.

Action items: ● Arup Chauhan will finish the Pulumi script part by Friday. ● Arup Chauhan needs to see the code and read up on the integration aspects regarding the database scripts and what is expected for deploying instances. ● Jashmita Sri Akurathi needs to adjust the order of countries and states in her data to match the numbering in the countries table, and ensure the country ID and state ID are correctly synced. She should use "text" for the ID column before insertion and ensure the list of countries is complete. ● Jashmita Sri Akurathi needs to follow up on missing country data. ● Joshitha Uppalapati needs to remove the deletion from user_skills in the middle of the trigger function. ● Joshitha Uppalapati needs to remove government_id_type and add another ID column (e.g., government_id_path_2) to volunteer_details. ● Joshitha Uppalapati needs to create the pull request (PR) with only the three tables: volunteer_details, volunteer_applications, and user_skills, including testings and a clear, brief explanation of the trigger and tables involved. ● Tanvi Mahajan and Prathamesh Raut need to make a list of tables that need to be changed for the consistent date column naming convention (last_updated_at with a timestamp) by Wednesday. ● Tanvi Mahajan will share the current ER diagram with the team. ● Tanvi Mahajan should post the ER diagram link in the comment section of the issue (issue 45). ● Tanvi Mahajan and Pallavi Chitrada plan to update the Ireland region on Friday. ● Vikashini Sabarinathan needs to complete 15 tables for the ER diagram using the database or GitHub. ● Vikashini Sabarinathan should request the ER diagram from Tanvi Mahajan. ● Vikashini Sabarinathan needs to disconnect from the database after completing her work. ● Pallavi Chitrada will create a couple of other tables, including a new user table.

Date: 05/01/2026

Attendees: Pallavi Chitrada, Joshitha Uppalapati, Vikashini Sabarinathan, Tanvi Mahajan, Anusha Gurugubelli, Arup Chauhan, Siddhant Survase

Topics Discussed: ● Existing Issues and Improvements: Pallavi Chitrada inquired about existing feature issues and necessary improvements. ● Audit Scripts: The status of who took up the audit scripts issue was addressed. ● Task Assignments: ○ Joshitha Uppalapati: Asked to help Tanvi with Ireland integration. Later assigned to research automation and capacity calculations and create a wiki page for documentation on testing and capacity calculation. ○ Vikashini Sabarinathan (Vikashini): Assigned to address preferences and split the user table, and to list out additional user table attributes by tomorrow before the scrum call. ○ Tanvi Mahajan (Tanvi) and Pratamesh: Discussed synchronizing column names (like updated_at) across tables to ensure consistent data types. Tanvi was asked to compare Ireland and Virginia scripts for table merges by Wednesday. ● Schema and Database Care: Pallavi Chitrada emphasized the need to handle schema changes carefully, as they are reflected across QA, stage, and broad instances. Changes should be made in this release. ● Scrum Call Time: The scrum call time for the next day was tentatively set for 10:00 a.m. PST. ● Anusha's Work: Anusha had completed the audit script for microservice user and was working on issues 161 (connectivity and session audit) and 160 (traffic audit). She was asked to share her files in a Google Doc and attach the link in the comment section. ● Arup's Work: Arup updated a wiki page for the Pulumi script. He was waiting for details on creating RDS instances for the EU region. Pallavi mentioned she asked Moan to review the wiki page and would follow up with him. Arup was asked to focus on the testing part for the QA instance of the Pulumi script rather than direct creation. ● Database Credentials and Permissions: Pallavi announced plans to change database usernames and passwords and exchange all permissions for database users (Ireland and Virginia) by the weekend and requested all integration tasks and table changes be completed before Thursday. ● MVP 1.0 Tasks: Everyone was asked to list out their assigned 1.0 MVP tasks and links in the group and comment on each issue asking if database support is needed. ● Time Sheet and Assignment Issues: Siddhant was informed about Gauri Parmar and Lokesh Jeswani assigning themselves tasks (like 163) and possibly filling out time sheets and was instructed to report them to HR.

Action Items: ● Joshitha Uppalapati: Help Tanvi with Ireland integration. Research and create a wiki page for automation and capacity calculations, including documentation on testing and capacity planning. List assigned 1.0 MVP tasks and links in the group. Comment on all assigned 1.0 MVP issues asking if database support is needed. ● Vikashini Sabarinathan: Address preferences and split the user table. List out additional attributes of the user table in the RDBMS WhatsApp group by tomorrow before the scrum call. ● Tanvi Mahajan: Look into merging tables in the Ireland region by comparing Ireland and Virginia scripts by the end of Wednesday. ● Anusha Gurugubelli: Put documentation and script files (including micro service user script and connectivity/session audit script) in a Google Doc and attach the link in the comment section of the issue. ● Arup Chauhan: Go through the Pulumi script documentation again and provide feedback on necessary permissions/access. Perform testing on the QA instance creation part of the Pulumi script and produce screenshots of the output. ● Pallavi Chitrada: Discuss the preferences and user table splitting with Vikashini in the scrum call. Talk to DevSecOps team about their handling of infrastructure and Arup's Pulumi script access. Follow up with Moan for the review of Arup's Pulumi wiki page. ● All Attendees: Complete all integration things, table creations, and updations before Thursday due to planned database credential changes. List assigned 1.0 MVP tasks and links in the group. Comment on all assigned 1.0 MVP issues asking if database support is needed. ● Siddhant Survase: Request a status update from everyone not present at the meeting. Report Gaurav Parmar and Lokesh Jeswani to HR regarding self-assignment and time sheets. Ensure meeting links are updated.

Date: 1/12/2025 Attendees: Pallavi, Swayansiddha (Swan), Vikashini, Joshitha, Tanvi, Ashutosh Others Mentioned: Prachi, Rashmi, Anusha, Gautami, Prathmish, Justmita

Topics discussed: Onboarding & Access: Swayansiddha still lacks GitHub access. Pallavi will coordinate access and assign onboarding tasks. DB team focus recommended. Database & Schema Work: DEV instances ready. Team will proceed with schema improvements, table pluralization, and user table refactor (user_additional_details). Changes to be coordinated and applied together. Audit Automation: Audit scripts to be automated for permissions, usage, and operational performance. Vikashini: Main audit issues and user table changes Joshitha: Operational performance audits and sample scripts Target: complete before QA instance creation. Regional Sync (VA & IE): Tanvi and Prathmish to ensure schema parity, including last_updated columns. Changes planned for Thursday. Meeting Storage Design: Approved normalized schema (meetings + meeting_attendees) instead of JSON for analytics and integrity.

Action items: Pallavi: Request GitHub org membership for Swayansiddha; assign onboarding tasks; review PRs and documentation. Swayansiddha: Provide GitHub repo name/ID and engage once access is granted. Vikashini: Post comments/PR for issue 179 and audit sub-issues; review Anusha’s documentation and implement audit scripts as needed; complete before Wednesday night if possible. Tanvi: Prepare ALTER scripts for column changes (last_updated additions, emergency numbers), add function/trigger comments, coordinate with Prathmish; schedule Thursday morning for changes. Joshitha: Implement sample operational performance scripts (issue 16); later prepare capacity calculation document; coordinate with CI/CD team for integration. Team: Coordinate Thursday morning session to apply schema changes across Virginia and then sync Ireland; test operational audits and update documentation.

Clone this wiki locally