data_management

Synchronize lottery data via incremental updates, issue normalization, and deduplication.

11|4|Updated Feb 2, 2025
One-click install
npx skills add https://github.com/konglr/Lottery --skill data-management-konglr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data_management
Source: https://github.com/konglr/Lottery/tree/main/skills/data_management
Command: npx skills add https://github.com/konglr/Lottery --skill data-management-konglr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates inconsistent or incomplete lottery datasets by automating incremental updates, normalizing issue formats, and transforming raw API responses into standardized, analysis-ready features.

Core Features & Use Cases

  • Incremental + coverage synchronization: Retrieves the most recent records (e.g., last 100), re-captures issues using >= logic, and deduplicates by issue to preserve the latest winnerDetails.
  • Cross-candy issue normalization: Normalizes varying issue formats before comparing local_latest to remote data to prevent missed updates.
  • Standardized preprocessing & feature engineering: Maps award tiers per lottery type, cleans columns via allowlists, and computes core statistics such as sum, span, odd/even, big/small, 连号/跳号, AC value, heavy/repeat counts, and interval-region distributions.

Quick Start

Run python request_data_update.py to sync the latest lottery data and ensure winnerDetails integrity.

Frequently Asked Questions about data_management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize inconsistent lottery issue formats during data cleaning?

Lottery data cleaning normalizes varying issue formats before comparing local_latest to remote data to prevent missed updates. This cross-candy issue normalization ensures consistent datasets and preserves the latest winnerDetails during incremental synchronization.

What is the best way to automate incremental sync for lottery data?

Automating incremental sync for lottery data retrieves the most recent records, re-captures issues using >= logic, and deduplicates by issue. Running python request_data_update.py executes this workflow to retain complete winnerDetails across multi-lottery scenarios.

How do I perform feature engineering on SSQ and DLT lottery datasets?

Feature engineering on SSQ and DLT datasets maps award tiers per lottery type, cleans columns via allowlists, and computes core statistics like sum, span, odd/even, big/small, AC value, and interval-region distributions for downstream model training.

Does this data preprocessing approach handle multiple lottery types like PL3, PL5, and KL8?

This data preprocessing approach handles multi-lottery scenarios including PL3, PL5, and KL8 by applying tier-specific mappings and allowlist-based column retention to transform raw JSON API responses into consistent, analysis-ready datasets.

Why are my lottery API responses missing complete winnerDetails after updates?

Missing winnerDetails after updates often occurs when deduplication lacks >=-based coverage logic. Re-capturing issues with >= logic and deduplicating by issue ensures the preservation of the latest complete winnerDetails.