Because paragraphs are so variable, my Project Gutenberg import script makes 25-line cards with a 5-line overlap between adjacent cards (for context). It also blanks out a random word on the 15th line as a cloze deletion test, to ensure I have some understanding of what’s going on.
Brilliant strategy.
This is still a fairly new strategy for me, so I don’t yet know how many parallel threads I can keep straight at the same time— So far, it doesn’t feel like I’m anywhere near the limit.
This idea was actually born to combat review starvation: I haven’t been very active at adding new cards lately, and there was a risk that my daily review count would hit 0 for long enough that I’d stop checking regularly— I needed a source for lots of interesting but low-priority cards to keep the pump primed.
The original paper on cloze deletion [1] uses them as a readability measure: Readers are given an unfamiliar text with blanks and are asked to guess the omitted words; the percentage correct is then a measure of the text’s quality rather than the reader’s knowledge.
Instead of a knowledge quiz, which is how clozes are usually treated in the SRS world, this is an automated reading comprehension test— Just the thing for capturing the intangible benefits of reading literature. In theory, as you become more familiar with the book’s style and subject matter, you should be able to pass the first review of an unseen passage most of the time.
I settled on 25 lines of text per card with one omitted word about 2/3 through the passage. Successive cards contain some duplicated lines (5) to provide a sense of continuity between the cards, which are presented in a disjoint manner.
I import each book into its own deck set to show 1 new card per day (in the order added)- I want whatever mental connections are necessary to understand the next passage to end up in long-term rather than short-term memory. The reviews give me an opportunity to spot details that seemed unimportant on a first reading but that foreshadow something that happens later.
Beyond that, it’s driven by Anki’s normal scheduling algorithm; these are subdecks of my general-review deck, so Anki will autumatically mix the new cards and reviews with any other reviews I have due.
Most of the books I’ve imported are 300-400 cards, so it’ll take about a year to work through each of them. I wouldn’t be surprised if I end up doubling the number of books I’m reading at once, which would bring the average to around 1/month.
[1] https://www.gwern.net/docs/psychology/writing/1953-taylor.pd...
I did the first one manually. In addition to being a lot of work, there were major spoiler hazards— If I wasn’t already familiar with the general shape of the plot, the process would have revealed secrets too early.
The script will ask you for a text file to process and the pop up a Tkinter window with a single button. Each time you press the button, it copies the next card's body text to the clipboard, ready to be pasted into Anki's Add window.
The text file needs to be already split into reasonable-length lines, like the ones you get from gutenberg.org
Card template: https://pastebin.com/BFJxW1jC
Cloze splitting script: https://pastebin.com/4Jek0G7u
My strategy for this was to dump the entire text of some good literature into Anki decks that give me one new paragraph per day. The steady drip of unseen material removes the stigma of pressing the “again” button and gives me a small reward of story progression from each session.
In a separate deck, I use cloze deletion on sheet music to help learn songs. That deck only gets reviewed by actively playing music, which is an inherently enjoyable activity on its own.