Difference between revisions of "Addon:InformationGraph"

From Gramps
Jump to: navigation, search
m
(svn to git)
(One intermediate revision by one other user not shown)
Line 1: Line 1:
:'''''NB''': The InformationGraph plugin only works with [[3.2 Roadmap|GRAMPS 3.2]], currently (2009-08-21) only available from [[Brief introduction to SVN|Subversion]]''
+
:'''''NB''': The InformationGraph plugin only works with [[3.2 Roadmap|Gramps 3.2]], currently (2009-08-21) only available from [[Brief introduction to Git|Git]]''
  
 
'''InformationGraph''' is a report plugin to generate detailed GraphViz graphs of a database.  It is intended to allow effectiving dumping of a database or select parts of the database, onto dead wood.
 
'''InformationGraph''' is a report plugin to generate detailed GraphViz graphs of a database.  It is intended to allow effectiving dumping of a database or select parts of the database, onto dead wood.

Revision as of 13:04, 7 November 2013

NB: The InformationGraph plugin only works with Gramps 3.2, currently (2009-08-21) only available from Git

InformationGraph is a report plugin to generate detailed GraphViz graphs of a database. It is intended to allow effectiving dumping of a database or select parts of the database, onto dead wood.

Features implemented

  • Dump as much information as possible for each person and event into the node:
    • Date and place of birth
    • Date and cause of death
    • All other events (Residences, Graduations, etc)
    • Occupations
    • Notes
    • Date and place of marriage
    • Possibly references to sources of information
  • Changing the date stringification to print a more human-friendly date. Eg, "16th December, 1842"; "June quarter, 1912"; "about 1875"
  • Include edges for non-primary event participants, eg, Witness, Minister, etc.
  • Add labels for non-standard child relationship edges, or modify style in some way to indicate different types, eg, Adopted, Step child, etc.
  • Use a method similar to the FamilyLines plugin to specify a list of people to start spidering over the database from. Also include a list of people not to spider beyond. This will allow dumps of one side of a family tree.

Features to be implemented

  • Include a legend for edge and node types
  • Have the ability to store profiles of spider settings. Eg, "Mum's family", "Dad's family", "Everyone".