From: Gary B. <bur...@ya...> - 2008-06-26 14:06:00
|
>When I do a GEDCOM export with something less than the complete database, I >get all sources, repositories and ALL notes included in the GEDCOM file, not >only those referenced by the included individuals. Seems not to necessary? I've noticed that too. Please create a bug report for it. I'm working through understanding the GEDCOM inport and export code to fix the location import errors you are getting so I shall probably pick up these other issues too. Bye Gary __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html |
From: Gary B. <bur...@ya...> - 2008-06-27 14:58:29
|
>This means that I have to go through all notes and change the private state If I will do a restricted export. >My original questions was about all unnecessay notes etc exported with UNrestricted export for a part of the >complete database. So if I want to give away, as a GEDCOM file, a branch of my family tree to some other family >researcher, who is interested in just that branch of my tree, he/she will the get all sources, repositories and >notes, which I don't think he/she is interested in. As a simple workaround - this might work - I haven't tried it yet 1) Export a filtered subset of people to a Gramps XML file 2) Import the XML file back into an empty database 3) Clean the database using the "Remove Unused Objects" tool to get rid of unwanted objects which should now be unlinked to individuals & families. It might be necessary to do this a few times - events first, then places, sources, notes etc. 4) Export the whole database as a Gedcom Bye Gary __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html |
From: Peter L. <pet...@te...> - 2008-06-27 16:34:09
|
Den Friday 27 June 2008 16:58:24 skrev Gary Burton: > > >This means that I have to go through all notes and change the private state If I will do a restricted export. > >My original questions was about all unnecessay notes etc exported with UNrestricted export for a part of the >complete database. So if I want to give away, as a GEDCOM file, a branch of my family tree to some other family >researcher, who is interested in just that branch of my tree, he/she will the get all sources, repositories and >notes, which I don't think he/she is interested in. > > As a simple workaround - this might work - I haven't tried it yet > > 1) Export a filtered subset of people to a Gramps XML file > 2) Import the XML file back into an empty database > 3) Clean the database using the "Remove Unused Objects" tool to get rid of unwanted objects which should now be unlinked to individuals & families. It might be necessary to do this a few times - events first, then places, sources, notes etc. > 4) Export the whole database as a Gedcom > > Bye > > Gary > Made a quick test. And it works perfectly. I had to do three "Remove Unused Objects" to get rid of all unnecessary info. I got a GEDCOM file of 2 981 bytes in stead of 1 095 773 bytes. (366 times smaller) /Peter |
From: Brian M. <br...@gr...> - 2008-06-27 17:36:05
|
Gary, > >This means that I have to go through all notes and > change the private state If I will do a restricted export. > >My original questions was about all unnecessay notes > etc exported with UNrestricted export for a part of the > >complete database. So if I want to give away, as a > GEDCOM file, a branch of my family tree to some other > family >researcher, who is interested in just that > branch of my tree, he/she will the get all sources, > repositories and >notes, which I don't think he/she > is interested in. > > As a simple workaround - this might work - I haven't > tried it yet > > 1) Export a filtered subset of people to a Gramps XML file > 2) Import the XML file back into an empty database > 3) Clean the database using the "Remove Unused > Objects" tool to get rid of unwanted objects which > should now be unlinked to individuals & families. It > might be necessary to do this a few times - events first, > then places, sources, notes etc. > 4) Export the whole database as a Gedcom This is an excellent observation and suggestion. I think a great feature addition (for ALL export options) would be a new check box labeled "remove unreferenced objects". When this box is checked, Gramps would apply the filters as requested by the user, and then proceed to remove objects without references. It would perform the object clean up over and over until no more objects are removed. ~Brian |
From: S. C. <ste...@gm...> - 2008-06-27 19:12:13
|
> This is an excellent observation and suggestion. I think a great feature addition (for ALL export options) would be a new check box labeled "remove unreferenced objects". When this box is checked, Gramps would apply the filters as requested by the user, and then proceed to remove objects without references. It would perform the object clean up over and over until no more objects are removed. > > ~Brian +1 IMO the checkbox should be checked by default. Stéphane |
From: Espen B. <es...@gm...> - 2008-06-26 15:51:34
|
2008/6/26, Gary Burton <bur...@ya...>: > >When I do a GEDCOM export with something less than the complete database, I > >get all sources, repositories and ALL notes included in the GEDCOM file, not > >only those referenced by the included individuals. Seems not to necessary? > > > I've noticed that too. Please create a bug report for it. I'm working through understanding the GEDCOM inport and export code to fix the location import errors you are getting so I shall probably pick up these other issues too. > > Bye > > > Gary Similar for XML-export gives me even more data when exporting filtered data. See http://bugs.gramps-project.org/view.php?id=2193 Espen |
From: Benny M. <ben...@gm...> - 2008-06-27 07:20:43
|
Filtering is on people. One of the ideas was to also add selection boxes for filters on other objects, and to also be able to not work with export via person but eg do an export of everything related to a specific source. This just to make clear this should be designed very carefully so as to be general and easily extensible. The present code is filter on person with no real thought put into how the other objects come out. It is important to add that, but we need an easy to use and well designed way of doing it (proxy db's and such). Benny 2008/6/26 Espen Berg <es...@gm...>: > 2008/6/26, Gary Burton <bur...@ya...>: > > >When I do a GEDCOM export with something less than the complete > database, I > > >get all sources, repositories and ALL notes included in the GEDCOM > file, not > > >only those referenced by the included individuals. Seems not to > necessary? > > > > > > I've noticed that too. Please create a bug report for it. I'm working > through understanding the GEDCOM inport and export code to fix the location > import errors you are getting so I shall probably pick up these other issues > too. > > > > Bye > > > > > > Gary > > > Similar for XML-export gives me even more data when exporting filtered > data. See http://bugs.gramps-project.org/view.php?id=2193 > > > Espen > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Peter L. <pet...@te...> - 2008-06-27 11:37:52
|
Ok agreed, but another question: If I check "Restrict data on living people" all their notes are exported. However, the notes are not connected to any "living" person, but can be found in the Notes View. As notes can contain any information, this is a problem if you do not wish to export all information. /Peter > Filtering is on people. > One of the ideas was to also add selection boxes for filters on other > objects, and to also be able to not work with export via person but eg do an > export of everything related to a specific source. > > This just to make clear this should be designed very carefully so as to be > general and easily extensible. > The present code is filter on person with no real thought put into how the > other objects come out. It is important to add that, but we need an easy to > use and well designed way of doing it (proxy db's and such). > > Benny > > 2008/6/26 Espen Berg <es...@gm...>: > > > 2008/6/26, Gary Burton <bur...@ya...>: > > > >When I do a GEDCOM export with something less than the complete > > database, I > > > >get all sources, repositories and ALL notes included in the GEDCOM > > file, not > > > >only those referenced by the included individuals. Seems not to > > necessary? > > > > > > > > > I've noticed that too. Please create a bug report for it. I'm working > > through understanding the GEDCOM inport and export code to fix the location > > import errors you are getting so I shall probably pick up these other issues > > too. > > > > > > Bye > > > > > > > > > Gary > > > > > > Similar for XML-export gives me even more data when exporting filtered > > data. See http://bugs.gramps-project.org/view.php?id=2193 > > > > > > Espen > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > -- Peter Landgren Talken Hagen 671 94 Brunskog SWEDEN 0570-530 21 070-635 4719 pet...@te... skype:pgl4820.2 |
From: Benny M. <ben...@gm...> - 2008-06-27 12:12:18
|
Brian, should we consider this as a major issue that needs resolving in 3.0.1? 2008/6/27 Peter Landgren <pet...@te...>: > Ok agreed, but another question: > If I check "Restrict data on living people" all their notes are exported. > However, the notes are not connected to any "living" person, but can be > found in the Notes View. > As notes can contain any information, this is a problem if you do not wish > to export all information. very true. Notes with living people should be restricted if their data is restricted in my opinion too. Obviously, this means shared notes cause some troubles, they must be restricted as soon as one person is restricted. Technically it should be possible, but again all will be a lot slower again. The restrict living works on a proxy database, see gen/proxy/db, so technically I would do the following: 1/if an object is requested in the database all persons it connects too must be requested. Then on all persons one must ask if living, and replace the object with the default if indeed living (eg for notes I would replace the text with: 'note connected to living person') 2/above would mean some quick caching is needed, that is, every person of which living or not it is asked is stored in a dictionary with the result (True False), and before the check the dictionary is checked before running the probably alive function. Benny > > /Peter > > > Filtering is on people. > > One of the ideas was to also add selection boxes for filters on other > > objects, and to also be able to not work with export via person but eg do > an > > export of everything related to a specific source. > > > > This just to make clear this should be designed very carefully so as to > be > > general and easily extensible. > > The present code is filter on person with no real thought put into how > the > > other objects come out. It is important to add that, but we need an easy > to > > use and well designed way of doing it (proxy db's and such). > > > > Benny > > > > 2008/6/26 Espen Berg <es...@gm...>: > > > > > 2008/6/26, Gary Burton <bur...@ya...>: > > > > >When I do a GEDCOM export with something less than the complete > > > database, I > > > > >get all sources, repositories and ALL notes included in the GEDCOM > > > file, not > > > > >only those referenced by the included individuals. Seems not to > > > necessary? > > > > > > > > > > > > I've noticed that too. Please create a bug report for it. I'm working > > > through understanding the GEDCOM inport and export code to fix the > location > > > import errors you are getting so I shall probably pick up these other > issues > > > too. > > > > > > > > Bye > > > > > > > > > > > > Gary > > > > > > > > > Similar for XML-export gives me even more data when exporting filtered > > > data. See http://bugs.gramps-project.org/view.php?id=2193 > > > > > > > > > Espen > > > > > > > ------------------------------------------------------------------------- > > > Check out the new SourceForge.net Marketplace. > > > It's the best place to buy or sell services for > > > just about anything Open Source. > > > http://sourceforge.net/services/buy/index.php > > > _______________________________________________ > > > Gramps-devel mailing list > > > Gra...@li... > > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > > > -- > Peter Landgren > Talken Hagen > 671 94 Brunskog > SWEDEN > > 0570-530 21 > 070-635 4719 > pet...@te... > skype:pgl4820.2 > |
From: Benny M. <ben...@gm...> - 2008-06-27 12:25:22
|
Looking at the code, it seems all would become most complicated. Perhaps it's better to offer on export/report * private/public * list of filter for persons, source, event, place, note, repository * Every filter corresponds to an easy to understand proxy db, that can be stacked * on running things, stack the proxy's and process the data. So remove living info with no private data means: 1/select private check box 2/select person filter: Entire database 3/select for person check box: restrict data on living 4/select source filter: Entire database 5/select if you want so: exclude sources connected to living people 6/select note filter: Entire database 7/select if you want so: exclude notes connected to living people .... Then the final proxy database is constructed from a long list of intermediate proxy databases: proxy --> private --> living --> filter person all --> filter source all --> living source --> ..... As all proxy's have limited complexity, all should remain maintainable. Benny 2008/6/27 Benny Malengier <ben...@gm...>: > Brian, should we consider this as a major issue that needs resolving in > 3.0.1? > > 2008/6/27 Peter Landgren <pet...@te...>: > >> Ok agreed, but another question: >> If I check "Restrict data on living people" all their notes are exported. >> However, the notes are not connected to any "living" person, but can be >> found in the Notes View. >> As notes can contain any information, this is a problem if you do not wish >> to export all information. > > > very true. > Notes with living people should be restricted if their data is restricted > in my opinion too. > Obviously, this means shared notes cause some troubles, they must be > restricted as soon as one person is restricted. > > Technically it should be possible, but again all will be a lot slower > again. The restrict living works on a proxy database, see gen/proxy/db, so > technically I would do the following: > > 1/if an object is requested in the database all persons it connects too > must be requested. Then on all persons one must ask if living, and replace > the object with the default if indeed living (eg for notes I would replace > the text with: 'note connected to living person') > 2/above would mean some quick caching is needed, that is, every person of > which living or not it is asked is stored in a dictionary with the result > (True False), and before the check the dictionary is checked before running > the probably alive function. > > Benny > > >> >> /Peter >> >> > Filtering is on people. >> > One of the ideas was to also add selection boxes for filters on other >> > objects, and to also be able to not work with export via person but eg >> do an >> > export of everything related to a specific source. >> > >> > This just to make clear this should be designed very carefully so as to >> be >> > general and easily extensible. >> > The present code is filter on person with no real thought put into how >> the >> > other objects come out. It is important to add that, but we need an easy >> to >> > use and well designed way of doing it (proxy db's and such). >> > >> > Benny >> > >> > 2008/6/26 Espen Berg <es...@gm...>: >> > >> > > 2008/6/26, Gary Burton <bur...@ya...>: >> > > > >When I do a GEDCOM export with something less than the complete >> > > database, I >> > > > >get all sources, repositories and ALL notes included in the GEDCOM >> > > file, not >> > > > >only those referenced by the included individuals. Seems not to >> > > necessary? >> > > > >> > > > >> > > > I've noticed that too. Please create a bug report for it. I'm >> working >> > > through understanding the GEDCOM inport and export code to fix the >> location >> > > import errors you are getting so I shall probably pick up these other >> issues >> > > too. >> > > > >> > > > Bye >> > > > >> > > > >> > > > Gary >> > > >> > > >> > > Similar for XML-export gives me even more data when exporting filtered >> > > data. See http://bugs.gramps-project.org/view.php?id=2193 >> > > >> > > >> > > Espen >> > > >> > > >> ------------------------------------------------------------------------- >> > > Check out the new SourceForge.net Marketplace. >> > > It's the best place to buy or sell services for >> > > just about anything Open Source. >> > > http://sourceforge.net/services/buy/index.php >> > > _______________________________________________ >> > > Gramps-devel mailing list >> > > Gra...@li... >> > > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > >> > >> >> >> >> -- >> Peter Landgren >> Talken Hagen >> 671 94 Brunskog >> SWEDEN >> >> 0570-530 21 >> 070-635 4719 >> pet...@te... >> skype:pgl4820.2 >> > > |
From: Brian M. <br...@gr...> - 2008-06-27 13:38:18
|
> Brian, should we consider this as a major issue that needs > resolving in > 3.0.1? > > Ok agreed, but another question: > > If I check "Restrict data on living people" > all their notes are exported. > > However, the notes are not connected to any > "living" person, but can be > > found in the Notes View. > > As notes can contain any information, this is a > problem if you do not wish > > to export all information. > very true. > Notes with living people should be restricted if their data > is restricted in > my opinion too. > Obviously, this means shared notes cause some troubles, > they must be > restricted as soon as one person is restricted. In my humble opinion, everything is working properly. There is no such thing as a "living" note. Only *people* can be living. When filtering living people, notes are not treated any differently than places or sources. When you restrict data on living people, the output will not associate any notes with people who are living - the same as events, places and sources. If you have notes in your database that you don't want to export, I suggest you mark them as private and also exclude private data on your export. ~Brian |
From: Peter L. <pet...@te...> - 2008-06-27 14:21:52
|
Den Friday 27 June 2008 15:38:19 skrev Brian Matherly: > > Brian, should we consider this as a major issue that needs > > resolving in > > 3.0.1? > > > > Ok agreed, but another question: > > > If I check "Restrict data on living people" > > all their notes are exported. > > > However, the notes are not connected to any > > "living" person, but can be > > > found in the Notes View. > > > As notes can contain any information, this is a > > problem if you do not wish > > > to export all information. > > > very true. > > Notes with living people should be restricted if their data > > is restricted in > > my opinion too. > > Obviously, this means shared notes cause some troubles, > > they must be > > restricted as soon as one person is restricted. > > In my humble opinion, everything is working properly. There is no such thing as a "living" note. Only *people* can be living. When filtering living people, notes are not treated any differently than places or sources. > > When you restrict data on living people, the output will not associate any notes with people who are living - the same as events, places and sources. > > If you have notes in your database that you don't want to export, I suggest you mark them as private and also exclude private data on your export. > > ~Brian > This means that I have to go through all notes and change the private state If I will do a restricted export. My original questions was about all unnecessay notes etc exported with UNrestricted export for a part of the complete database. So if I want to give away, as a GEDCOM file, a branch of my family tree to some other family researcher, who is interested in just that branch of my tree, he/she will the get all sources, repositories and notes, which I don't think he/she is interested in. This is a limitation for exchanging GEDCOM files with subparts of the database. /Peter |
From: Gerald B. <ger...@gm...> - 2008-06-27 14:27:00
|
I think what is being asked here is to restrict an export to the people being filtered and the other objects that link to them, somehow. So say I have John Foo in my database and two places: Foo's Home and Bar's Home. John Foo has a reference (say, in an event) to Foo's Home but not to Bar's home. If I want to export data and I filter on John Foo, I would expect the place Foo's Home to be exported but not Bar's Home. The same idea would apply to other objects as well. The difficulty is the recursive tree-like nature of the relationships. So John Foo could have a residence event at Foo's Home that has a source reference of Foo's Deed that has a repository of Foo's Study which is located at Foo's Home. Each of these might have a note or two, just for fun. On Fri, Jun 27, 2008 at 9:38 AM, Brian Matherly <br...@gr...> wrote: >> Brian, should we consider this as a major issue that needs >> resolving in >> 3.0.1? > >> > Ok agreed, but another question: >> > If I check "Restrict data on living people" >> all their notes are exported. >> > However, the notes are not connected to any >> "living" person, but can be >> > found in the Notes View. >> > As notes can contain any information, this is a >> problem if you do not wish >> > to export all information. > >> very true. >> Notes with living people should be restricted if their data >> is restricted in >> my opinion too. >> Obviously, this means shared notes cause some troubles, >> they must be >> restricted as soon as one person is restricted. > > In my humble opinion, everything is working properly. There is no such thing as a "living" note. Only *people* can be living. When filtering living people, notes are not treated any differently than places or sources. > > When you restrict data on living people, the output will not associate any notes with people who are living - the same as events, places and sources. > > If you have notes in your database that you don't want to export, I suggest you mark them as private and also exclude private data on your export. > > ~Brian > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2008-06-27 14:49:09
|
2008/6/27 Gerald Britton <ger...@gm...>: > I think what is being asked here is to restrict an export to the > people being filtered and the other objects that link to them, > somehow. So say I have John Foo in my database and two places: Foo's > Home and Bar's Home. John Foo has a reference (say, in an event) to > Foo's Home but not to Bar's home. If I want to export data and I > filter on John Foo, I would expect the place Foo's Home to be exported > but not Bar's Home. > > The same idea would apply to other objects as well. The difficulty is > the recursive tree-like nature of the relationships. So John Foo > could have a residence event at Foo's Home that has a source reference > of Foo's Deed that has a repository of Foo's Study which is located at > Foo's Home. Each of these might have a note or two, just for fun. > Yes, and this is why I suggested to thread all objects independently with it's own filter. Like that it is clear what will be exported, and GRAMPS need not assume. Benny > > > > > On Fri, Jun 27, 2008 at 9:38 AM, Brian Matherly > <br...@gr...> wrote: > >> Brian, should we consider this as a major issue that needs > >> resolving in > >> 3.0.1? > > > >> > Ok agreed, but another question: > >> > If I check "Restrict data on living people" > >> all their notes are exported. > >> > However, the notes are not connected to any > >> "living" person, but can be > >> > found in the Notes View. > >> > As notes can contain any information, this is a > >> problem if you do not wish > >> > to export all information. > > > >> very true. > >> Notes with living people should be restricted if their data > >> is restricted in > >> my opinion too. > >> Obviously, this means shared notes cause some troubles, > >> they must be > >> restricted as soon as one person is restricted. > > > > In my humble opinion, everything is working properly. There is no such > thing as a "living" note. Only *people* can be living. When filtering living > people, notes are not treated any differently than places or sources. > > > > When you restrict data on living people, the output will not associate > any notes with people who are living - the same as events, places and > sources. > > > > If you have notes in your database that you don't want to export, I > suggest you mark them as private and also exclude private data on your > export. > > > > ~Brian > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |
From: Gerald B. <ger...@gm...> - 2008-06-27 14:53:41
|
yup. agree with that. Leave it up to the user. Not that it is impossible to do what I described -- just difficult and would probably perform badly in most cases On Fri, Jun 27, 2008 at 10:49 AM, Benny Malengier <ben...@gm...> wrote: > > > 2008/6/27 Gerald Britton <ger...@gm...>: >> >> I think what is being asked here is to restrict an export to the >> people being filtered and the other objects that link to them, >> somehow. So say I have John Foo in my database and two places: Foo's >> Home and Bar's Home. John Foo has a reference (say, in an event) to >> Foo's Home but not to Bar's home. If I want to export data and I >> filter on John Foo, I would expect the place Foo's Home to be exported >> but not Bar's Home. >> >> The same idea would apply to other objects as well. The difficulty is >> the recursive tree-like nature of the relationships. So John Foo >> could have a residence event at Foo's Home that has a source reference >> of Foo's Deed that has a repository of Foo's Study which is located at >> Foo's Home. Each of these might have a note or two, just for fun. > > Yes, and this is why I suggested to thread all objects independently with > it's own filter. Like that it is clear what will be exported, and GRAMPS > need not assume. > > Benny >> >> >> >> >> On Fri, Jun 27, 2008 at 9:38 AM, Brian Matherly >> <br...@gr...> wrote: >> >> Brian, should we consider this as a major issue that needs >> >> resolving in >> >> 3.0.1? >> > >> >> > Ok agreed, but another question: >> >> > If I check "Restrict data on living people" >> >> all their notes are exported. >> >> > However, the notes are not connected to any >> >> "living" person, but can be >> >> > found in the Notes View. >> >> > As notes can contain any information, this is a >> >> problem if you do not wish >> >> > to export all information. >> > >> >> very true. >> >> Notes with living people should be restricted if their data >> >> is restricted in >> >> my opinion too. >> >> Obviously, this means shared notes cause some troubles, >> >> they must be >> >> restricted as soon as one person is restricted. >> > >> > In my humble opinion, everything is working properly. There is no such >> > thing as a "living" note. Only *people* can be living. When filtering living >> > people, notes are not treated any differently than places or sources. >> > >> > When you restrict data on living people, the output will not associate >> > any notes with people who are living - the same as events, places and >> > sources. >> > >> > If you have notes in your database that you don't want to export, I >> > suggest you mark them as private and also exclude private data on your >> > export. >> > >> > ~Brian >> > >> > >> > ------------------------------------------------------------------------- >> > Check out the new SourceForge.net Marketplace. >> > It's the best place to buy or sell services for >> > just about anything Open Source. >> > http://sourceforge.net/services/buy/index.php >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > > |