| entity | |||||||||
| physical entity | |||||||||
| thing | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
| external body part | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
| abstraction | |||||||||
<tbody> </tbody> | |||||||||
<tbody> </tbody> | |||||||||
<tbody>
</tbody>
I tried to import it but it sucked, as it didn't have any structure! just the thing copied and pasted!
This is like a tree with nodes but it's in excel, I don't like it in excel
Entity is the parent of physical entity, etc, they have ascendants, children, siblings, etc
My plan is to make it in access now: maybe with just 1 table, is it good or do you suggest many tables?
I want it to be designed in such a way that I be able to consult many things:
1)given a word, consult the definition, the last ascendant, the first ascendant, the number of ascendants, images of the word (hyperlinks)
2)see the whole ascendency or hierarchy of a in a numbered way, like 1.1, 1.2, 1.2.1, 1.2.1.1, 1.2.1.2, etc and make it Automatic. How?
3)given the hierarchy for example 1.2.1.3, see the children of 1.2.1.3 (actually when i say 1.2.1.3 it is entity.abstraction.psychological_feature.event, so the children of event)
Any suggestions about the design of the database? (this will be my first database in my life but I want it to be good)
I come here because I tried to do it in onenote, but onenote sucked because of memory problems because it has thousands of elements
I also tried to do it in freemind (a program for mind maps) but it sucked because I want to see a word or an ascendency at a time mostly, and access looks like a marvelous option...
<tbody> </tbody> |
<tbody>
</tbody>
