Reports – Point Form Narratives Setup #reports

Rev 2016-04-05: Version 2
Tired of verbose and repetitious sentences in narrative reports and the effort involved in customising and tweaking them so that grammar and prepositions and pronouns were correct, I got the idea some years ago that what I might prefer is a hybrid of the tabular format of the Individual Summary and Family Group Sheet with event/fact notes embedded rather than at the end. Jerry Bryan demonstrated such a concept with his Oct 12, 2015 RootsMagic Forums posting, “Preparing an RM Descendant Narrative Report for a Family Reunion for This Year“. While he did so using largely manual procedures, this SQLite script makes it easy to try out a similar format and then restore your prior format.

SettingsNormalPoint Form
Normal – “Keep facts in same paragraph”Point Form – space character starts fact, 0 Carriage Returns

Note that for all examples of Point Form, the RootsMagic report settings option for paragraphing is set to “Keep facts in same paragraph”.

Although the Point Form is not strictly point form because the facts run together in the same paragraph, it is actually better for fast reading than is the Normal report because there are fact names that catch the eye, the ‘sentences’ are terse and consistent and it is the most efficient in use of space and paper.

DescNarrJohnWoods-Normal0DescNarrJohnWoods-Normal0.pngDescNarrJohnWoods-PointForm0DescNarrJohnWoods-PointForm0.png
Normal – “New paragraph after every fact”Point Form – 2 Carriage Returns start fact

Both of these waste trees!

DescNarrJohnWoods-Normal1DescNarrJohnWoods-Normal1.pngDescNarrJohnWoods-PointForm2DescNarrJohnWoods-PointForm2.png
Normal – “New paragraph after facts with notes”Point Form – 1 Carriage Return starts fact

This Point Form layout is the most attractive of the three or, at least, comes closest to the concept of a hybrid of the Individual Summary and Narrative report.

DescNarrJohnWoods-Normal2DescNarrJohnWoods-Normal2.pngDescNarrJohnWoods-PointForm1DescNarrJohnWoods-PointForm1.png

Features:

  • Backs up key tables or parts thereof to ‘x’ versions which are used by the complementary script to restore back to the previous format.
  • User control* over fact/event sentence heading format: one of plain, bold, italics, underlined.
  • User control* over fact/event sentence lead-in carriage returns.
  • Changes default sentences to point form without [person] variables.
  • Default sentences begin with the fact type name as a heading. This is the name defined in Lists>Fact Type List; the user can edit user-defined fact types in RootsMagic.
  • Alternate Names are labelled by their type, if assigned in the Edit Person screen.
  • Shared events show the role names of the sharers.
  • Adds _Heading event to provide the initial [person] sentence as the first ‘fact’ so each person’s section will start with the person’s name and not be stated as ‘factless’. Version 2 does not do this; instead it uses a Jerry Bryan trick of putting a line feed/carriage return after the [Person] variable for the Birth sentence template, normally the person’s first event. This does require a Birth event as the first event to be output to the narrative report.
  • Adds two trailing CR/LF to the Note field of the last family event (by SortDate) of each couple to force the spouse’s subsection of a person’s report section to start a new paragraph. (V2)

*The script works best with a SQLite manager that supports run-time variables such as SQLite Expert Personal to provide control over the format of fact headings and fact paragraphing. Those that do not support them, such as SQLiteSpy, default to bold and no <CR>s. In either case, a RMNOCASE collation extension is needed. To add the RNMOCASE collation extension, see either:

Version 2
Reports-PointFormNarrativeSetup2.sql
Reports-RestoreAfterPointForm2.sql
Version 1
Reports-PointFormNarrativeSetup.sql
Reports-RestoreAfterPointForm.sql

Use:

  1. Open your database (safer to use a copy) with your SQLite manager.
  2. Load the RMNOCASE extension.
  3. Load the SQLite script Reports-PointFormNarrativeSetup.sql.
  4. Execute the script.
  5. SQLite will throw an error if the database has been previously modified by this script without subsequently running Reports-RestoreAfterPointForm.sql. Load and run the latter and return to step 3.
  6. If prompted for a value for $FactNameFormat_ibun, type in one of the letters: italics, bold, underline, no and OK. Any value other than i, u, n is the same as b.
  7. If prompted for a value for $ParagraphCR_0_1_2, type in one of the numbers 0,1,2 to define the number of Carriage Returns prepended to the sentence. Any value other than 1 or 2 is the same as 0 – a leading space character.
  8. On successful completion the results window will display a status message so reporting.
  9. Open RootsMagic and generate narrative reports. Use the Report Settings Option “Keep fact sentences in same paragraph” to start, especially if you have chosen to have lead-in carriage returns.
  10. You can leave the report preview open and rerun the scripts to switch back to original and to different point form formats. After each execution of a script, you can quickly see its effects from report view with Alt-t to return to Report Settings and <Enter> to regenerate the report with the changes.
  11. You may want to try some other scripts that affect reports after having set up your database for point-form reports:

5 Replies to “Reports – Point Form Narratives Setup #reports

  1. I finally made the switch about a year ago to RM9.

    Has anyone used this script in RM9? I am getting an error
    table xfactTypeTable has 10 columns but 11 values were supplied.
    SQL Statement:
    INSERT INTO xfactTypeTable
    SELECT *FROM FactTypeTable
    ;.

    I really liked this report in RM7 and was hoping to use it again.

    Keep in mind, I am an SQL dummy and need either VERY specific instructions or someone to modify the script for me.

  2. Hi Jaime, those scripts are well and truly for RM7 or earlier because changes to table definitions in RM8 and RM9 have rendered them incompatible. The common one that springs to mind was the addition of the UTCModDate column to every table but there may be more. It would take some time to investigate, revise and test.

    That you are the only one to have expressed the wish to use them with RM8 and RM9 databases is a bit of a disappointment, given that we are now years into both their releases. I’m still unpacking and setting up after a major move so don’t hold your breath in the hope that I will get to it soon.

  3. Tom,

    Thanks for your reply 🙂 I must have missed my notification and just saw it.

    I am surprised no one else has wanted to use the point-form narrative reports either. I thought maybe I could create my own using custom reports … boy was I wrong! I have never thought much about that RM feature. It sounds a lot better than it is, but maybe I’m missing something. Correct me if I am wrong!

    I am sympathetic to your major move; I moved about 9 months ago and am still switching things around from one drawer to another or one closet to another. I’m driving myself a bit crazy!

    Good luck settling in!

    Jaime

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.