Skip to main content
  1. Posts/

Omnivore Read Later Workflow

·1 min
Personal Knowledge Management - This article is part of a series.
Part 3: This Article

This is a series of blog posts showcasing how I have my personal knowledge management (PKM) system set up, the changes I’ve made, and best practices I’ve implemented.

Omnivore is a read-later app that integrates well with Obsidian via the Omnivore plugin. Here’s how I have it set up.

Plugin Settings

Frontmatter

I’ll get to why I use these frontmatter keys later, for now each note gets imported with these properties (plus the necessary id)

Image 1

Article Template

Imports only the important stuffs.

Image 2

Date Format

Consistent with other plugins and notes in my vault: YYYY-MM-DD @ h:mm a

Extras

  • Filter: Sync all items
  • Sync on startup: enabled
  • Filename: {{title}}
  • Highlight order: the location of highlights in the article

Personalization

Now, about those frontmatter properties…

```dataview
TABLE without id file.link AS articles, state, omnivore_url, date_read AS timestamp
FROM "60 Resources/omnivore"
WHERE contains(state, "INBOX") OR contains(state, "READING")
```

The Dataview query above on shows all notes with the INBOX or READING states, the filename (i.e. title), and a link to read the article in Omnivore.

Image 3

That’s it.

Personal Knowledge Management - This article is part of a series.
Part 3: This Article