You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new feature that allows user's to add their own custom vocabulary.
Current Model
When a user signs up, a row in the User table is created, paired with a row in the Profile table. Profile holds everything you'd expect that isn't in User (i.e. WK API key, about information, user settings, etc.).
All of the WaniKani vocabulary words sit one-to-one in the Vocabulary table. Each row in the Vocabulary table has one or more entries in the Reading table. Vocabulary holds the word's meaning in English, whilst each Reading holds a reading in Japanese, including
character, the reading in Kanji/Hiragana/Katakana;
kana, the reading in Hiragana; and
level, the level that it corresponds to in WK.
Each entry in the UserSpecific table corresponds to an actual word that is being reviewed by a user. That is, it is basically the user's own record of each row in Vocabulary. This tracks everything about the user's word, such as when it's next up for review.
Custom Vocabulary Model
The data model for custom user vocabulary should look similar to the above. Specifically, the review information should be distinct from the actual vocabulary word, as this will facilitate potentially later adding functionality for reviewing words KW style.
The text was updated successfully, but these errors were encountered:
Create a new feature that allows user's to add their own custom vocabulary.
Current Model
When a user signs up, a row in the
User
table is created, paired with a row in theProfile
table.Profile
holds everything you'd expect that isn't inUser
(i.e. WK API key, about information, user settings, etc.).All of the WaniKani vocabulary words sit one-to-one in the
Vocabulary
table. Each row in theVocabulary
table has one or more entries in theReading
table.Vocabulary
holds the word's meaning in English, whilst eachReading
holds a reading in Japanese, includingcharacter
, the reading in Kanji/Hiragana/Katakana;kana
, the reading in Hiragana; andlevel
, the level that it corresponds to in WK.Each entry in the
UserSpecific
table corresponds to an actual word that is being reviewed by a user. That is, it is basically the user's own record of each row inVocabulary
. This tracks everything about the user's word, such as when it's next up for review.Custom Vocabulary Model
The data model for custom user vocabulary should look similar to the above. Specifically, the review information should be distinct from the actual vocabulary word, as this will facilitate potentially later adding functionality for reviewing words KW style.
The text was updated successfully, but these errors were encountered: