"the automation was nice, and efficient, but it was also detached and remote. The notes felt distant; I frequently never even reviewed them."

"First, I read the book and mark it up along the way. Second, I created a source note for the book, that acts as a kind of map of content (MOC) for that book. Third, I review the notes I took, decide which are worth capturing as a separate linked not, which are worth noting in the source MOC, and which are safe to ignore."

"I don’t go and create my note in Obsidian right then and there. Experimentation has taught me that if I wait until I finish, some of the passages I marked aren’t really worth capturing."

"When I finish reading a book, I do a couple of things. I update Goodreads. I update my list of books I’ve read since 1996. And then, I go back to the book and review the flags I’ve left."

"If I don’t think the note is worth keeping or recording, I’ll pull out the flag. Of course, my underlined passages and notes are still there, but the flag is there to tell me if I should collect that note in Obsidian. Whatever flags remain mark things I want to capture."

"I have a top level “Reading” folder in Obsidian with two sub-folders: Sources and Commonplace. Source notes go into my Sources folder. I have a template for Source notes to ensure there is consistency in their formatting and content."

"Once I’ve got my source note, and I’ve whittled the flags down to those that I want to keep, I begin adding my notes to Obsidian. I do this manually, reading from the highlighted passages, typing them into a note in Obsidian, and then adding any necessary meta-data."

"My initial idea was that I’d save myself a ton of time by automating as much of the process as possible. But I found that I didn’t really absorb my notes when doing that. It was only when I was culling, curating, and typing in my notes manually that they began to resonate with me."

"instead of using the Post-It flags, I use Kindle bookmarks to mark those notes that I want to keep. This has worked much better for me."

"For skimming search results, I’ve found that a useful title for a note is key."

"Between paper, Ebooks, and audiobooks, the toughest challenge is gathering notes for audio books."

"This is a lesson I learned from the automation I originally set up: the automation was nice, and efficient, but it was also detached and remote."

"There are three things that I do when reading a book to get my notes into Obsidian."

"First, I read the book and mark it up along the way."

"Second, I created a source note for the book, that acts as a kind of map of content (MOC) for that book."

"Third, I review the notes I took, decide which are worth capturing as a separate linked not, which are worth noting in the source MOC, and which are safe to ignore."

"To help find the places I markup after I’m finished, I keep spare sets of Post-It Flags handy."

"Next, I create a source note in Obsidian. A source note is a note that represents the book I am reading."

"I have a top level “Reading” folder in Obsidian with two sub-folders: Sources and Commonplace."

"Capturing a passage in its own separate note and then link to that note from the source note (MOC) using a transcluded link so that the full note will show up in preview mode."

"Sometimes, I just want to capture a thought that isn’t really a separate note itself."

"My initial idea was that I’d save myself a ton of time by automating as much of the process as possible. But I found that I didn’t really absorb my notes when doing that."

"I also found that I was defeating myself by automating the titles of the reading notes with UIDs instead of readable titles."