List branches by surname
Brought to you by:
canajun2eh,
yalnifj
Geneweb software has a nice feature : list all branches for a surname.
Useful to find duplicates or unlinked persons.
Here is a sample :
http://roglo.eu/roglo?lang=en;m=N;v=kennedy
I have started working on this and will commit files within one week.
NB : geneweb is used on geneanet
http://www.geneanet.org/
Christophe
Isn't this the same, or at least similar, to the 'Roots' option in Individual Lists?
There is also this "Unattached Individuals" report available in Patches:
https://sourceforge.net/tracker/index.php?func=detail&aid=1977245&group_id=55456&atid=477081
@kiwi_pgv :
this is something much better than "roots" filter
showing full hierarchy of people sharing the same surname.
Added to SVN :
branches.php
Now that I see it "in action" on my own data it makes more sense to me. I think your version looks better than the example link you gave too.
I wonder if it would help understanding/reading, especially when scrolling a long way down the screen, if you used something like the d'Aboville numbering system
1
2
3
3.1
3.2
3.2.2
etc?
Have you thought about where in the menu structure it belongs? I would guess "Lists" perhaps?
Christophe,
Interesting list.
1. If I search on an English page for Hebrew name אמתי or on the Hebrew page for Amity, I should see the names of both spouses in the same language if the second spouse has a name in the viewed language. Same issue exists for other special types of letters (Greek, Cyrilic. Chenese, Arabic etc.).
2. As you know, we need to translate the text of the Random button.
3. Should we also include different spellings of the surnames, for instance by using the DM soundex?
My husband's cousins use the name Amitay and we use Amity …
My mother-in-law was called Sztejn in Lithuania and later Shtein or Stein.
3. In the Jewish Genealogy conference 2 years ago John and I were asked to add to PGV a list where we would highlight certain given-names (or given-name equivalents) in different generations of families. The requesters suggested to show this in a family-tree where the ancestor is at the top. I believe that your presentation would as well meet their requirement.
Meliza
@Meliza :
Your 3 points should be fixed in the latest SVN.
@kiwi_pgv :
My vote for "Lists" menu
Not sure about adding level to numbering. What do others think ?
Hi Christophe,
COngratulations for this feature. It is for me a great idea.
I had myself developed a similar list (as kiwi_phv say, it is under Lists), and you can see it at: http://genea.jaubart.com/pgv/module.php?mod=perso_tools&pgvaction=patronymiclineage&ged=SauvGEDCOMAncest.GED
It is however more intrusive in terms of code than your version.
I report a bug:
When I am not connected, I have an error for couples where the nameholder is dead and the spouse is not. For instance:
1.Roger ROUSSET 1923-1982 (Age 59)
ERROR 8: Undefined offset: 1
0 Error occurred on line 118 of file branches.php in function print_fams
1 called from line 127 of file branches.php in function print_fams
2 called from line 127 of file branches.php in function print_fams
3 called from line 127 of file branches.php in function print_fams
4 called from line 127 of file branches.php in function print_fams
5 called from line 127 of file branches.php in function print_fams
6 called from line 70 of file branches.php
Notice: Undefined offset: 1 in Z:\www\htdocs\phpGedViewSVN\branches.php on line 118
Détails privés
.........
Here Roger Rousset is dead but his wife is not.
If I connect, I do not have any problem. I think this is just a problem of privacy.
Regards, Cordialement,
Jonathan
Hi Jonathan
thanks for your comments. Bug has been fixed.
I have visited your PGV website : design is really nice !
I can see that you have developped some very interesting modules (pedigree_map, stat_sosa, ...).
Would you mind sharing them with PGV community ?
Very easy : just upload your files to Patches tracker :
https://sourceforge.net/tracker/?group_id=55456&atid=477081
Thanks
Christophe
Christophe, My "Pedigree map" experiment has been in Patches since January 2008.
https://sourceforge.net/tracker/index.php?func=detail&aid=1863843&group_id=55456&atid=477081
I can't remember whether that version still works in latest PGV though. It has needed updating occasionally to reflect other changes in PGV.
Christophe
* I do not yet see Different spellings of the surname in one report. How should I activate this feature?
* On the RTL page the sequence of the shown data is not correct, when we view a LTR name.
The icons, the gender icon, the – of live people and the marriage year are in odd places. Also the () for instance of unknown names are not printed as expected.
* Should we use an icon instead of the x for marriages?
Meliza
Regarding Meliza's question about different spellings. It does appear the code uses a single spelling. I though at first this was a 'rtl' language type issue (a silly assumption on my part I realise), but have just noticed it affects all of us. I have a key line in my family that has changed its spelling three times. This file only displays one of them, and the line appears to stop, when in fact it just changed its spelling.
The version that Jonathan has seems to use different logic (presumably following relationships rather than just the names?) as it displays name variations. Perhaps the two of you could combine your work to come up with a single solution? I can certainly see benefits in both approaches.
(I also support Meliza's recommendation for something instead of 'x' for "married'.)
Christophe,
I also support recommendation for something image or abbreviation instead of 'x' for married.
The second issue:
In Poland we have two types of names.
The first is simillar to english names. After the marriage men and women
are the same name.
The second is names ending on -ski, -cki, -dzki. After the marriage
women's names are ending on -ska, -cka, -dzka.
In addition, the daughter's name of such couples are ending on -ska,
-cka, -dzka.
Sons have the same name like father.
see: https://sourceforge.net/tracker/?func=detail&aid=2319821&group_id=55456&atid=477082
It would be great if the branches list work correctly with such surnames.
Added soundex search to fix spelling changes.
Added SOSA numbering with relationship link to PGV_USER_ROOT_ID.
'x' for 'married' replaced by 'rings' icon from :
http://upload.wikimedia.org/wikipedia/commons/d/d8/Marriage_symbol_in_genealogy.gif
Nice changes, but
1. I no longer see any data when I search for a Hebrew name with or without using Soundex search on English or on Hebrew pages.
2. When I search for the oldest family surname spelling using Soundex, I see all the different spellings. (sample Sztejn)
When I search for a newer surname spelling, I do not see the ancestors with the older spelling. (sample Stein or Shtein).
Is this as intended?
Meliza
Sorry Christophe, latest changes give me errors if not logged in:
ERROR 8: Undefined index: user_ancestors
0 Error occurred on line 121 of file branches.php in function print_fams
1 called from line 86 of file branches.php
Of course, this could be something I did wrong, so if you can suggest what file(s) I might have missed...
@kiwi_pgv : error fixed
@meliza : hebrew search should now work as expected
Not sure how to deal with different spellings. Soundex search is not enough (in my tree I can find a branch GIRAUD or GIRAULT and soundex are different...). Even metaphone php function is not enough.
@wooc : latest version should work better with -ski -ska etc...
Christophe,
Shouldn't we include the Polish -ski -ska etc... and similar Russian, Islandic etc. text rules in the regular and Soundex searches?
The DM Soundex rules do not work well for instance for French spellings of letters that are 'silent'. Can you suggest how to improve the dmsounds_UTF8.php file without getting too many wrong positive hits in other languages?
The brances.php list should return the main name if it is equal to the searched name and a name in the same type of letters as the searched name, if such a name exists. On my site I see now a lot of Hebrew names when I search for a Latin name. (All my site individuals are defined with Latin names). This happens even when the Soundex boxes are not checked.
When I search for instance for the name O'Keefe (contains a quote ') or for other names with quotes, I get error
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'KEEFE' OR n_surname='O'KEEFE' OR n_soundex_surn_dm="'057000'") ORDER BY n_sort' at line 1' in /home/meliza/public_html/future/phpGedViewSVN/includes/classes/class_pgv_db.php:858 Stack trace: #0 /home/meliza/public_html/future/phpGedViewSVN/includes/classes/class_pgv_db.php(858): PDOStatement->execute() #1 [internal function]: PGV_DBStatement->__call(Array, Array) #2 /home/meliza/public_html/future/phpGedViewSVN/branches.php(202): PGV_DBStatement->execute('execute', Array) #3 /home/meliza/public_html/future/phpGedViewSVN/branches.php(85): indis_array() #4 {main} thrown in /home/meliza/public_html/future/phpGedViewSVN/includes/classes/class_pgv_db.php on line 858
When a searched name does not exist in the DB, I get the following error
ERROR 8: Undefined index: rootid
0 Error occurred on line 97 of file branches.php
Notice: Undefined index: rootid in /home/meliza/public_html/future/phpGedViewSVN/branches.php on line 97
The development user gets the error after 28 hits when he searches for name Wardi in my big file.
For a name with a double quote only the letters till the " are shown in the search field.
When the development user searches for ורדי on the big file he sees in the 2nd hit the Sosa and Generations as [2 2] and [3 2] instead of the expected [2]2 and [3]2. I have seen this format only when a spouse is alive and the reported name is a Hebrew one.
The () for instance of unknown given names is not printed correctly for RTL names on the LTR pages or for LTR names on RTL pages.
LTR names on RTL pages are not yet printed correctly.
Perhaps we can work on this offline.
Meliza
Christophe,
Thank, the Polish -ski & -ska names works fine
@wooc : soundex for -ski & -ska are equals so it works without changes :-)
@meliza: most of bugs are fixed but rtl display is really a headache.
Any help welcome.
SVN 5861
"The () for instance of unknown given names is not printed correctly for
RTL names on the LTR pages or for LTR names on RTL pages."
Corrected
When the development user searches for ורדי on the big file he sees in
the 2nd hit the Sosa and Generations as [2 2] and [3 2] instead of the
expected [2]2 and [3]2. I have seen this format only when a spouse is alive
and the reported name is a Hebrew one.
Corrected.
The – of live people prints still sometimes at the end of the row. Corrected
Marriage data at the end of the row. Corrected.
(unknown), (unknown) name in the spouse's language instead of the page language. Corrected.
Meliza
Christophe,
I know that the soundex for -ski & -ska are equals.
I have a reguest:
Could it be possible to display -ski & -ska names with standard search if the Surname Tradition is set to polish?
@meliza : thanks for the fix for rtl display
ERROR 8: Undefined index: rootid
Fixed by moving pgv_lang[rootid] from admin.en.php to lang.en.php
@wooc : not sure to understand your request. Is it a change for every lists or only for branches.php ? May you post a link with an example. Thanks
New entry "Branches" added to "Lists" menu reusing "patriarch" icon.
It really looks nice. There are a few points I noticed. Using the latest SVN, DM soundex does not seem to work as expected. In addition, it will only show death years if the birth year is known, otherwise it is ignored