How yoru0/maidata works
maidata is an early-WIP terminal tool intended to curate a personal maimai chart library. The current executable starts a Bubble Tea menu, but the README explicitly says its batch operations are not wired up and the chart parser is empty; the processing stages below therefore describe the documented target workflow, not implemented calls. Drive and zetaraku clients exist as separate integrations, but sampled source shows no connection from the menu to them.
Main entry points: model.go TUI menu · internal Archive extraction · client.go Zetaraku client · main.go CLI entry
Components 15
Chart curation workflow
- Pack download
internal - Archive extraction
internal - Chart cleanup
internal - Chart validation
internal - Chart browsing
internal
External data
- Drive client
internal/drive/client.go - Zetaraku client
internal/zetaraku/client.go - Song constants
internal/zetaraku/db.go
Configuration and chart data
- Configuration
internal/config/config.go - Level types
internal/chart/level.go
Other components
- Library curator
- Google Drive
- Zetaraku data
Connections 13
- Library curator → CLI entry: starts
cmd/maidata/main.go - CLI entry → TUI menu: runs
cmd/maidata/main.go - TUI menu → Pack download: lists choice
internal/tui/model.go - TUI menu → Archive extraction: lists choice
internal/tui/model.go - TUI menu → Chart cleanup: lists choices
internal/tui/model.go - TUI menu → Chart validation: lists choice
internal/tui/model.go - TUI menu → Chart browsing: lists choice
internal/tui/model.go - Pack download → Archive extraction: followed by
README.md - Archive extraction → Chart cleanup: followed by
README.md - Drive client → Google Drive: lists and downloads
internal/drive/client.go - Zetaraku client → Zetaraku data: fetches data
internal/zetaraku/client.go - Zetaraku client → Song constants: builds database
internal/zetaraku/client.go - Song constants → Level types: matches levels
internal/zetaraku/db.go