transliminal
New member
- Local time
- Yesterday, 22:35
- Joined
- Sep 27, 2019
- Messages
- 4
Hi there,
I'm a newb currently trying to design a bi-lingual dictionary/glossary database for eventual use in an iOS/Android app.
I'm inexperienced, and could use some help doing this right, from the ground up.
As follows is a description of my situation:
I have a list of thousands of words in two different languages, English and Arabic. (These are currently stored in two different Excel sheets, one in each language. Each word has its own unique ID [GUID] already assinged).
Each word in English list corresponds to one or more words in the Arabic list, and vice versa.
(Eg., the English word "tomorrow", translates both to "bukra" and "ghadaan" in Arabic. "Ghadaan" in Arabic translates to both "tomorrow" and "next day" in English... etc., etc.)
So, it's a two-way, one-to-many sort of relationship between words (records), i guess you could say.
As i migrate this rudimentary word list from Excel to Access, i also want to add numerous data about each word (record), and generally make the whole database efficient, compact, and readily searchable and updateable.
***
To give you an example of some of the complexity i'll need to account for, in addition to the core bi-directional, one-to-many relationship between English and Arabic words, i also need to store:
(1) each word's "part of speech" (e.g., verb, noun, adjective, etc.); and
(2) ... depending on what part of speech a given word has, i want to store further information about that word (e.g., *if* it's a verb, then i want to store all its conjugations... but *if* it's a noun, then there are no conjugations, but there are plurals, and (in Arabic) masculine, feminine, forms, etc.)
At this stage, i'm curious how you, as database experts, would design this database.
What basic principles should i keep in mind given my particular needs? How do i express the relationships most effectively?
What should i use as my primary vs. foreign keys? etc.
Should i have multiple tables for the different kinds of information i want to store about each word (record)? Or should i just store everything in one gigantic table per language?
... these are the kinds of questions (amongst others) i'm currently contemplating.
Thank you in advance for any help you can offer, be it in terms of general guiding principles, or more specific suggestions.
-jordan (transliminal)
I'm a newb currently trying to design a bi-lingual dictionary/glossary database for eventual use in an iOS/Android app.
I'm inexperienced, and could use some help doing this right, from the ground up.
As follows is a description of my situation:
I have a list of thousands of words in two different languages, English and Arabic. (These are currently stored in two different Excel sheets, one in each language. Each word has its own unique ID [GUID] already assinged).
Each word in English list corresponds to one or more words in the Arabic list, and vice versa.
(Eg., the English word "tomorrow", translates both to "bukra" and "ghadaan" in Arabic. "Ghadaan" in Arabic translates to both "tomorrow" and "next day" in English... etc., etc.)
So, it's a two-way, one-to-many sort of relationship between words (records), i guess you could say.
As i migrate this rudimentary word list from Excel to Access, i also want to add numerous data about each word (record), and generally make the whole database efficient, compact, and readily searchable and updateable.
***
To give you an example of some of the complexity i'll need to account for, in addition to the core bi-directional, one-to-many relationship between English and Arabic words, i also need to store:
(1) each word's "part of speech" (e.g., verb, noun, adjective, etc.); and
(2) ... depending on what part of speech a given word has, i want to store further information about that word (e.g., *if* it's a verb, then i want to store all its conjugations... but *if* it's a noun, then there are no conjugations, but there are plurals, and (in Arabic) masculine, feminine, forms, etc.)
At this stage, i'm curious how you, as database experts, would design this database.
What basic principles should i keep in mind given my particular needs? How do i express the relationships most effectively?
What should i use as my primary vs. foreign keys? etc.
Should i have multiple tables for the different kinds of information i want to store about each word (record)? Or should i just store everything in one gigantic table per language?
... these are the kinds of questions (amongst others) i'm currently contemplating.
Thank you in advance for any help you can offer, be it in terms of general guiding principles, or more specific suggestions.
-jordan (transliminal)