Database Schema Migration

[zainfathoni]

Overview

Problem Statement

The current workflow of our database management system is too complicated and has a significant bottleneck in the manual update process. This situation hinders us from scaling up our database updater volunteers.

Solution

Therefore, we came up with a more scalable database management system.

Implications to the Website

1. The main Google Sheets file needs to be moved into another file
2. There are additional columns to operate with
3. Tanggal Verifikasi is not to be shown on the website anymore. Only the Terakhir Update field is shown.
4. Tanggal Verfikasi only impacts the ✅ checkmark status on the website.

More Context

Three weeks ago, we initiated a discussion on this Slack thread where we defined the problem statements and the potential solutions here: Penyesuaian Workflow dan Database Relawan.

Two weeks ago, the new database schema was ready to implement, but I couldn't afford to spend enough focus on this issue because we had to focus on kawalcovid19/silacak#8 for a few weeks.

Since we have deprioritised kawalcovid19/silacak#8 for now, we can resume our focus on this issue.

Current Tasks

These are the tasks we need to do to migrate the content gracefully. Please always refer to these documents to understand the expected result of the new database schema:

1. Struktur Informasi Baru Database WBW.
2. [Database Utama] WargaBantuWarga

• Implement fetch-database.ts to fetch from https://kcov.id/wbw-database #784
• Use fetch-database.ts in mirror-box.ts #785
• Write e2e tests to ensure there are no regressions introduced during the database migration #786
• Use the wbw-database.json data in the Province and Contact page according to the new logic #787