How Octarine works for researchers and long-form writers

Research and long-form writing place different demands on the same material. During collection, you need fast capture and enough provenance to find the source again. During synthesis, you need to see relationships and disagreements. During drafting, you need a quiet document that does not hide the evidence in a different system.

Octarine can hold those stages in one workspace without turning the workspace into an Octarine-only database. Notes are Markdown files, attachments live with the workspace, and organization can be expressed through folders, links, tags, and YAML properties.

Start with the files you want to keep

Choose a workspace folder that can contain the whole project. A straightforward layout might look like this:

Book/
  Drafts/
  Sources/
  Interviews/
  Claims/
  Attachments/

The names are less important than whether they still make sense outside the app. Octarine can open an existing Markdown folder without moving or renaming it. It watches external changes as well, so a script, Git client, or another editor can participate in the workflow.

Use YAML properties for facts you expect to filter repeatedly. A source note might have author, published, source_type, and status. A draft might have stage and deadline. Do not convert every observation into metadata. If you never sort or filter by a field, it is probably clearer in the prose.

Separate evidence from your interpretation

Create one note per source when you need a durable record. Put the source URL, bibliographic details, and access date near the top. Distinguish direct excerpts from your own summary. Copyright and research integrity are easier to manage when a later reader can tell which words came from where.

Then create synthesis notes around questions or claims rather than around the source list. A note named “Why adoption slowed after 2024” can link to several source notes and record how they agree or conflict. Backlinks reveal which drafts or claim notes depend on a source. Workspace search helps when you remember the language but not the location.

Views can turn consistent properties into a table or Kanban board. That is useful for questions such as “Which interviews still need consent?” or “Which claims have only one supporting source?” The underlying notes remain Markdown; the view is another way to inspect them.

Move from notes to a draft without a copy-and-paste maze

Keep a project outline close to the draft and link each section to the relevant synthesis notes. Draft in a long Markdown document if that matches the final form, or use one file per chapter when the project is easier to navigate that way. Because the documents are ordinary files, you can use Git to review changes or hand a .md file to another tool for conversion.

The Writing Assistant can work beside the current note, selected text, or notes and folders added with @ mentions. It can help outline material, identify a missing counterargument, or tighten a paragraph. Inserting a suggestion is safer than replacing the original when you want to compare versions. The Writing Assistant documentation describes the exact context controls.

AI is optional and requires Pro or a trial. With a cloud provider, the prompt and included context are sent to that provider. For sensitive or unpublished research, use a local provider, exclude private folders from Ask Octarine, or do not use AI on that material.

What Octarine does not replace

Octarine is not a formal reference manager. It does not attempt to replace Zotero’s catalog, citation styles, browser capture, or word-processor integration. Keep a citation manager as the authority for bibliographic records when a journal, university, or publisher requires exact citation output.

It is also not a specialist qualitative-analysis package, collaborative LaTeX environment, or tracked-changes workflow. A research team that needs coded transcripts, granular permissions, simultaneous editing, or an audit trail may need a dedicated system. Octarine is strongest as the individual researcher’s thinking and drafting layer around those tools.

PDFs and other attachments can live in the workspace, but a reader whose work depends on high-volume PDF annotation should test that part of the workflow carefully. The portable center of Octarine is the Markdown note, not a proprietary annotation database.

Back up research as a project, not a handful of drafts

Copy the entire workspace, including hidden .octarine, .attachments, .files, and .templates directories. Octarine’s data-storage guide explains why a complete backup includes more than visible notes. Built-in Git Sync can provide version history; cloud-folder sync and a separate local backup are other options.

Before committing a project, run a representative test. Bring in one long draft, ten source notes, several attachments, and the metadata you actually use. Search for a claim, follow it back to a source, change a file outside Octarine, and restore the folder from backup. That exercise tells you more than a feature matrix about whether the workspace can carry years of research.