Skip to content

Latest commit

 

History

History
1297 lines (929 loc) · 36.2 KB

File metadata and controls

1297 lines (929 loc) · 36.2 KB
title OSM-Notes-Analytics Documentation
description Comprehensive documentation index for OSM-Notes-Analytics data warehouse and ETL
version 1.0.0
last_updated 2026-01-25
author AngocA
tags
documentation
analytics
data-warehouse
index
audience
data-engineers
developers
data-analysts
project OSM-Notes-Analytics
status active

Documentation Directory

This directory contains comprehensive documentation for the OSM-Notes-Analytics project, including architecture diagrams, data dictionaries, testing guides, and CI/CD documentation.

Overview

The documentation provides detailed information about the data warehouse design, ETL processes, testing strategies, and development workflows.

Documentation Index

Core Documentation

  • Rationale.md: Project motivation, background, and design decisions
  • Troubleshooting_Guide.md: Centralized troubleshooting guide for common problems and solutions

data warehouse Documentation

Data Flow Diagrams (DFD) - System Data Flow

  • DFD Level 0: Context diagram (system and external entities)
  • DFD Level 1: System decomposition (Extract, Transform, Load, Export)
  • DFD Level 2: ETL process detail
  • Data stores and data flow descriptions
  • Process descriptions and frequencies

Contents:

  • Context diagram showing system boundaries
  • Process decomposition diagrams
  • Data store documentation
  • Data flow descriptions
  • Incremental vs full load flows

Audience: Data engineers, system architects, business analysts

When to read:

  • Understanding overall data flow
  • Designing new data pipelines
  • Troubleshooting data flow issues
  • Explaining system to stakeholders

Data Lineage - Complete Data Traces

  • Complete lineage paths from source to destination
  • Column-level transformations and mappings
  • Business rules applied at each stage
  • Dependencies between processes
  • Impact analysis for schema changes

Contents:

  • Lineage diagram (source → staging → DWH → datamarts → JSON)
  • Detailed transformation rules for each path
  • Dimension lineage (users, countries, dates)
  • Business rules documentation
  • Data quality checks
  • Impact analysis

Audience: Data engineers, data quality analysts, compliance officers

When to read:

  • Understanding data transformations
  • Debugging data quality issues
  • Impact analysis (what breaks if source changes)
  • Compliance and auditing
  • Onboarding new team members

Business Glossary - Terms and Key Metrics

  • Business definitions for core terms (Note, Resolution, Active User, etc.)
  • Key metric definitions from business perspective
  • Calculation formulas and interpretations
  • Business rules and their rationale
  • Example calculations

Contents:

  • Core business terms (Note, Resolution, Community Health, etc.)
  • Key metrics overview (historical counts, resolution, applications, content quality)
  • Business rules documentation
  • Example calculations

Audience: Business analysts, product managers, stakeholders, new team members

When to read:

  • Understanding core business concepts
  • Getting overview of available metrics
  • Communicating with non-technical stakeholders
  • See also: Metric Definitions for complete 77+ (countries) and 78+ (users) metrics reference

Metric Definitions - Complete Reference

  • Comprehensive definitions for all 77+ (countries) and 78+ (users) metrics in datamarts
  • Detailed business definitions, formulas, and interpretations
  • Organized by category (Historical, Resolution, Applications, Content, Temporal, Geographic, etc.)
  • Metric summary tables

Contents:

  • Historical count metrics (30+ metrics across time periods)
  • Resolution metrics (7 metrics: avg, median, rate, by year/month)
  • Application statistics (4 metrics: mobile/desktop counts, most used)
  • Content quality metrics (5 metrics: length, URLs, mentions, engagement)
  • Temporal pattern metrics (5 metrics: working hours, activity heatmap, peak dates)
  • Geographic pattern metrics (15+ metrics: countries, users, rankings)
  • Community health metrics (5 metrics: backlog, active notes, age distribution)
  • Hashtag metrics (8 metrics: usage, top hashtags, favorites)
  • First/Last action metrics (8 metrics: dates and note IDs)
  • User classification (1 metric: contributor type with 23 types)
  • Metric interpretation guide
  • Metric calculation details

Audience: Data analysts, BI developers, dashboard builders, business analysts

When to read:

  • Building dashboards and reports
  • Understanding all available metrics
  • Interpreting metric values
  • Comparing metrics across users/countries
  • See also: Business Glossary for core terms

