10.4 Assemble an Outline
aka: new child
Index: streamlined reading;
In many cases, the Notes within a Collection will bear little relationshp to each other.
In some cases, the Tags field may be used to group Notes together by topic.
In other cases, Notes within a Collection may be organized by Date.
But in addition to these other organizational paradigms, Notenik has several related capabilites that allow the Notes within a Collection to be assembled into an outline. The Notenik Knowledge Base (this document) is itself an example of how this can be done.
The first step is to add a Seq field to your Collection. This field can then be used to place your Notes into a meaningful sequence.
Next, add a Level field to the Collection. Make use of a text editor to modify the Collection template file to specify how many levels your outline will have, with the top level being 1. You can assign some meaningful bit of text to each number, to make it easier to keep things straight as you are adding Notes to your Collection. Level 1 can be used to represent the top level for the entire Collection.
At this point, if you have an existing outline you wish to import into Notenik, you can use the Import from OPML option to import the data (possibly after exporting it from another app into the neutral OPML format).
Then make a couple of adjustments to your Collection Settings. Uncheck the box that says “Include explicit Body field label on the Display tab,” and check the box that says “Format Display for Streamlined Reading.”
Now start populating your Collection. Set the Sort parm for the Collection to Seq + Title
. Your very first Note should probably represent the top level for the entire Collection, and be assigned a Level of 1, while setting the Seq to 0
, or simply leaving the Seq field blank.
Now build out your outline, using the Level to indicate the depth of each Note within the outline, and using Seq plus Level to indicate the relationships between parents and children.
Note that, on the List tab, your Note titles will be indented to indicate the Level of each Note.
For an outline structure, it's usually handy to assign Seq values so that the numbers assigned indicate the outline structure. For example, a Note with a Seq value of 3.2.4 would be the fourth child of the Note with a Seq value of 3.2.
If you need to insert a Note into the sequence you are building, you can use the Note -> Increment
menu item to increment the Seq value of the selected Note, as well as all following Notes, in order to preserve the existing order and make room for a new Note at the original Seq value of the incremented Note.
In order to have the Seq value incremented automatically for a new Note, first select the preceding Note before adding the new one.
You can perform some basic resequencing by dragging and dropping a Note from one position to another on the List tab. Note that you must move the Drop indicator to a line above and/or below existing Notes in order to indicate a desired new position for an existing Note (in other words, not on top of an existing Note). Only the Note being dragged and dropped will have its Seq value changed.
To add a child Note to an existing Note, ctrl-click on the row representing the existing Note, then select New Child
from the popup menu. This will pre-populate both the Level and Seq fields with appropriate values. (If the intended parent already has other children, you may want to first increment the Seq value of the current first child, to avoid duplicate Seq values.)
As you continue building out your outline, you may wish to make use of a couple of helpful menu items beneath the Collection
menu.
Collection -> Level -> Renumber Seq based on Level
will renumber your entire Collection, preserving the current order, but regenerating Seq values so that each segment of each Seq value is numbered consecutively, without any gaps, and with the number of segments reflecting each Note's level.
Collection -> Level -> Replace Tags based on Seq and Level
will generate Tags with a top level of levels-outline
, and with sub-tags mirroring the structure of your outline. The advantage of navigating your Collection this way is that you will have disclosure triangles, allowing you to drill down to a particular point in the outline, while hiding other branches not currently of interest.
Note that, if you have followed all the instructions above, including modifying your Collection settings, your Display tab will now look a little different.
You will now find that, using the links described above, you can navigate through your entire Collection entirely within the Display tab.
If you'd like, you can use the View -> Show/Hide List
menu item to completely hide the List and Tags tabs.
The overall intent of all this is to provide a “streamlined reading” experience for your Collection, focusing on the outline structure and the content, much as you would when reading a book.
You have several useful options available for exporting an outline like this into some other format.
Export to OPML
(beneath the File
menu) to put your data into a format that can be imported into a dedicated outlining app. Generate Web Book
(also beneath the File
menu) in order to create a set of web pages that are linked together. Export
command beneath the File
menu. And one last tip for a project like this. If you add an Index field, and then use that to provide index terms for your pages, then you can use the Collection -> Generate Index
menu item to generate an index for your Collection (as you might find at the end of a book). The index will be formatted using Markdown, and copied to the system clipboard. Simply create an index Note in your Collection, and use a normal paste command to place your index into the body of your index Note.