From: Peter L. <pet...@te...> - 2010-09-09 07:38:04
|
Den Thursday 09 September 2010 09.09.34 skrev Benny Malengier: > 2010/9/9 Peter Landgren <pet...@te...> > > > Den Wednesday 08 September 2010 22.29.05 skrev Benny Malengier: > > > I tweaked the design somewhat. > > > > > > > > > > > > I removed father/mother side, scanning parents makes that clear. > > > > > > I made patronymic/matronymic a derivation type, indicating how the name > > > > was > > > > > derived. Default type would be Inherited. Any other predefined types > > > > > > needed? Eg: Taken, Given, ??? > > > > How will you handle the case with people having a "son-name" (sonnamn in > > Swedish) > > > > changing it to a non-son-name. That was very common during the 1800's and > > you could do it by yourself. Later we got a name law that organized all > > this. The change took place on a certain date. > > > > The new name is called a "taken" name (taget in Swedish) as opposed to > > "inherited" from your parents either as a patronymic or as a family name. > > As an example, my great great grandfather changed from Olofsson to > > Landgren in 1830. The church record from that year says "calling himself > > Landgren"- > > > > /Peter > > Your great great grandfather has two names, one primary and one > alternative. > > His primary name would have surname=Landgren, type='taget' > His alternative name would have surname = Olofsson, type='patronymic' > > So no compound surname in this case. Only how we store patronymic changes. > The notes and sources of the name must be used to document this, surnames > will have no notes or sources. > > Benny OK. I would like to have the possibility to print (or display) the name as: Landgren (Olofsson before 1830) which means that a date must be coupled to the name change. /Peter > > > Question: are there people using suffix in their language for > > > something > > > > > > else than Jr., III, ... (apart from the use to store compound surname > > > > > > which would no longer be needed? I need to know if it is needed to have > > > a > > > > > > suffix for every surname of a compound surname, or if it is only needed > > > > > > once for the complete name. Something like Jr., III, is best stored > > > > > > globally. > > > > > > > > > > > > Benny > > > > > > > > > > > > 2010/9/8 Benny Malengier <ben...@gm...> > > > > > > > I finished a first design for GEPS 021: Additional Name > > > > > > > > Fields< > > > > http://www.gramps-project.org/wiki/index.php?title=GEPS_021:_Addi > > > > > > tional_Name_Fields> > > > > > > > > > > > > > > > > This is obviously a _core_ part of Gramps, so changing it should be > > > > done > > > > > > with consensus. > > > > > > > > So please go over the design proposal, and test with your use-cases. > > > > > > > > > > > > > > > > Questions: > > > > > > > > 1/ Do we need family nickname, father side, mother side in the > > > > design. > > > > > > > > Less fields reduces complexith, however, we don't change database/xml > > > > > > > > often, so let's do now what is needed. > > > > > > > > > > > > > > > > 2/ This is about how we store names. The UI side is not worked out > > > > apart > > > > > > from generic concepts (it should be as fast as today even with the > > > > > > > > functionality for compound surnames). Important point now is: can > > > > this > > > > > > > > datastructure (see xml schema) hold the complexity as needed? > > > > > > > > > > > > > > > > Looking forward to your feedback. > > > > > > > > > > > > > > > > Benny |