Dashboard Analysis - Data Availability and Recommendations

  • Analysis of data available in star schema vs datamarts
  • Dashboard implementation recommendations
  • Gap analysis and enhancement suggestions
  • Recent enhancements documentation

Contents:

  • Star schema data availability
  • Datamart metrics overview (77+ for countries, 78+ for users)
  • Dashboard-ready data analysis
  • Implementation phases and recommendations
  • Completeness checklist

Audience: Dashboard developers, data analysts, product managers

When to read:

  • Planning dashboard implementation
  • Understanding available metrics
  • Identifying data gaps
  • See also: Dashboard Implementation Guide for implementation details

Dashboard Implementation Guide - Step-by-Step Instructions

  • Complete guide for building dashboards
  • SQL queries and frontend integration examples
  • Performance optimization tips
  • Best practices and troubleshooting

Contents:

  • 8 dashboard types with complete examples
  • SQL queries for each dashboard type
  • JavaScript/frontend integration code
  • Performance optimization strategies
  • Error handling and best practices

Audience: Frontend developers, dashboard builders, full-stack developers

When to read:

  • Building dashboards from scratch
  • Integrating with frontend applications
  • Optimizing dashboard performance
  • See also: Dashboard Analysis for data availability

User Personas and Use Cases - User-Centered Design

  • 6 detailed user personas with backgrounds and goals
  • 18+ specific use cases organized by persona
  • Query patterns and dashboard recommendations
  • Common workflows and best practices

Contents:

  • Individual Contributor persona
  • Community Leader persona
  • Data Analyst persona
  • Campaign Organizer persona
  • Researcher persona
  • System Administrator persona
  • Use cases for each persona
  • Query patterns and recommendations

Audience: Product managers, UX designers, developers, stakeholders

When to read:

  • Understanding user needs
  • Designing features and dashboards
  • Prioritizing development work
  • See also: Dashboard Implementation Guide for implementation

Machine Learning Implementation Plan - Future Enhancement

  • Complete plan for implementing ML capabilities
  • Use cases: resolution time prediction, note classification, at-risk detection
  • Architecture and technical requirements
  • Step-by-step implementation guide
  • Data requirements and model specifications

Contents:

  • 3 main use cases (resolution prediction, classification, risk detection)
  • Available data for training (facts table + datamarts)
  • Model architecture (regression, classification, binary classification)
  • Implementation architecture (Python ML service + PostgreSQL)
  • File structure and integration points
  • Training data requirements
  • 5-phase implementation plan (8-12 hours)
  • Technical requirements and dependencies
  • Expected outcomes and performance metrics
  • Maintenance and monitoring guidelines

Audience: Data scientists, ML engineers, system architects, project managers

When to read:

  • Planning ML implementation
  • Understanding ML requirements
  • Evaluating feasibility
  • Designing ML architecture
  • Estimating effort and resources

Status: Future enhancement (not yet implemented)

Related Resources:


Real-Time Streaming Analytics Implementation Plan - Future Enhancement

  • Complete plan for implementing real-time note processing using PostgreSQL LISTEN/NOTIFY
  • Event-driven architecture for near-instantaneous analytics
  • Reduces latency from 15 minutes to seconds

Contents:

  • Architecture using PostgreSQL LISTEN/NOTIFY mechanism
  • Database trigger setup in Ingestion system
  • Streaming processor implementation (Python + Bash)
  • Micro-ETL for single-note processing
  • Batch processing and error handling
  • Performance considerations and scalability
  • Monitoring and observability
  • Migration strategy and testing approach
  • Cost-benefit analysis

Audience: System architects, database administrators, DevOps engineers, project managers

When to read:

  • Planning real-time analytics implementation
  • Understanding event-driven architecture
  • Evaluating LISTEN/NOTIFY approach
  • Designing streaming data pipelines
  • Estimating effort and resources

Status: Future enhancement (not yet implemented, LOW priority)

Key Features:

  • Native PostgreSQL solution (no external message queue)
  • Event-driven processing
  • Automatic reconnection and error handling
  • Batch processing for efficiency
  • Works alongside existing batch ETL

Current State:

  • Ingestion: Every 1 minute
  • ETL: Every 15 minutes
  • Latency: ~15 minutes maximum

Proposed State:

  • Streaming: Real-time (seconds)
  • Batch ETL: Continues as safety net
  • Latency: Seconds to minutes

