From: KURTATAS D. <de...@ot...> - 2013-04-23 15:25:32
|
Hello everyone, I have started using GRAMPS 3.4.2-1 recently. Currently, I am trying to maintain two genealogical trees, e.g. Tree1 and Tree2, but I came up with the following case: Person1 belongs to Tree1 and has been created in Tree1. His spouse belongs to Tree2 and has already been created as Person2 in Tree2. In order to create the family record of Person1 and Person2 in Tree1: (a) Should I have to create another Person3 in Tree 1 (with the same data as the Person2 in Tree2)? (b) Or, there is a way to avoid data duplication by referencing (pointing to) Person2 in Tree2 from Tree1? Thank you in advance for your help Dem |
From: Martin S. <mar...@ma...> - 2013-04-24 13:51:07
|
On Tue, Apr 23, 2013 at 06:25:09PM +0300, KURTATAS DHMHTRIOS wrote: >I have started using GRAMPS 3.4.2-1 recently. Currently, I am trying to maintain two genealogical trees, e.g. Tree1 and Tree2, but I came up with the following case: > >Person1 belongs to Tree1 and has been created in Tree1. >His spouse belongs to Tree2 and has already been created as Person2 in Tree2. > >In order to create the family record of Person1 and Person2 in Tree1: > >(a) Should I have to create another Person3 in Tree 1 (with the same data as the Person2 in Tree2)? Yes. >(b) Or, there is a way to avoid data duplication by referencing (pointing to) Person2 in Tree2 from Tree1? No. Have you considered putting all your data into one tree (= database)? M. |
From: Heinz B. <hei...@ya...> - 2013-04-24 15:44:52
|
Hi Dem, is there a "good" reason for you too keep 2 separate trees? What I would do is to set an attribute "tree 1" to all people from tree1 and an attribute "tree 2" to all people from tree2. Then I would export both trees and import both into a new tree. This way you can reference and connect the persons since they are now in only one tree. For persons belonging to both trees I would then set both attributes (tree 1 and tree 2). If needed you can easily recreate your previous trees by filtering for the according attribute and exporting, the export now containing all persons with the according attribute. But your "working base" would be the one new tree. Maybe there are other opinions and workflows? HTH and kind regards, Heinz On Tue, 23 Apr 2013 17:25:09 +0200, KURTATAS DHMHTRIOS <de...@ot...> wrote: > Hello everyone, > I have started using GRAMPS 3.4.2-1 recently. Currently, I am trying to maintain two genealogical trees, e.g. Tree1 and Tree2, but I came up with the following case: > > Person1 belongs to Tree1 and has been created in Tree1. > His spouse belongs to Tree2 and has already been created as Person2 in Tree2. > In order to create the family record of Person1 and Person2 in Tree1: > (a) Should I have to create another Person3 in Tree 1 (with the same data as the Person2 in Tree2)? > (b) Or, there is a way to avoid data duplication by referencing (pointing to) Person2 in Tree2 from Tree1? > > Thank you in advance for your help > Dem > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users |
From: Ken B <ken...@gm...> - 2013-04-25 06:21:34
|
Hi Dem, The suggested method by Heinz is the best way I have found. Instead for using tree1 and tree2 I use the last names of my grandparents. That make more sense to others reading the tree . In the people view I have set 2 filters, one for all descendants, spouses, children etc of the oldest paternal ancestors, and the same for the oldest maternal ancestors. There is also some good help on the web site about setting up filters. Ken, NZ. On 25/04/13 03:44, Heinz Brinker wrote: > Hi Dem, > > is there a "good" reason for you too keep 2 separate trees? > > What I would do is to set an attribute "tree 1" to all people from tree1 and an attribute "tree 2" to all people from tree2. Then I would export both trees and import both into a new tree. > This way you can reference and connect the persons since they are now in only one tree. > > For persons belonging to both trees I would then set both attributes (tree 1 and tree 2). > > If needed you can easily recreate your previous trees by filtering for the according attribute and exporting, the export now containing all persons with the according attribute. > But your "working base" would be the one new tree. > > Maybe there are other opinions and workflows? > > HTH and kind regards, > Heinz > > > On Tue, 23 Apr 2013 17:25:09 +0200, KURTATAS DHMHTRIOS <de...@ot...> wrote: > >> Hello everyone, >> I have started using GRAMPS 3.4.2-1 recently. Currently, I am trying to maintain two genealogical trees, e.g. Tree1 and Tree2, but I came up with the following case: >> >> Person1 belongs to Tree1 and has been created in Tree1. >> His spouse belongs to Tree2 and has already been created as Person2 in Tree2. >> In order to create the family record of Person1 and Person2 in Tree1: >> (a) Should I have to create another Person3 in Tree 1 (with the same data as the Person2 in Tree2)? >> (b) Or, there is a way to avoid data duplication by referencing (pointing to) Person2 in Tree2 from Tree1? >> >> Thank you in advance for your help >> Dem >> >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Michael G. <mic...@ay...> - 2013-04-25 02:00:47
|
Is there an automated way to set an attribute for all persons in a tree? Better yet, can I filter a tree by some criterion and then set an attribute for all persons who satisfy the filter? Thanks, Michael On Wed, Apr 24, 2013 at 11:44 AM, Heinz Brinker <hei...@ya...>wrote: > ... > What I would do is to set an attribute "tree 1" to all people from tree1 > and an attribute "tree 2" to all people from tree2. Then I would export > both trees and import both into a new tree. > This way you can reference and connect the persons since they are now in > only one tree. > > |
From: Heinz B. <hei...@ya...> - 2013-04-25 06:10:51
|
Hi Michael, you should be able to define a person filter and then call set attribute from the tools -> database processing menu (Exact entry names may differ since I'm using a german version). There you can select the filter you created, set attribute name and value and press execute to add the attribute to all people selected by the given filter. HTH, Heinz > Is there an automated way to set an attribute for all persons in a tree? > Better yet, can I filter a tree by some criterion and then set an > attribute for all persons who satisfy the filter? > > Thanks, > Michael > > On Wed, Apr 24, 2013 at 11:44 AM, Heinz Brinker <hei...@ya...>wrote: > >> ... >> What I would do is to set an attribute "tree 1" to all people from tree1 >> and an attribute "tree 2" to all people from tree2. Then I would export >> both trees and import both into a new tree. >> This way you can reference and connect the persons since they are now in >> only one tree. >> >> |
From: Michael G. <mic...@ay...> - 2013-04-27 14:17:55
|
Thanks for the suggestion, Heinz. I don't see anything like a database processing menu under Tools, but perhaps the problem is that I am using Gramps 3.3.1-1. I'll try to upgrade soon, and then will try again. Yours, Michael On Thu, Apr 25, 2013 at 2:10 AM, Heinz Brinker <hei...@ya...> wrote: > > Hi Michael, > you should be able to define a person filter and then call set attribute from the tools -> database processing menu (Exact entry names may differ since I'm using a german version). There you can select the filter you created, set attribute name and value and press execute to add the attribute to all people selected by the given filter. > > HTH, > Heinz > >> Is there an automated way to set an attribute for all persons in a tree? >> Better yet, can I filter a tree by some criterion and then set an >> attribute for all persons who satisfy the filter? >> >> Thanks, >> Michael >> >> On Wed, Apr 24, 2013 at 11:44 AM, Heinz Brinker <hei...@ya...>wrote: >> >>> ... >>> What I would do is to set an attribute "tree 1" to all people from tree1 >>> and an attribute "tree 2" to all people from tree2. Then I would export >>> both trees and import both into a new tree. >>> This way you can reference and connect the persons since they are now in >>> only one tree. >>> >>> > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users |
From: Tim L. <guy...@gm...> - 2013-04-29 18:22:32
|
Michael Gordy wrote > Thanks for the suggestion, Heinz. I don't see anything like a > database processing menu under Tools, but perhaps the problem is that > I am using Gramps 3.3.1-1. I'll try to upgrade soon, and then will > try again. It's an Addon called "SetAttributeTool", see: http://www.gramps-project.org/wiki/index.php?title=Third-party_Plugins It appears under Tools->Family Tree Processing->Set Attribute... once you have installed it. I had to restart Gramps after installing the addon before it appeared in the menu (but that shouldn't be necessary). It also appears to be available for Gramps 3.3 -- View this message in context: http://gramps.1791082.n4.nabble.com/Cross-referencing-Persons-in-different-Genealogical-Trees-tp4659947p4660003.html Sent from the GRAMPS - User mailing list archive at Nabble.com. |
From: Heinz B. <hei...@ya...> - 2013-04-29 19:38:46
|
Hi Tim, thank you for this additional information. I wasn't aware of this any more. And Michael, please excuse this missing information in my post. > It's an Addon called "SetAttributeTool", see: > http://www.gramps-project.org/wiki/index.php?title=Third-party_Plugins |
From: Ken B <ken...@gm...> - 2013-04-29 21:44:00
|
Hi Heinz, Just one word of warning about this tool, the remove function is problematic and does not remove the attributes set. This applies to the current version. Ken. On 30/04/13 07:38, Heinz Brinker wrote: > Hi Tim, > > thank you for this additional information. I wasn't aware of this any more. And Michael, please excuse this missing information in my post. > >> It's an Addon called "SetAttributeTool", see: >> http://www.gramps-project.org/wiki/index.php?title=Third-party_Plugins > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |