dingir
asked on
Follow up, table design dictionary
This question is based on the result of https://www.experts-exchange.com/questions/24125835/Table-design.html, where I got an follow up. A dictionary with many words, needs of course to be grouped.
This dictionary needs an extra level. A grouping level.
* View available Language
* View available groups (Which also needs to exist on all languages), 6 languages.
* View all words based on the selected language and group
Thank's in advanced,
This dictionary needs an extra level. A grouping level.
* View available Language
* View available groups (Which also needs to exist on all languages), 6 languages.
* View all words based on the selected language and group
Thank's in advanced,
ASKER
yeah I see that my solution was going over my head when I came to the CMS part of it. too bad with my available time. I need to start over with an simplier version and forget the language part. Just a "group" "words" and then the translation...
Yeah, think so... You could still use the above, just need to decide if you are making it mandatory to have same Alias's at the group before you can have them at the word level...
ASKER
Thank's. I'm sure it works. I'm now finished with my solution and are happy with it (except that I have a coming nightmare importing the excel data files where the translations are stored in fields). I will however use ur design later. My solution is now (in short) something like this,
table_language
- lang_id
- lang_name
table_groups
- group_uid
- group_name
- group_lang_id
- group_id
table_words
- word_id
- word_lang_id
- word_group_id
- word_text
Which let the visitor to select a language, select a group and then gets a list of words related to that group and language. When clicking a word, the user gots a translation for that word on all available language in the dictionary_language. The word and menus is always showed up with the correct choosed local language.
For the CMS part the Add Group query creates the new group for all available languages. When adding a word, that word are being created for that group in every available language. I can also create and delete a new/existing language with just a click. When the CMS-user clicked a group_name, the user gots a editable gridview with the translation to all available languages. The same idea is applied when clicking a word.
Am I still doing something uneccesary complicated here?
table_language
- lang_id
- lang_name
table_groups
- group_uid
- group_name
- group_lang_id
- group_id
table_words
- word_id
- word_lang_id
- word_group_id
- word_text
Which let the visitor to select a language, select a group and then gets a list of words related to that group and language. When clicking a word, the user gots a translation for that word on all available language in the dictionary_language. The word and menus is always showed up with the correct choosed local language.
For the CMS part the Add Group query creates the new group for all available languages. When adding a word, that word are being created for that group in every available language. I can also create and delete a new/existing language with just a click. When the CMS-user clicked a group_name, the user gots a editable gridview with the translation to all available languages. The same idea is applied when clicking a word.
Am I still doing something uneccesary complicated here?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Open in new window