External Note Classification Strategies - Research and Analysis

  • Analysis of external tools for note classification
  • Keyword-based classification strategies
  • Hashtag-based classification approaches
  • Integration opportunities with our ML system

Contents:

  • DE:Notes Map v2.5 analysis (keyword and hashtag-based classification)
  • How external strategies could enhance our ML system
  • Keyword lists for feature engineering
  • Hybrid classification approaches (rule-based + ML)
  • Recommendations for integration

Audience: ML engineers, data scientists, system architects

When to read:

  • Researching classification strategies
  • Enhancing ML feature engineering
  • Understanding keyword-based approaches
  • Planning hybrid classification systems

Note Categorization and Classification - Note Type System

  • Comprehensive guide to note classification system
  • Based on AngocA's diary article on note types
  • How analytics help categorize notes
  • SQL queries for identifying note types
  • Use cases for mappers, community leaders, and analysts

Contents:

  • Two main note categories (contribute vs don't contribute with change)
  • 18+ detailed note subtypes with examples
  • Available metrics for categorization
  • Classification SQL queries
  • Use cases for different user types
  • Related resources and articles

Audience: Mappers, community leaders, data analysts, note resolution campaign organizers

When to read:

  • Understanding note classification system
  • Planning note resolution campaigns
  • Analyzing note patterns
  • Identifying priority notes
  • Learning about note types and characteristics

Related Articles:


Query Performance Baselines - Performance Expectations

  • Expected query times for common operations
  • Performance optimization tips and strategies
  • When to use datamarts vs facts table
  • Troubleshooting slow queries

Contents:

  • 8 categories of common queries
  • Expected execution times for each query type
  • Performance optimization strategies
  • Monitoring and troubleshooting guide
  • Best practices for query performance

Audience: Developers, data analysts, system administrators

When to read:

  • Understanding query performance expectations
  • Optimizing dashboard queries
  • Troubleshooting slow queries
  • See also: Dashboard Implementation Guide for query examples

Architecture Diagrams - System Structure

  • C4 model architecture documentation (Level 1 and Level 2)
  • System context and container diagrams
  • Component interactions and data flows
  • Technology stack documentation
  • Deployment and security architecture

Contents:

  • C4 Level 1: System context (system and external entities)
  • C4 Level 2: Container diagram (high-level building blocks)
  • Detailed architecture with components
  • Technology stack (PostgreSQL, Bash, SQL)
  • Deployment architecture
  • Security architecture
  • Performance and scalability considerations

Audience: System architects, DevOps engineers, developers, technical leads

When to read:

  • Understanding overall system structure
  • Planning deployments
  • Designing new features
  • Troubleshooting architecture issues
  • Onboarding new developers

Deployment Diagram - Infrastructure and Operations

  • Deployment architecture (single and multi-server)
  • Operational schedules and cron configuration
  • Process dependencies and execution order
  • Infrastructure requirements
  • Monitoring, backup, and disaster recovery

Contents:

  • Deployment architecture diagrams
  • Production schedule (Gantt chart)
  • Cron configuration examples
  • Process dependency graphs
  • Infrastructure specifications
  • Deployment steps
  • Operational workflows
  • Monitoring and alerting
  • Backup and recovery procedures
  • Security considerations
  • Performance tuning

Audience: DevOps engineers, system administrators, SREs, deployment teams

When to read:

  • Planning production deployment
  • Setting up cron automation
  • Understanding operational dependencies
  • Configuring monitoring
  • Disaster recovery planning
  • Performance optimization

Cron Setup Guide - Automated Execution

  • Complete guide for setting up automated ETL execution
  • Cron configuration and scheduling
  • Monitoring and troubleshooting
  • Best practices for production

Contents:

  • Installation and configuration
  • Scheduling options
  • Lock file behavior
  • Log management
  • Monitoring scripts
  • Troubleshooting common issues
  • Best practices

Audience: System administrators, DevOps engineers

When to read:

  • Setting up automated ETL execution
  • Configuring cron jobs
  • Troubleshooting cron issues
  • See also: Deployment Diagram for complete deployment architecture

Entity-Relationship Diagram and Schema Overview

  • Complete star schema design
  • Dimension and fact table relationships
  • ETL flow diagrams (Mermaid)
  • Data model visualization
  • Table relationships and foreign keys

Contents:

  • Conceptual data model
  • Logical schema design
  • Physical implementation details
  • ETL data flow
  • Operational workflows

Audience: Database architects, data engineers, developers

When to read:

  • Understanding the data warehouse structure
  • Designing new features
  • Optimizing queries
  • Planning schema changes

Complete Data Dictionary for All Tables

  • Detailed column definitions
  • Data types and constraints
  • Business rules and logic
  • Sample data and examples
  • Relationships between tables

Contents:

  1. Fact Table:

    • dwh.facts - All columns with descriptions
  2. Dimension Tables:

    • dimension_users - User information
    • dimension_countries - Country data
    • dimension_regions - Geographic regions
    • dimension_continents - Continental groupings
    • dimension_days - Date dimension
    • dimension_time_of_week - Temporal dimension
    • dimension_applications - Application tracking
    • dimension_application_versions - Version history
    • dimension_hashtags - Hashtag catalog
    • dimension_timezones - Timezone information
    • dimension_seasons - Seasonal classifications
    • dimension_automation_level - Bot/script detection levels
    • dimension_experience_levels - User experience classification (newcomer to legend)
  3. Datamart Tables:

    • dwh.datamartCountries - Country analytics (77+ metrics)
    • dwh.datamartUsers - User analytics (78+ metrics)
    • dwh.datamartGlobal - Global statistics
  4. Control Tables:

    • dwh.properties - ETL metadata
    • dwh.contributor_types - User classifications

Audience: Analysts, report developers, data scientists

When to read:

  • Writing queries
  • Building reports
  • Understanding data lineage
  • Validating data quality

Advanced ETL Features and Capabilities

  • Enhanced ETL functionality
  • Performance optimizations
  • Recovery and monitoring
  • Advanced processing techniques

Contents:

  • Parallel processing by year
  • Incremental update strategies
  • Recovery and resume capabilities
  • Resource monitoring
  • Data validation and integrity checks
  • Performance tuning guidelines
  • Troubleshooting common issues

Audience: Data engineers, ETL developers, DevOps

When to read:

  • Setting up ETL processes
  • Troubleshooting ETL failures
  • Optimizing performance
  • Implementing recovery strategies

data warehouse Maintenance and Cleanup Guide

  • Cleanup script usage and safety guidelines
  • Maintenance workflows and best practices
  • Troubleshooting common issues
  • Emergency procedures

Contents:

  • When and how to use cleanup script
  • Safe vs destructive operations
  • Common maintenance workflows
  • Safety guidelines and best practices
  • Troubleshooting cleanup issues
  • Configuration and prerequisites

Audience: Database administrators, DevOps, developers

When to read:

  • Planning maintenance procedures
  • Troubleshooting data warehouse issues
  • Setting up development environments
  • Understanding cleanup operations

Comprehensive Troubleshooting Guide

  • Common problems and solutions
  • Diagnostic commands
  • Recovery procedures
  • Error code reference

Contents:

  • Quick diagnostic commands
  • ETL issues and solutions
  • Database issues and solutions
  • Datamart issues and solutions
  • Performance issues and solutions
  • Export and profile generation issues
  • Configuration and integration issues
  • Recovery procedures

Audience: All users, developers, system administrators

When to read:

  • When encountering errors or problems
  • Before asking for help
  • Setting up new environments
  • Troubleshooting performance issues

See also: bin/README.md for script-specific troubleshooting


Testing Documentation

For comprehensive testing documentation, see tests/README.md:

Complete Testing Guide:

  • Test suite descriptions (Quality Tests, DWH Tests, All Tests)
  • How to run tests locally
  • Test configuration and setup
  • Database requirements
  • Troubleshooting common issues
  • Writing new tests
  • CI/CD integration
  • Git hooks for testing

Test Suites:

  • Quality Tests: Fast validation without database (shellcheck, shfmt, SQL syntax)
  • DWH Tests: Database-dependent tests (ETL, datamarts, SQL functions)
  • Integration Tests: End-to-end workflow validation

Test Files:

  • Unit tests: tests/unit/bash/*.bats and tests/unit/sql/*.sql
  • Integration tests: tests/integration/*.bats

Audience: Developers, QA engineers, contributors

When to read:

  • Setting up test environment
  • Running tests locally
  • Writing new tests
  • Debugging test failures
  • Understanding test coverage

Hybrid Strategy: Database Separation

  • Implemented strategy to separate Ingestion and Analytics databases
  • Local table copy for initial load (avoids millions of cross-database queries)
  • Foreign Data Wrappers (FDW) for incremental execution

Contents:

  • Configuration and usage
  • Implementation scripts
  • Troubleshooting
  • Technical details

Audience: Developers, database administrators

When to read:

  • Configuring database separation
  • Understanding how the hybrid strategy works
  • Troubleshooting table copy or FDW issues

Hybrid ETL Execution Guide - Complete Pipeline Testing

  • Complete guide for running hybrid ETL execution scripts
  • End-to-end pipeline testing (Ingestion + ETL)
  • Hybrid mode configuration (real DB, mocked downloads)
  • Step-by-step execution control
  • Expected behavior in each iteration

Contents:

  • Overview of hybrid execution scripts
  • Architecture and dependencies
  • Hybrid mode configuration (real PostgreSQL + mocked downloads)
  • Complete execution flow (4 iterations)
  • Expected behavior for each execution:
    • Execution #1: Planet/Base Load
    • Execution #2: API Sequential (5 notes)
    • Execution #3: API Parallel (20 notes)
    • Execution #4: API Empty (0 notes)
  • Cleanup and error handling
  • Troubleshooting common issues
  • Integration with CI/CD

Scripts:

  • run_processAPINotes_with_etl.sh - Automatic execution mode
  • run_processAPINotes_with_etl_controlled.sh - Step-by-step control mode

Audience: Developers, QA engineers, system integrators

When to read:

  • Testing complete data pipeline (Ingestion → DWH)
  • Understanding hybrid mode execution
  • Debugging end-to-end workflows
  • Setting up integration tests
  • Verifying ETL after ingestion updates

CI/CD Documentation

GitHub Push Setup for Production

Configuration guide for automated git pushes to GitHub from production servers, particularly for non-interactive users (e.g., notes user in cron jobs).

Contents:

  • SSH key setup (recommended)
  • Personal Access Token configuration
  • Deploy key setup
  • Troubleshooting guide
  • Security best practices
  • Production checklist

Audience: System administrators, DevOps engineers

When to read:

  • Setting up automated exports to GitHub
  • Configuring git credentials for production
  • Troubleshooting push failures
  • Securing automated git operations

Complete CI/CD Setup and Configuration Guide

  • GitHub Actions workflows
  • Automated testing and validation
  • Deployment strategies
  • Git hooks and quality gates

Contents:

  1. GitHub Actions Workflows:

    • Quality checks workflow
    • Test execution workflow
    • Dependency checking
    • Security scanning
  2. Git Hooks:

    • Pre-commit validation
    • Pre-push testing
    • Commit message linting
    • Installation and configuration
  3. Quality Gates:

    • Code quality thresholds
    • Test coverage requirements
    • Security vulnerability checks
    • Performance benchmarks
  4. Deployment:

    • Deployment strategies
    • Environment management
    • Rollback procedures
    • Production readiness checks

Audience: DevOps engineers, release managers, developers

When to read:

  • Setting up CI/CD pipelines
  • Configuring quality gates
  • Troubleshooting workflow failures
  • Planning deployments

Quick Start

New to the project? Start here:

  1. Rationale.md (30 min) - Understand why this project exists
  2. Main README (20 min) - Project overview and quick start
  3. DWH_Star_Schema_ERD.md (30 min) - Understand the data model

Total time: ~1.5 hours for a complete overview.

For detailed navigation paths by role, see Recommended Reading Paths by Role below.

Recommended Reading Paths by Role

For New Users (~2 hours total)

Step 1: Project Context (50 min)

  • Rationale.md (30 min) - Project purpose and motivation
    • Why this project exists
    • Problem statement
    • Historical context
  • Main README (20 min) - Project overview and quick start
    • Features and capabilities
    • Quick start guide
    • Basic workflows

Step 2: System Overview (60 min)

  • Data_Flow_Diagrams.md (20 min) - System data flow
    • Context diagram
    • Process decomposition
    • Data flow overview
  • DWH_Star_Schema_ERD.md (30 min) - data warehouse structure
    • Star schema design
    • Table relationships
    • ETL data flow
  • bin/README.md (10 min) - Scripts overview
    • Main entry points
    • Basic usage examples

Step 3: Getting Started (25 min)

For Developers (~3 hours total)

Step 1: Foundation (75 min)

Step 2: Implementation Details (60 min)

Step 3: Development Workflow (45 min)

Step 4: Deep Dive (as needed)

For Data Analysts (~2 hours total)

Step 1: Data Model (60 min)

Step 2: Data Access (45 min)

Step 3: Advanced Topics (45 min)

For DevOps/SRE (~2.5 hours total)

Step 1: Deployment (45 min)

Step 2: Operations (60 min)

Step 3: Monitoring and Troubleshooting (60 min)

For System Administrators (~2 hours total)

Step 1: System Overview (45 min)

Step 2: Operations (60 min)

Step 3: Configuration (15 min)

Quick Reference

Essential Documents

Script Documentation

Technical Reference

Documentation Standards

Markdown Style

All documentation follows these standards:

  • Headers: Use ATX-style headers (#, ##, ###)
  • Code blocks: Use fenced code blocks with language specification
  • Links: Use reference-style links for readability
  • Lists: Use - for unordered lists, numbers for ordered lists
  • Emphasis: Use **bold** for important terms, *italic* for emphasis
  • Tables: Use GitHub-flavored markdown tables
  • Diagrams: Use Mermaid for diagrams when possible

Content Structure

Standard document structure:

  1. Title and Overview
  2. Table of Contents (for long documents)
  3. Main Content (organized by topic)
  4. Examples (practical demonstrations)
  5. Troubleshooting (common issues)
  6. References (related documents)

Code Examples

All code examples should:

  • Be tested and verified
  • Include comments explaining key points
  • Show realistic use cases
  • Follow project coding standards

Diagrams

  • Use Mermaid for architecture and flow diagrams
  • Use ASCII art for simple diagrams
  • Use external tools only when necessary
  • Include diagram source in comments

Maintenance

Updating Documentation

When updating documentation:

  1. Keep it accurate: Update docs when code changes
  2. Be clear: Write for the intended audience
  3. Add examples: Show, don't just tell
  4. Test examples: Verify all code examples work
  5. Update cross-references: Fix broken links
  6. Version appropriately: Note what version applies

Documentation Review

Documentation should be reviewed:

  • When features are added or changed
  • During code review process
  • Quarterly for accuracy
  • After major releases

Documentation Checklist

Before finalizing documentation:

  • Spelling and grammar checked
  • All code examples tested
  • Links verified
  • Diagrams accurate and current
  • Table of contents updated
  • Cross-references correct
  • Version information included
  • Audience appropriate

Contributing to Documentation

How to Contribute

  1. Identify gaps: Find missing or incomplete documentation
  2. Create/update: Write or update documentation
  3. Test: Verify all examples and instructions
  4. Submit PR: Create pull request with changes
  5. Address feedback: Respond to review comments

Documentation Issues

Report documentation issues:

  • Incorrect information
  • Outdated examples
  • Broken links
  • Confusing explanations
  • Missing topics

Create an issue with:

  • Document name and section
  • What's wrong
  • Suggested correction
  • Your use case

Tools and Utilities

Recommended Tools

Markdown Editors:

  • VSCode with Markdown extensions
  • Typora (WYSIWYG)
  • MacDown (macOS)
  • ReText (Linux)

Diagram Tools:

  • Mermaid Live Editor
  • Draw.io
  • PlantUML

Documentation Linters:

  • markdownlint
  • write-good
  • proselint

Validation

Validate documentation:

# Check markdown syntax
markdownlint docs/*.md

# Check spelling
aspell check docs/*.md

# Validate links
markdown-link-check docs/*.md

# Check code blocks
# Extract and test all code examples

Additional Resources

Related Documentation

External Resources

Support

For documentation questions:

  1. Check if answer is in existing docs
  2. Search closed issues for similar questions
  3. Create new issue with "documentation" label
  4. Provide context about what you're trying to do

Document History

This documentation structure was established: 2025-10-14

Major Updates:

  • 2025-12-14: Added Dashboard Implementation Guide, Use Cases and Personas, Performance Baselines
  • 2025-12-14: Added Performance Monitoring system documentation
  • 2025-12-14: Updated metric counts (77+ for countries, 78+ for users)
  • 2025-12-14: Updated test counts (197+ tests)
  • 2025-10-14: Initial comprehensive documentation structure
  • 2025-10-13: Added CI/CD Guide
  • 2025-10-12: Enhanced testing documentation
  • 2025-08-18: Updated ETL features documentation
  • 2025-08-08: Initial star schema documentation

Feedback

We value your feedback on documentation:

  • What's missing?
  • What's confusing?
  • What examples would help?
  • How can we improve?

Please create an issue or contact the maintainers with suggestions.