Using Readwise’s highlight_id as a single source of truth in Obsidian

  • I can run the export command as many times as I want in my Obsidian vault and the highlight will always have the same ID.
Readwise configuration for export to Obsidian
Example of Readwise exported highlights in Obsidian
- {{ highlight_text }}{% if highlight_location and highlight_location_url %} ([{{highlight_location}}]({{highlight_location_url}})){% elif highlight_location %} ({{highlight_location}}){% endif %} ^rw{{highlight_id}}{% if highlight_tags %}
- Tags: {% for tag in highlight_tags %}[[{{tag}}]] {% endfor %}{% endif %}{% if highlight_note %}
- Note: {{ highlight_note }}{% endif %}
  • The next 2 characters are rw. I choose to export the rw as a prefix for the identifier as a way of telling myself that this block reference originates with Readwise, but it is not necessary, you don’t have to include it if you don’t want it.
  • Then the highlight_id field from readwise ^rw{{highlight_id}}.
- The checklist cannot be lengthy. A rule of thumb some use is to keep it to between five and nine items, which is the limit of working memory. Boorman didn’t think one had to be religious on this point. [Loc 1831](https://readwise.io/open/75317236) ^rw75317236
  • The Readwise ID does not follow a sequential order nor is it guaranteed to follow some pattern.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store