From: lcc <lc...@6z...> - 2009-08-30 14:08:39
|
Hello Frederico. I really don't know how hard it'd be to add that feature to GRAMPS. I suppose this should be a common pattern: people using a GRAMPS Family Tree (database) for their ahnentafel. Then using different Family Trees for each complete family from which they descend, i.e., all collateral relatives: uncles/aunts, great-uncles, etc. The way it is now (importing) there seems to be no smooth way of handling this. So I think the cross-database navigation is a good idea. Provided that it isn't too hard to implement which is not for me to tell. Regards. --lcc On Sat, 08/29/2009 at 10:30pm, "Frederico Muñoz" <fs...@gm...> wrote: > Hello all, > > This is a very general idea that I'm not sure has been discussed > before. I was looking at one of my trees (my personal one in fact) > that contains as "root" persons both myself and my wife. It got me > thinking that perhaps splitting them would be nice in terms of > management but I would lose the ability to easily navigate by choosing > "Spouse". > > Now, this is not something I consider essential, but I thought that > there could be some way to make some individuals "entry points" to > another database. I know that in general when there is a relationship > people just import (after verifying the data, etc), but this could > perhaps be useful in providing a slightly more decentralised model, > since one would have different databases, that could even be managed > and altered by different people, but navigate to them when needed > through individuals that are "shared". > > This is likely not a great idea, but one never knows ;) > > Regards, > > Frederico > > ----------------------------------------------------------------------------- > - > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities. |
From: lcc <lc...@6z...> - 2009-08-31 13:14:13
|
Hello To be totally honest I have been using GRAMPS for a while but have not used filters. Maybe using a single database and working with filters could be a workaround but it definitely seems not to be as smooth as the proposal of cross-database-linking. What you write about merging is actually another issue. The export should imo be also able (perhaps optionally) to export all the "foreign" (from another db) people and all linked people (relatives/spouses) in the "other db". Then merging could also theoretically work with all databases. It would be as a single database, just split for the sake of organization. This is still a cloudy subject but it seems very worth discussing. Regarding Benny's comment on data integrity I think such a "foreign person" should only be editable synchronously. That still leaves some integrity problems but perhaps they could be worked around. It seems it should be for all purposes a single person if that is possible. Kind regards --lcc On Mon, 08/31/2009 at 6:23am, "derHeinzi" <hei...@ya...> wrote: > Richard Stitz-2 wrote: >> >> I think linking multiple databases is one of the best ideas I've seen >> thus far (I haven't been subscribed long though). My aunts and uncles >> by marriage would love to have their own database for their >> families...not to mention spouses of cousins, and if we could have just >> one primary root tree with smaller databases for extended family, it >> would surely clean things up for us and make it so much easier to avoid >> duplications and errors. >> > > Sorry, Richard, but I do not agree. > At first this might seem a charming idea, but what will follow afterwards? > Assuming you "split off" a part of your database and link to it as a 2nd > database. You give a copy of this 2nd database to your aunt and your uncle. > Both find new information and enter it in their databases. Wouldn't you want > to see the new information from both, after they give you their updated > database versions? Wouldn't they want to see what the other found (merge the > data)? And what if you find new data for their part of the database? > And how far will you go in splitting up? Split at every marriage > (automatically)? > > I think for your described purpose a central server with one database for > your whole family and relatives by marriage would be more suitable. > > If GRAMPS should be changed to allow working with 2 databases at the same > time, I would prefer something like a difference browser with merge options. > > > It should work as follows: > 1.) You open your working database. > 2.) You open a second database (read only?). > 3.) You select a person in your working database. > 4.) You select the same(!) person in the 2nd database. > 5.) GRAMPS scans the data in the databases (recursively) starting at this > person and provides a visual browser (tree display?) which shows where > differences (disregarding the GRAMPS ID) between the databases exist. > 6.) You can select a marked node in this browser and a dialog shows the > difference to your database e.g. > - added data (dates, children, spouses, notes, families, sources, ...) > - differences in data (dates, names, children, spouses, notes, sources, ...) > 7.) You can select to take over the information (add or replace, only one > item or tree below, including or excluding notes, media, sources, ...) > 8.) If you take over the information a "source" (you define once for this > compare) is automatically added to the new items. > > This is only a rough scheme. After selecting a difference there might be a > list of differences for this node and you can select the difference to work > on (e.g. different birth date or missing daughter). After selection of the > difference, the standard GRAMPS dialog for this piece of information is > shown twice. One with your data (active), one with the new data (grayed out) > and a button "take over". > > This would allow you and your relatives to work on a copy of the same > database and to easily merge the results at a later point in time. Thats > what I am missing most in GRAMPS. To be able to give my database to some > relative and easily take over his added or changed information after some > time. > > Kind regards > derHeinzi > > > -- > View this message in context: http://www.nabble.com/Allow-cross-database- > navigation-when-clicking-on-an-individual-tp25208009p25220553.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > > ----------------------------------------------------------------------------- > - > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities. |