Skip to content

fix(schaledb): use JP student source - #54

Closed
HU-Lee wants to merge 1 commit into
mainfrom
fix/schaledb-jp-source-v2
Closed

HU-Lee wants to merge 1 commit into
mainfrom
fix/schaledb-jp-source-v2

Conversation

@HU-Lee

@HU-Lee HU-Lee commented Aug 5, 2026

Copy link
Copy Markdown
Member

Summary

  • Use the Japanese SchaleDB dataset as the authoritative student roster and structure.
  • Populate KO, JP, EN, and ZH student, skill, weapon, and gear names from each exact locale dataset.
  • Reject incomplete or inconsistent locale sets before writing data; no locale fallback is used.
  • Clarify the batch CLI role in the README.

Evidence

  • Current upstream dry run: 270 students in every locale, zero ID differences, zero missing localized names across students, skills, selectable EX skills, weapons, and gear.
  • Static checks, tests, and build: PASS.

Upstream status

Student 10148 is not present in any of the four current SchaleDB locale datasets yet. The batch can ingest it once SchaleDB publishes the record.

@HU-Lee HU-Lee self-assigned this Aug 5, 2026
@HU-Lee

HU-Lee commented Aug 5, 2026

Copy link
Copy Markdown
Member Author

After additional analysis, it's totally same.
Student 10148 is not present so I opened this PR, but this student (Iroha swimsuit) is updated 08/05 so not updated in SchaleDB.

Close the issue because this PR doesn't change anything.

@HU-Lee HU-Lee closed this Aug 5, 2026
@HU-Lee
HU-Lee deleted the fix/schaledb-jp-source-v2 branch August 5, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant