Knowledge Processing Pipelines

As another example of the flexibility of this process, I’m currently processing a set of some 15 or so articles from a website as a single source, since they all revolve around teaching a particular set of closely-related techniques.

It didn’t start out this way. I started by processing a single article but quickly realized that I wanted to process many of the articles. I initially planned to create a source per article but the more I read (and flipped through articles on the site to find out what they were like) I realized creating 15+ “sources” and trying to interlink the various literature notes (across folders) would be cumbersome, so I just kept taking notes in the original source note as I clicked through to each article. To keep things straight I’m attaching links to the specific articles in each applicable section of the notes.

Once I’m done reviewing all the articles and producing the outline in this single note I’ll begin chunking them together in meaningful themes and groups that work for me in my contexts and then convert those into phrase-based literature notes capturing the core principles and processes.

Then I’ll rename the source note to something more meaningful and write a statement at the top explaining that it is syntopically derived from multiple source articles.

This works because the fundamental workflow is simple enough to flex to accommodate it, while still providing a strong framework in which to perform the work.

3 Likes