Data Requirements and Schema Design for TheRock Ingestion (Phase 1)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 16
Description
Phase: 1 Design
Labels: quartz, phase-1, design
Blocks: Phase 1 A2, Phase 1 B+C, Phase 1 D
Design work that must be completed before Phase 1 implementation can begin. All
four issues feed into the implementation — the database schema and status.json
structure must be stable before any code is written.
Subissues
- Phase 1 Design 1: Define Required Grafana Metrics (
phase1-design-1-grafana-metrics.md) - Phase 1 Design 2: Data Extraction Spec (
phase1-design-2-data-extraction-spec.md) - Phase 1 Design 3: Database Schema Design (
phase1-design-3-db-schema.md) - Phase 1 Design 4: status.json Schema Design (
phase1-design-4-status-json-schema.md)
Dependency Order
1. Grafana Metrics
↓
2. Data Extraction Spec
↓
3. Database Schema ←─ parallel ─→ 4. status.json Schema
Contributor guide
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
Read the four named design files: phase1-design-1-grafana-metrics.md, phase1-design-2-data-extraction-spec.md, phase1-design-3-db-schema.md, and phase1-design-4-status-json-schema.md, following their dependency order. Define the database schema and status.json structure so they are stable and ready for the Phase 1 implementation issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, python
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100