Version: 2.50, released 04 Feb 2017 <details>
Notenik is a system for recording, collecting and referencing notes.
Notenik is really three things:
The Notenik design is based on the following principles.
If this set of principles sounds appealing to you, then Notenik may be just what you’ve been looking for.
Each Note is stored as a separate text file, in the UTF-8 format, capable of being read and modified by any text editor, on almost any computer system in the world.
A note file may be stored with any of the following file extensions:
A Collection of Notes is stored as a folder (aka directory). A collection resides on a local disk or file share, but may be synced to the cloud and to other devices and users via a service such as Dropbox or iCloud.
Each Note contains a number of Fields.
At its most basic, a note consists of a Title Field and a Body Field.
Each Field in a Note consists of the Field Label, followed by a colon and one or more spaces, followed by the Field Value.
A Field Label must always start at the beginning of a line. A Field Label may not consist of more than 48 characters, and may not contain a comma (‘,’).
The Field Value may be specified on the same line, and/or on one or more following lines.
The Body Field, if present, will always be the last Field in a Note, since all following text will be assumed to be part of the Body (even if it contains strings of text that might otherwise appear to be additional Field Labels).
Each Note must have a Title that is unique within its Collection. Each Note’s file name is based on its Title, and each Note’s file name must also be unique within its folder.
Each Field Label may be considered to have a proper form (including capitalization, spaces and punctuation), and a common form (the proper form without capitalization, whitespace or punctuation). The common form is considered to be the key identifier for the Field, so that any variations of the Label that include the same letters and digits in the same sequence will be considered equivalent.
The Notenik data format is intended be easily read and edited by humans, using any text editor. Following is an example of a Note.
Title: The unique title for this note Author: The author of the Note Date: 2016-12-13 Status: 0 - Suggested Type: The type of note Seq: Rev Letter or Version Number Tags: One or more tags, separated by commas Link: http://notenik.com Rating: 5 Index: Index Term 1; Teaser: A brief sample of the note Body: The substance of the note
By default, Notenik shows only four Fields for a Note: Title, Link, Tags and Body. However, this default may be altered by placing a file named ‘template.txt’ or ‘template.md’ within a Collection’s folder. Such a file should be in the normal Notenik format, as depicted above, although the Field Labels specified need not have any accompanying values. When such a template file is found, the field names found in this file will be used as the fields to be displayed and maintained for that Collection. This file should be created using a text editor – not using the Notenik app itself for this purpose. The file extension used for the template file will be used as the file extension for Notes subsequently created within the Collection.
The following Field Labels are typically expected to be used within Notes, and often have some special rules associated with them. Note that not all Collections need use all of these fields, and not all Notes within a Collection need specify all of the Fields used within the Collection. Other fields may be specified, and will be treated as simple text fields.
Each Note in a Collection must have a unique Title. If a Title is not specified within a Note file, then the file name (without the extension) will be used as the Title of the Note.
Tags may be used to group related notes into categories. One or more tags may be associated with each note, and each tag may contain one or more sub-tags. A period or a slash may be used to separate one level of a tag from the next level, with the period being preferred. A comma or a semi-colon may be used to separate one tag from another, with the comma being preferred.
The “Favorites” tag may be used to identify favored notes within a collection, and these notes will appear on the Favorites Report. The “Startup” tag may be used to identify notes whose links you wish to have opened by the application when it first starts.
A Hyperlink (aka URL) that can be opened by a Web browser. Notice that a Collection of Notes with Links is essentially a set of Web bookmarks.
The author(s) of the Note.
Your rating of the note, on a scale of one to five.
The type of note. Any values may be used to distinguish between different types of notes within a collection.
The state of the note, indicating its degree of completion. Status values are usually selected from the following standard list. Note that each status may be represented by a single digit and/or an associated label. The digits serve to place the values into an approximate life cycle sequence.
The labels may be modified by placing a series of integer + label pairs in the data area of the relevant template file, with separating punctuation. The template line might look something like this:
Status: 1 - Idea; 4 - In Work; 9 - Published;
A revision letter or version number or any other value used to keep notes in a prescribed sequence.
The date of the note, such as the date the note was officially published, or a due date for the note. The date may be expressed in any of a number of common formats. It may also be a partial date, such as a year, or a year and a month. It may or may not contain a specific time of day.
One or more terms under which this note should appear in an index of the collection. Multiple terms can be placed on separate Index lines within the note, or can be entered as one field by using a semi-colon (‘;’) to end each term entry. A URL to be associated with the term can be placed in parentheses following the term. If the term should reference a specific anchor within the note, then the anchor can be specified by preceding it with the usual pound sign (‘#’).
An excerpt from the note used as a teaser in a list of notes. The teaser may be formatted using Markdown.
The Body of the Note; in other words, an indicator that the document portion of the Note follows. In this case the Field Value is expected on following lines. The Body Field will always be treated as the final field in a Note, to avoid having portions of the document inadvertently treated as Fields.
Note that, if the ‘Body:’ Label is omitted, then Notenik will by default consider any block of text following other fields to constitute the Body of the Note.
The Body of a Note may be formatted using the Markdown syntax.
This is the last modification of the Note, as maintained by the file system (not specified within the contents of the Note, but available as Note metadata).
This is the size of the file, in characters, as maintained by the file system (not specified within the contents of the note, but available as metadata).
Each Collection may be thought of as a Table, with each Note in the Collection treated as a Row, and each Field in the collection represented as a Column, with the Field Labels used as Column Headings.
When considered in this way, each Collection may be Viewed in a grid, Sorted on one or more columns, Filtered using one or more criteria, Output in one or more formats, and used to generate things like web pages through the use of Templates.
In fact, all of this and more can be accomplished through the use of the PSTextMerge application.
The Notenik App looks like this.
The Notenik application can perform the following functions.
A toolbar with multiple buttons appears at the top of the user interface.
Each Collection of Notes is stored within its own folder (aka directory) on disk. Create as many different Collections as you would like. The File menu lets you work with Collections.
Each Note must have a unique title within its Collection. Each note’s file name is based on its title, and each note’s file name must also be unique within its folder.
One of the options on the File menu is to select from a list of recently opened Collections. You can adjust the number of Collections available on the Files tab within the Notenik Preferences. This is also the place where you can specify whether you would like Notenik to open the most recently used Collection used when it starts up, or always open one specific Collection.
Each note contains a number of fields. At its most basic, a note consists of a Title field and a Body field. By default, a Tags field and a Link field will also be included in every Note. Use a Template file to specify other fields to be used within a particular Collection.
Since your Notes are stored as plain text files, in an easy-to-read format, they can easily be edited using any text editor on any device. In fact, from within Notenik, you can select Text Edit Note from the Note menu to have the current Note opened in your preferred text editor.
You are encouraged to use Markdown syntax when creating the Body of your Notes. In fact, there is an option under the Note menu to generate HTML from the Body of a Note, and to either copy it to your system clipboard, in preparation for pasting the HTML somewhere else, or to store it in a file. You can even specify a preferred HTML folder for each of your Collections, in your Collection Preferences.
Use the Tags tab in the main window to see your Notes Collection organized by its Tags. By adding multiple levels to your Tags, you can effectively organize your Notes into an outline.
The “Favorites” tag by default identifies Notes you wish to appear in your favorites file (see the Publish section below). The “Startup” tag identifies Notes whose links you wish to have launched in your favorite Web Browser whenever Notenik launches, (so long as this is requested on the Favorites tab within the Notenik Preferences).
A basic Note consists of a Title, a Tags line, a Link, plus the actual Body of the Note.
However, other fields can be added by providing a template file for a collection, named ‘template.txt’ (or ‘template.md’ if you’d prefer Notenik to use the ‘.md’ file extension for notes in this collection). The template is in the same format as a Note, but with the specification of additional fields. (There’s a command on the File menu that can be used to generate a template, which you can then modify with any text editor.) Notenik will then configure its UI dynamically to handle the fields specified in the template for that collection.
When you create a backup of a Collection, Notenik creates an exact copy of the current folder of Notes, and gives the new folder a name starting with the name of your source folder, and ending with the current date and time.
Additionally, on the Files tab of the Notenik preferences, you can specify whether you want Notenik to backup automatically, or to occasionally (on a weekly basis) prompt you to create a backup. And if you would like Notenik to automatically delete older backups, then you can specify the maximum number of backups to keep for any Collection.
The Folder Sync tab on the Collection preferences allows the user to identify a common folder to which several different Notenik collections can be synced.
Such a common folder could then be conveniently accessed using nvAlt, for example.
Each collection can have a different prefix assigned, and that prefix will then be used to keep the notes from the different collections separately identified within the common folder. The prefix will default to the folder name for the collection, with a trailing ‘s’ removed if one is found, and with a dash added as a separator. A folder name of ‘Bookmarks’, for example, would result in a prefix of ‘Bookmark - ’ being appended to the front of each note as it is stored in the common folder.
The logic for the syncing works as follows.
A sweep of the entire common folder will be performed whenever syncing is first turned on for a collection, and henceforth whenever a collection with syncing already on is opened.
The sweep sync includes the following logic.
For any common folder notes with a matching prefix, where the corresponding note does not already exist within the Notenik collection, the note will be added to the Notenik collection.
For any Notenik notes where a matching nvAlt note is not found, the note will be added to the nvAlt folder.
For any Notenik notes where a matching nvAlt note has been updated more recently than the matching Notenik note, the Notenik note will be updated to match the nvAlt note.
Once folder sync has been turned on for a collection, then every time that Notenik makes an update to any note within that collection, a parallel update will be made to the corresponding note within the common folder.
Notenik allows you to export a Collection of Notes in any of several different formats.
You may filter the notes to be exported, for any of these formats, by adjusting the entries in the Tags Export preferences. You may specify one or more tags to be selected, so that only notes containing those tags will be exported. You may also suppress one or more tags, meaning that exported notes will have those tags removed from the resulting output.
For example, if you have a collection of blog entries stored as a Collection of Notes, and you have multiple blogs to which they are published, you can specify tags for the relevant blogs for each note, and then select only those notes when publishing a particular blog (and suppress the tags for the other blogs).
If you leave the Tags to Select field blank, then all Notes will be exported.
Under the File menu you will find options to Import and Export your Notes.
You can import and export your Notes in this collection from/to a folder in the same Notenik format.
The Notes in this collection will be exported to an XML-based Outline format that can be opened by an app such as OmniOutliner. The Tags in the collection will be used to create the outline.
Note that, for XML formats, the resulting file may contain invalid characters if those are present in your Notes.
Each Note will be represented as one row/line, and each field will be represented in a separate column. This format is suitable for import into MS Excel, for example.
Similar to tab-delimited, but the Title and link are concatenated into a single field, with a ‘#’ character separating the title from the link. Some Microsoft apps can use this format to import each link into a special field that combines the title and the hyperlink into a single field.
Your Notes will be represented in an XML format with each field represented as a separate tag.
Note that, for XML formats, an exported file may contain invalid characters if those are present in your Notes.
When running on a Mac, if you choose this option, and then select your Applications folder, Notenik will import one Note for each application found in the folder. If duplicates are found then the existing notes will be updated rather than adding new notes. You will get the best results by first specifying a ‘template.txt’ file for the Collection in the following format.
Title: The unique title for this note Tags: One or more tags, separated by commas Link: http://anyurl.com Date: 2017-01-22 Seq: Rev Letter or Version Number Minimum System Version: Body: The body of the note
After the import, you can use the Tags field to organize the applications in any way you like, and clicking on the Link field will launch the application.
The publish option allows you to easily publish your Notes in a variety of useful formats. For example, you can easily publish your notes as a series of web pages.
To begin the publication process, select the Publish command from the File menu.
You will then see a window with the following fields available to you.
Publish to: You may use the Browse button above and to the right to select a folder on your computer to which you wish to publish your Notes. You may also enter or modify the path directly in the text box. When modifying this field, you will be prompted to specify whether you wish to update the existing publication location, or add a new one. By specifying that you wish to add a new one, you may create multiple publications, and then later select the publication of interest by using the drop-down arrow to the right of this field.
Equivalent URL: If the folder to which you are publishing will be addressable from the World Wide Web, then enter its Web address here.
Templates: This is the address of a folder containing one or more publishing templates. This will default to the location of the templates provided along with the application executable. You may use the Browse button above and to the right to pick a different location, if you have your own templates you wish to use for publishing.
Select: Use the drop-down list to select the template you wish to use.
Apply: Press this button to apply the selected template. This will copy the contents of the template folder to the location specified above as the Publish to location.
Publish Script: Specify the location of the script to be used. The PSTextMerge templating system is the primary scripting language used for publishing. A PSTextMerge script will usually end with a ‘.tcz’ file extension.
Publish when: You may specify publication ‘On Close’ (whenever you Quit the application or close a Collection), or ‘On Demand’.
Publish Now: Press this button to publish to the currently displayed location. Note that, if you’ve specified ‘On Demand’, then this is the only time that publication will occur.
View: Select the local file location or the equivalent URL location.
View Now: Press this button to view the resulting Web site in your Web browser.
You can easily publish a single web page containing your favorite links arranged in a series of columns and rows. Use the Favorites tab on the Notenik preferences to specify the number of columns to appear, and the maximum number of rows to include in a single column.
The Reports menu allows you to select from a list of reports, and then generate the report of your choice. Reports are generally HTML web pages generated from PSTextMerge scripts.
Any number of report scripts and templates may be placed within a folder named ‘reports’ that appears inside each folder of notes.
If a ‘reports’ folder has not yet been created and populated for a particular Collection, then a set of standard reports will be loaded from the application’s resources folder.
Reports are generally a simpler and more straightforward approach to the Publish function described above.
Under the File menu you’ll find an option to Purge closed notes. Notes with a Status of Canceled or Closed will be purged. You may choose to discard the purged notes, or to copy them to an archive folder.
The following operations are available from the Collection menu.
Search for any text string using the Find box in the Toolbar.
Enter a replacement value for a search string and perform a mass replace operation.
Replace one Tag with another.
Flatten the levels of all your Tags, making each level a separate Tag.
Change all your tags to lower case letters.
Validate all the links in your collection.
The Display tab in the Notenik preferences allows you to change the font, font size, and foreground and background colors used for the Display of each Note.
The Notenik General preferences contain a number of options for modifying the program’s look and feel. Feel free to experiment with these to find your favorite configuration. Some options may require you to quit and re-launch Notenik before the changes will take effect.
SplitPane: Horizontal Split?: Check the box to have the List and Tags appear on the left of the main screen, rather than the top.
Deletion: Confirm Deletes?: Check the box to have a confirmation dialog shown whenever you attempt to delete the selected Note.
Software Updates: Check Automatically?: Check the box to have Notenik check for newer versions whenever it launches.
Check Now: Click this button to check for a new version immediately.
File Chooser: If running on a Mac, you may wish to select AWT rather than Swing, to make your Open and Save dialogs appear more Mac-like. However, Swing dialogs may still appear to handle options that can’t be handled by the native AWT chooser.
Look and Feel: Select from one of the available options to change the overall look and feel of the application.
Menu Location: If running on a Mac, you may wish to have the menus appear at the top of the screen, rather than at the top of the window.
Notenik is free and open source software.
Notenik Software, Specifications and Documentation are all Copyright 2009 - 2016 by Herb Bowie.
Licensed under the Apache License, Version 2.0 (the “License”); you may not use Notenik except in compliance with the License. You may obtain a copy of the License at www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Source code for the Notenik app is available at github.com/hbowie/notenik.
Java classes for Notenik data access are available at github.com/hbowie/psdatalib in the ‘com.powersurgepub.psdatalib.notenik’ package.
The Notenik app can be downloaded in either of two forms. The first is packaged as a typical Mac App, and can only be run on macOS (formerly known as OS X). The second contains a folder full of jar files, and can be run on pretty much any operating system. Double-click on the appropriate jar file to launch the corresponding app.
Because Notenik may be run on multiple platforms, it may look slightly different on different operating systems, and will obey slightly different conventions (using the CMD key on a Mac, vs. an ALT key on a PC, for example).
Note that you may receive various warnings that the software is written in Java and/or that the application code has not been signed. So long as you have downloaded the software from Notenik.com or PowerSurgePub.com then you should be safe to ignore such warnings and proceed to happily use the software.
If you see a message saying you need Java, then you can visit Java.com to download a recent version for most operating systems.