The documentation is a bit blurry about this, but leeches are represented in Anki as tags, which are properties of notes. So if one card of your note is difficult, the others aren’t, once it becomes a leech, all the cards are tagged or even suspended, while only one deserves it.
I understand why - Anki does not provide a mechanism to tag cards, you can only tag notes - but the situation as it is makes the leech tag useless for me. I suggest to introduce the possibility to tag individual cards.
When this counter reaches 8, Anki tags the note as a leech and suspends the card.
Leeches - Anki Manual
Yes, the entire note will be tagged, but if you have “Suspend” turned on for Leeches, only that card should be suspended.
Counterpoint:
I think it makes sense to apply the “Leech” designation at the Note level. One of the main techniques for dealing with a leech – editing it – is an action you’re going to take on the note as a whole, not a specific card.
OK, I don’t have my Leeches suspended. I hate cards being auto-suspended, that’s just intrusive.
It’s logical to apply the “Leech” designation to the object that caused it, not to the parent object of it. When I see a Leech card, by browsing it I am immediately at a place where I can edit the fields of the note.
My main technique for dealing with a Leech is adding additional cards. This may be further subcards of the note (triggered by filling out fields of the cards e.g. to provide example sentences for this word), or further notes which somehow relate to that card, so I generate chunks of context.
I came to report the same thing. I find that leech “tagging” can be useful, but the implementation as it is now is easy but, I concur, unhelpful, as well as departing from the documented motivation. The documentation is talking about “cards” all the way up to the point where it mentions how Anki deals with them — tagging a note.
The remedy can be just as easy; already now flags are card- and not note-property. Anki could implement a special reserved “leech flag”.
Sure, but you could say that this is only true because you cannot edit a card, only a note ![]()
Another technique —I use it— is to create more notes to tackle the question the leech (card) asks from a different angle. But if I filter on leeches I get a “list of notes” and not a “list of cards”, so I cannot immediately know which one of any note’s card is the problematic one.
Adding prop:lapses>=8 to your search will solve that.
Leeches in general: I also usually add more notes when I have a leech or a leech-in-the-making. A common reason for my leeches is that they have multiple failure points. That means I may fail a card twice as much for two different reasons, resulting in a leech.
For flagging cards: I use the following add-on and renamed the 7th-flag to “Purple (Leech)” for clarity. I can then search leech cards or notes with flag:7.
Regarding the suggestion itself: I am not convinced by the argument for why tagging a note is preferable to flagging a card. Flagging a card, unlike tagging a note, loses no information and creates no superfluous ones. Besides, a note is not meant to contain review history, which the leech status reflects. Finally, the Anki software cannot and should not determine if the note itself needs editing or even if siblings of a leech require addressing.
That said, if the Anki team considers this feature more trouble than it is worth, I would be perfectly content with that argument.
When I mentioned flags above, I immediately imagined Shige making an add-on to apply the idea. I did not realize he had been many a step ahead of me ![]()
The documentation makes no such argument. I agree that what has been mentioned on this thread doesn’t seem to try to be persuasive, either. I suspect it’s plain conservatism. I’d imagine it to be unclear how to deal with backward compatibility, if a new Anki version changes how leeches are implemented. The leech implementation is a leech in a figurative sense too, it seems..
I guess that it might be a major change to make leeches properties of cards rather than notes, and that is probably the reason why they are misplaced on the notes currently. You would have to introduce the concept of tagging a card instead of a note, and - apart from the leech tag - introduce a load of functionality to administer such card-level-tags.