What Are Fields in Notenik and How Do They Help Organize Notes?

Fields are the structured data slots that make up every note in Notenik. Instead of treating a note as one undifferentiated block of text, Notenik splits each note into named fields — a Title, a Body, and any others you choose to add, such as Tags, Link, Date, Seq, or Author. Because those fields are real, separate values, you can sort and filter a whole collection by any of them. That is the core mechanism behind Notenik's organization: structure comes from fields, and you decide which fields each collection uses.

How a note is built from fields

Every Notenik note has at least two fields:

• Title — the note's name.
• Body — the main text, written in Markdown.

From there you add whatever fields fit the kind of notes you're keeping. The site lists several examples:

Each field also has a type, so a Date field behaves like a date and a Seq field behaves like a number rather than plain text. That distinction matters when you sort: a date field sorts chronologically, not alphabetically.

One collection, one field set

A Notenik collection is just a folder of notes, and each collection can use a different set of fields. This is the part that makes fields useful rather than rigid.

If you keep a reading list, you might define fields for Author, Date, and Link. If you keep a project log in a separate folder, you might use Date, Seq, and Tags instead. The two collections don't have to share a schema, so you aren't forced into one universal note format across everything you store.

Sorting and filtering by field

Once notes carry fields, you can sort your collection using any of those fields. A collection of quotations sorted by Author groups all the quotes from one person together; the same collection sorted by Date gives you a chronological view. Filtering works on the same values, so a Tags field lets you narrow a collection down to one topic without moving or duplicating notes.

The practical result: the same set of notes can be reorganized on demand by changing which field you sort or filter on, rather than by physically rearranging files.

Why this matters for organization

Fields shift the work of organizing from "where do I file this?" to "what do I record about this?" You decide up front what attributes a collection's notes should have, fill those in as you write, and then let sorting and filtering produce the views you need. Because the notes are stored as plain text files in folders, that structure stays readable and portable outside the app as well.

If you want to see how a given collection's fields are defined, the Notenik Knowledge Base — itself stored as a Notenik collection — is reachable from the Help menu inside the app.