shift-org / shift-org/shift-docs
Evaluate unused database tables
Open
Nobody has claimed this yet.
database
documentation
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
There are a handful of database tables that are no longer used, e.g. caladdress. The application hasn't used these for about 5 years.
We should sort through them, keep what's needed, and clear out what isn't:
- Back them up in full and retain the data
- Determine if any of them may be useful for application purposes in the foreseeable future; keep those tables, if any
- Determine if any of them contain data that could be moved into the main database tables; if so, migrate the data
- Determine if any of them have data that's unlikely to change and are OK to share publicly; if so, export it as static content and make a page for it
- Drop any unused tables, via migration script(s)
- Update the
services/db/seed/setup.sqlscript
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/TABLES.md and the existing services/db/migrations directory to inventory the unused tables, then review services/db/seed/setup.sql. Done means the data is backed up, each table has a documented keep, migrate, export, or drop decision, required migrations are added, and setup.sql is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100