From: Tim L. <guy...@gm...> - 2011-08-23 17:26:01
|
I have made a start on implementing GEPS 023 under: https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources But I have some problems with implementing the database upgrade. In particular, I would appreciate some help in adding and removing the backlinks in the reference map. I have looked at update_reference_map in write.py, but this has not helped me enough in implementing the upgrade when the database is not yet fully connected. As a temporary measure, I have modified write.py to connect the secondary tables, and have used update-reference_map in upgrade.py, but this is clearly too inefficient. (I guess I also need to do all the backlink upgrades where the new object is created). I also have a number of questions which are interspersed in the draft code in upgrade.py. (1) Does nesting BSDDBTxn inside DbTxn as I have done mean that the whole of the upgrade of each object instance is done as one transaction (and have I passed the correct transaction parameters?) (2) Do I need to upgrade any other secondary tables (specifically the reference_map_primary_map) (3) Have I implemented the creation of the new citation object in upgrade.py in the appropriate way? (4) The way I find the next gramps id for the new citation is almost certainly not the most efficient approach, and I also don't understand how cmap_index should be used and maintained (it doesn't seem to be initialised or updated). I am sorry that my code in upgrade.py is so untidy at present, but I am trying to work through how it should be implemented. Many thanks if you are able to help. |
From: Benny M. <ben...@gm...> - 2011-08-23 20:29:19
|
2011/8/23 Tim Lyons <guy...@gm...> > I have made a start on implementing GEPS 023 under: > https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-pgrade > of each objesources<https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources> > > But I have some problems with implementing the database upgrade. In > particular, I would appreciate some help in adding and removing the > backlinks in the reference map. I have looked at update_reference_map > in write.py, but this has not helped me enough in implementing the > upgrade when the database is not yet fully connected. > > As a temporary measure, I have modified write.py to connect the > secondary tables, and have used update-reference_map in upgrade.py, > but this is clearly too inefficient. (I guess I also need to do all > the backlink upgrades where the new object is created). > upgrade need not be efficient. Go for clarity of code here, not maximum speed. Creating an object should create backlinks if needed, but that is one function like is done for the other primary objects. > > I also have a number of questions which are interspersed in the draft > code in upgrade.py. > > (1) Does nesting BSDDBTxn inside DbTxn as I have done mean that the > whole of the upgrade of each object instance is done as one > transaction (and have I passed the correct transaction parameters?) > Ask Gerald Britton directly if that is the correct approach (2) Do I need to upgrade any other secondary tables (specifically the > reference_map_primary_map) > you can delete the table and recreate it with the function as used in the tool with that name. That tool is a good way to test your code. > (3) Have I implemented the creation of the new citation object in > upgrade.py in the appropriate way? > it is as the other upgrades. Do try to be consistent with names, so call sourcereference srcref, not source, ... . Also, it is nice to show the numbers in tuples as in new_person = (junk_handle, # 0 gramps_id, # 1 gender, # 2 so it is well readable how the old database structure was, and what the new becomes. (4) The way I find the next gramps id for the new citation is almost > certainly not the most efficient approach, and I also don't understand > how cmap_index should be used and maintained (it doesn't seem to be > initialised or updated). > This is the first use of citations, so why even count it and try to calculate. Just do comething like C%05d or so, and increase your own counter. > > I am sorry that my code in upgrade.py is so untidy at present, but I > am trying to work through how it should be implemented. > About your use of global. I don't like the use of globals in python :-) Here you can just remove it and make it local to gramps_upgrade_16, using something like num_citations += len(new_citation_list) A remark, every sourceref becomes a citation. Is the idea not that we can collaps sourceref in one single citation that is shared? I'm a bit afraid users will have a huge time needed to merge citations to something manageable. Benny > > Many thanks if you are able to help. > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Tim L. <guy...@gm...> - 2011-08-28 10:32:50
|
On 23 Aug 2011, at 21:29, Benny Malengier wrote: > This is the first use of citations, so why even count it and try to > calculate. Just do comething like C%05d or so, and increase your own > counter. > > About your use of global. I don't like the use of globals in > python :-) > Thanks for your advice, which I have implemented. > A remark, every sourceref becomes a citation. Is the idea not that > we can collaps sourceref in one single citation that is shared? I'm > a bit afraid users will have a huge time needed to merge citations > to something manageable. > Yes, every sourceref becomes a citation. A key objective in the way I have specified GEPS 023 is that it should be as simple as possible for users. in fact, users should not notice any difference due to the introduction of citations, unless they want to take advantage of new features. There is no need for users to merge citations unless they want to. I intend to implement a separate Gramplet to merge citations where they refer to the same source and have the same Volume/Page etc. I think it will be better to separate out merging rather that to do it automatically on upgrade. This will allow the user to choose whether they want to merge or not. It will also make it much simpler to change the criteria for merging without changing the main gramps code. I hope you think this approach is OK. |
From: Benny M. <ben...@gm...> - 2011-08-29 06:38:55
|
2011/8/28 Tim Lyons <guy...@gm...> > > On 23 Aug 2011, at 21:29, Benny Malengier wrote: > > This is the first use of citations, so why even count it and try to >> calculate. Just do comething like C%05d or so, and increase your own >> counter. >> >> About your use of global. I don't like the use of globals in python :-) >> >> > Thanks for your advice, which I have implemented. > > > A remark, every sourceref becomes a citation. Is the idea not that we can >> collaps sourceref in one single citation that is shared? I'm a bit afraid >> users will have a huge time needed to merge citations to something >> manageable. >> >> > Yes, every sourceref becomes a citation. > > A key objective in the way I have specified GEPS 023 is that it should be > as simple as possible for users. > > in fact, users should not notice any difference due to the introduction of > citations, unless they want to take advantage of new features. > > There is no need for users to merge citations unless they want to. I intend > to implement a separate Gramplet to merge citations where they refer to the > same source and have the same Volume/Page etc. I think it will be better to > separate out merging rather that to do it automatically on upgrade. This > will allow the user to choose whether they want to merge or not. It will > also make it much simpler to change the criteria for merging without > changing the main gramps code. I hope you think this approach is OK. > Yes, this is the typical approach. However, this is something that should be a tool in my opinion, not a gramplet, that is, something you run perhaps once a year. After the upgrade a request to the user if he wants to run the tool then right away, would be nice. It should also be part of gramps, and ready at time of release :-) Benny |
From: Tim L. <guy...@gm...> - 2011-08-29 09:52:59
|
On 23 Aug 2011, at 21:29, Benny Malengier wrote: > > > 2011/8/23 Tim Lyons <guy...@gm...> > > you can delete the table and recreate it with the function as used > in the tool with that name. That tool is a good way to test your code. > Could someone please explain the difference between Tools -> Family Tree Repair -> Rebuild Reference Maps and Rebuild Secondary Indices. I understand that the first calls write.py reindex_reference_map and the second calls rebuild_secondary. I can see that reindex_reference_map rebuilds the reference maps by going through each primary object, and calling update_reference_map, but what exactly does rebuild_secondary do? Also, in write.py I have had to call self.__connect_secondary() and self.__open_undodb() before doing the gramps_upgrade_16. Would I have to do that if I used the reindex_reference_map function? |
From: Benny M. <ben...@gm...> - 2011-08-29 10:12:26
|
2011/8/29 Tim Lyons <guy...@gm...> > On 23 Aug 2011, at 21:29, Benny Malengier wrote: > > > > 2011/8/23 Tim Lyons <guy...@gm...> > > >> you can delete the table and recreate it with the function as used in the > tool with that name. That tool is a good way to test your code. > > > > Could someone please explain the difference between Tools -> Family Tree > Repair -> Rebuild Reference Maps and Rebuild Secondary Indices. > > I understand that the first calls write.py reindex_reference_map and the > second calls rebuild_secondary. I can see that reindex_reference_map > rebuilds the reference maps by going through each primary object, and > calling update_reference_map, but what exactly does rebuild_secondary do? > Without looking at the code, secondary tables are index tables of bsddb which bsddb can construct automatically, eg our surname table for sorting. Also, in write.py I have had to call self.__connect_secondary() and > self.__open_undodb() before doing the gramps_upgrade_16. Would I have to do > that if I used the reindex_reference_map function? > Large updates are better without the secondary tables connected, as it slows down the upgrade. Then, when finished, you connect them or have bsddb rebuild them. I would have to dive into the code to help more. Benny |
From: Jérôme <rom...@ya...> - 2011-08-31 07:51:30
|
Tim, I just see that there is an "SourceTemplates" project: http://sourcetemplates.org/details.php I did not test GEPS 023 yet, but I guess current citation model could be compliant with this project or their work could be improved by your investigations, isn' it ? Regards, Jérôme Tim Lyons a écrit : > I have made a start on implementing GEPS 023 under: > https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources > > But I have some problems with implementing the database upgrade. In > particular, I would appreciate some help in adding and removing the > backlinks in the reference map. I have looked at update_reference_map > in write.py, but this has not helped me enough in implementing the > upgrade when the database is not yet fully connected. > > As a temporary measure, I have modified write.py to connect the > secondary tables, and have used update-reference_map in upgrade.py, > but this is clearly too inefficient. (I guess I also need to do all > the backlink upgrades where the new object is created). > > I also have a number of questions which are interspersed in the draft > code in upgrade.py. > > (1) Does nesting BSDDBTxn inside DbTxn as I have done mean that the > whole of the upgrade of each object instance is done as one > transaction (and have I passed the correct transaction parameters?) > (2) Do I need to upgrade any other secondary tables (specifically the > reference_map_primary_map) > (3) Have I implemented the creation of the new citation object in > upgrade.py in the appropriate way? > (4) The way I find the next gramps id for the new citation is almost > certainly not the most efficient approach, and I also don't understand > how cmap_index should be used and maintained (it doesn't seem to be > initialised or updated). > > I am sorry that my code in upgrade.py is so untidy at present, but I > am trying to work through how it should be implemented. > > Many thanks if you are able to help. > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2011-09-01 22:13:05
|
Jérôme, Thanks for the link. It seems to be more related to GEPS 018: Evidence style sources. However, they use a two-level source-citation hierarchy like Tim is implementing with GEPS 023. MasterSource is like our Source and SourceDetails is like our Citation. The also have a Repository object. Both there Sources and Citations can have media and comments. With GEPS 023 we will be able to attach both Notes and Media objects to Citations. Nick. On 31/08/11 08:51, Jérôme wrote: > Tim, > > > I just see that there is an "SourceTemplates" project: > http://sourcetemplates.org/details.php > > I did not test GEPS 023 yet, but I guess current citation model could be > compliant with this project or their work could be improved by your > investigations, isn' it ? > > > Regards, > Jérôme > > > Tim Lyons a écrit : >> I have made a start on implementing GEPS 023 under: >> https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources >> >> But I have some problems with implementing the database upgrade. In >> particular, I would appreciate some help in adding and removing the >> backlinks in the reference map. I have looked at update_reference_map >> in write.py, but this has not helped me enough in implementing the >> upgrade when the database is not yet fully connected. >> >> As a temporary measure, I have modified write.py to connect the >> secondary tables, and have used update-reference_map in upgrade.py, >> but this is clearly too inefficient. (I guess I also need to do all >> the backlink upgrades where the new object is created). >> >> I also have a number of questions which are interspersed in the draft >> code in upgrade.py. >> >> (1) Does nesting BSDDBTxn inside DbTxn as I have done mean that the >> whole of the upgrade of each object instance is done as one >> transaction (and have I passed the correct transaction parameters?) >> (2) Do I need to upgrade any other secondary tables (specifically the >> reference_map_primary_map) >> (3) Have I implemented the creation of the new citation object in >> upgrade.py in the appropriate way? >> (4) The way I find the next gramps id for the new citation is almost >> certainly not the most efficient approach, and I also don't understand >> how cmap_index should be used and maintained (it doesn't seem to be >> initialised or updated). >> >> I am sorry that my code in upgrade.py is so untidy at present, but I >> am trying to work through how it should be implemented. >> >> Many thanks if you are able to help. >> >> ------------------------------------------------------------------------------ >> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, >> user administration capabilities and model configuration. Take >> the hassle out of deploying and managing Subversion and the >> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > ------------------------------------------------------------------------------ > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Tim L. <guy...@gm...> - 2011-10-01 14:45:25
|
I have made progress on implementing GEPS 023, many thanks to Nick Hall for implementing treemodels with two object types and to Michiel Nauta for help with upgrade. I would be very grateful if some other developers could have a look at the user interface and try it with their data. The GEPS is at: https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources The principal user interface changes are to the Sources view, and the introduction of the Citations view. Key objectives are that citations can be shared and have Media as well as Notes. I have implemented a 'Merge citation' tool for use after database upgrade, as suggested by Benny on the developers list on 29 Aug. Database upgrade, xml import and export and the various editors are all done. The citation filter is mostly done, but some of the other filters still need some work. GEDCOM import and export and the various reports are the main outstanding things to be implemented. Would it be possible for this GEPS to be added to the roadmap for Gramps 3.4? Tim. |
From: Rob H. <rob...@gm...> - 2011-10-01 15:49:45
|
Greetings: I know that I am not exactly what you were asking about, as in a developer to test and give a complete analysis and help... I am willing to do and try whatever parts that you would need feedback from a user standpoint... I have a good working backup before I even start to use your new LARGE SOURCES! I have been looking forward to this so I have a +1 for implementing this into Gramps-3.4.0 ... Sincerely yours, Rob G. Healey On Sat, Oct 1, 2011 at 7:45 AM, Tim Lyons <guy...@gm...> wrote: > I have made progress on implementing GEPS 023, many thanks to Nick > Hall for implementing treemodels with two object types and to Michiel > Nauta for help with upgrade. > > I would be very grateful if some other developers could have a look at > the user interface and try it with their data. The GEPS is at: > https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources > > The principal user interface changes are to the Sources view, and the > introduction of the Citations view. Key objectives are that citations > can be shared and have Media as well as Notes. > > I have implemented a 'Merge citation' tool for use after database > upgrade, as suggested by Benny on the developers list on 29 Aug. > > Database upgrade, xml import and export and the various editors are > all done. The citation filter is mostly done, but some of the other > filters still need some work. > > GEDCOM import and export and the various reports are the main > outstanding things to be implemented. > > Would it be possible for this GEPS to be added to the roadmap for > Gramps 3.4? > > Tim. > > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > -- Sincerely yours, Rob G. Healey "Always surround yourself with people that inspire you to greatness!" |
From: John R. <jr...@ce...> - 2011-10-02 21:30:37
|
On Oct 1, 2011, at 7:45 AM, Tim Lyons wrote: > I have made progress on implementing GEPS 023, many thanks to Nick > Hall for implementing treemodels with two object types and to Michiel > Nauta for help with upgrade. > > I would be very grateful if some other developers could have a look at > the user interface and try it with their data. The GEPS is at: https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources > > The principal user interface changes are to the Sources view, and the > introduction of the Citations view. Key objectives are that citations > can be shared and have Media as well as Notes. > > I have implemented a 'Merge citation' tool for use after database > upgrade, as suggested by Benny on the developers list on 29 Aug. > > Database upgrade, xml import and export and the various editors are > all done. The citation filter is mostly done, but some of the other > filters still need some work. > > GEDCOM import and export and the various reports are the main > outstanding things to be implemented. > > Would it be possible for this GEPS to be added to the roadmap for > Gramps 3.4? Tim, Sorry I didn't get to this right away... something about getting a release out. ;-) There was a typo in displaytabs/Makefile.am, which I fixed for you, but it won't launch: 456: ERROR: grampsgui.py: line 316: Gramps failed to start. Traceback (most recent call last): File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/gui/grampsgui.py", line 292, in __startgramps Gramps(argparser) File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/gui/grampsgui.py", line 209, in __init__ from viewmanager import ViewManager File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/gui/viewmanager.py", line 69, in <module> from gui.plug import tool File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/gui/plug/__init__.py", line 32, in <module> from _guioptions import GuiMenuOptions, make_gui_option File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/gui/plug/_guioptions.py", line 60, in <module> from Filters import GenericFilterFactory, GenericFilter, Rules File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/Filters/__init__.py", line 31, in <module> from _FilterList import FilterList File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/Filters/_FilterList.py", line 37, in <module> from Filters._FilterParser import FilterParser File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/Filters/_FilterParser.py", line 37, in <module> from Filters import Rules File "/Volumes/RAID1/local/gtk-stable/inst/share/gramps/Filters/Rules/__init__.py", line 42, in <module> from Filters.Rules import (Person, Family, Event, Source, Citation, Place, ImportError: cannot import name Citation Looks like something's missing? Regards, John Ralls |
From: Tim L. <guy...@gm...> - 2011-10-01 22:29:01
|
Thanks for giving it a try, it is really helpful for someone else to have a look. On 1 Oct 2011, at 19:34, "Helge@Gramps" wrote: > This version looks really nice having this new features. I'll try > next few > days how to work using my available data. > Here a first error issue: <snip> > AttributeError: 'Person' object has no attribute > 'get_source_references' > Thanks for the bug report - I will fix that. (Note that the change is not yet complete, so there will doubtless be other things that don't work). > Shall we use the bug tracker for further issues? I don't know. However, since this is not even in the roadmap for 3.4 I imagine that it should NOT go in the bug tracker yet. In fact. I would imagine that it would only go in the bug tracker once the change was committed to trunk, but perhaps someone else could comment. > ___ > > Finally a question: > Citations are more and better in focus than before (having their own > user > table, having filters etc.). That's great. > For my own working process I'm not sure where to place the media > reference > of documents now. In the past I put them all into the gallery of the > source > (using one source for one original document part). Now it would be > more > interesting to have one source having several citations including > the media > reference in the the gallery of the citation. > But it would be hard to change the system for older data. And if I > would use > the new way for new data, than I would have my media references some > time in > the gallery of the sources and some time in the gallery of citation. > And during genaolgic work it's often necessary to check and validate > data to > have access to the original document (via e. g. source -> media --> > external > document). It's not easy and short today and could be more difficult > if > using several places for the media reference. > I hope I could explain my thinking good enough. And may be I'm lost > in my > own thinking. > Im my view, the answer is simple. If there is only ONE citation for a given source, then it doesn't really matter whether the media is in the Source or in the Citation. At the moment, reports etc will be designed for displaying the media with the source, so that is the way to go. However, the real power of the change comes when there are several different Citations for a single source. In that case, when the media is different for the different Citations, then it should be stored with the Citation. > -Helge Tim. |
From: Cedric S. <ce...@no...> - 2011-10-03 12:09:30
|
Tim, On Saturday 01 October 2011 15:45:10 Tim Lyons wrote: > I have made progress on implementing GEPS 023, many thanks to Nick > Hall for implementing treemodels with two object types and to Michiel > Nauta for help with upgrade. > > I would be very grateful if some other developers could have a look at > the user interface and try it with their data. The GEPS is at: > https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-la > rge-sources > > The principal user interface changes are to the Sources view, and the > introduction of the Citations view. Key objectives are that citations > can be shared and have Media as well as Notes. > > I have implemented a 'Merge citation' tool for use after database > upgrade, as suggested by Benny on the developers list on 29 Aug. > > Database upgrade, xml import and export and the various editors are > all done. The citation filter is mostly done, but some of the other > filters still need some work. > > GEDCOM import and export and the various reports are the main > outstanding things to be implemented. > > Would it be possible for this GEPS to be added to the roadmap for > Gramps 3.4? > > Tim. > I tried gep-023-large-sources today and I found one problem which you may not know about. The link from an event to people is missing. 1. Click on Event View 2. Click on an event 3. Click on References and the reference list is empty; in other versions of gramps it has at least one entry You can also see the problem if you add 'Main Participants' to an the Event View; there aren't any main participants. Do you want me to enter a bug report? Finally, I'd like to thank you for taking on the job of implementing this - I think that it's a great addition to gramps and I hope that it gets accepted into trunk in the near future. Cedric |
From: Tim L. <guy...@gm...> - 2011-10-03 14:08:21
|
On 3 Oct 2011, at 13:09, Cedric Scott wrote: > I tried gep-023-large-sources today and I found one problem which > you may not > know about. The link from an event to people is missing. Well spotted, there is a problem with the construction of the secondary index - I will fix it. Thanks very much for this. > Do you want me to enter a bug report? I would imagine not, as it is still in the branch directory at the moment, but I would be very grateful for similar omissions. (although I know that the change is not complete, so there are things that just don't work at the moment). > Finally, I'd like to thank you for taking on the job of implementing > this - I > think that it's a great addition to gramps and I hope that it gets > accepted > into trunk in the near future. Thanks for your comment. Tim. |
From: Tim L. <guy...@gm...> - 2011-10-03 17:23:43
|
On 3 Oct 2011, at 15:08, Tim Lyons wrote: > > On 3 Oct 2011, at 13:09, Cedric Scott wrote: > >> I tried gep-023-large-sources today and I found one problem which >> you may not >> know about. The link from an event to people is missing. > > Well spotted, there is a problem with the construction of the > secondary index - I will fix it. Thanks very much for this. I have fixed this now, commit 18245 in sourceforge. You will need to run "Tools -> Family Tree Repair -> Rebuild Secondary Indices..." to get the link re-created. Tim. |
From: Cedric S. <ce...@no...> - 2011-10-03 18:02:46
|
On Monday 03 October 2011 18:35:20 Helge@Gramps wrote: > Hi Tim, > > I tried the last version after your changes (commit 18245) and did run the > repair tool as described, but when I look at the Event Editor there are > still no references to any other item. You need to rebuild reference maps as well. > > Additional: Drag&Drop to the clipboard doesn't work for citations. > > -Helge Cedric > -- > View this message in context: > http://gramps.1791082.n4.nabble.com/Help-requested-on-database-upgrade-ple > ase-tp3763443p3868238.html Sent from the GRAMPS - Dev mailing list archive > at Nabble.com. > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Doug B. <dou...@gm...> - 2011-10-10 14:47:41
|
On Sat, Oct 1, 2011 at 10:45 AM, Tim Lyons <guy...@gm...> wrote: > I have made progress on implementing GEPS 023, many thanks to Nick > Hall for implementing treemodels with two object types and to Michiel > Nauta for help with upgrade. > > I would be very grateful if some other developers could have a look at > the user interface and try it with their data. The GEPS is at: https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources > > The principal user interface changes are to the Sources view, and the > introduction of the Citations view. Key objectives are that citations > can be shared and have Media as well as Notes. > > I have implemented a 'Merge citation' tool for use after database > upgrade, as suggested by Benny on the developers list on 29 Aug. > > Database upgrade, xml import and export and the various editors are > all done. The citation filter is mostly done, but some of the other > filters still need some work. > > GEDCOM import and export and the various reports are the main > outstanding things to be implemented. > > Would it be possible for this GEPS to be added to the roadmap for > Gramps 3.4? Tim, Excellent work! Overlord Devs: what are the thoughts on this? We going to add this to Gramps 3.4? -Doug > Tim. > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Rob H. <rob...@gm...> - 2011-10-10 22:47:21
|
Greetings: i believe that this should be implemented into Gramps3.4.x ... +1 Sincerely yours, Rob G. Healey On Mon, Oct 10, 2011 at 7:47 AM, Doug Blank <dou...@gm...> wrote: > On Sat, Oct 1, 2011 at 10:45 AM, Tim Lyons <guy...@gm...> wrote: > > I have made progress on implementing GEPS 023, many thanks to Nick > > Hall for implementing treemodels with two object types and to Michiel > > Nauta for help with upgrade. > > > > I would be very grateful if some other developers could have a look at > > the user interface and try it with their data. The GEPS is at: > https://gramps.svn.sourceforge.net/svnroot/gramps/branches/geps/gep-023-large-sources > > > > The principal user interface changes are to the Sources view, and the > > introduction of the Citations view. Key objectives are that citations > > can be shared and have Media as well as Notes. > > > > I have implemented a 'Merge citation' tool for use after database > > upgrade, as suggested by Benny on the developers list on 29 Aug. > > > > Database upgrade, xml import and export and the various editors are > > all done. The citation filter is mostly done, but some of the other > > filters still need some work. > > > > GEDCOM import and export and the various reports are the main > > outstanding things to be implemented. > > > > Would it be possible for this GEPS to be added to the roadmap for > > Gramps 3.4? > > Tim, > > Excellent work! > > Overlord Devs: what are the thoughts on this? We going to add this to > Gramps 3.4? > > -Doug > > > Tim. > > > > > > > > > ------------------------------------------------------------------------------ > > All of the data generated in your IT infrastructure is seriously > valuable. > > Why? It contains a definitive record of application performance, security > > threats, fraudulent activity, and more. Splunk takes this data and makes > > sense of it. IT sense. And common sense. > > http://p.sf.net/sfu/splunk-d2dcopy2 > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > -- Sincerely yours, Rob G. Healey "Always surround yourself with people that inspire you to greatness!" |