suggestion : bury cards that have been added in close proximity

[thiswillbeyourgithub]

Hi, great addon btw,

I can sometimes have to enter 5 different cards on the same disease but with the phrasing so different that your plugin cannot pick them up as cousins.

So I thought about it and thought it would be a nice feature to enable to automatically bury the cards that have been added just before and just after some card.

Say I add five cards in a row : 1 2 3 4 5

If in my review queue I see card #3 then your addon would automatically consider as cousin the cards 2 and 4, or 1 2 4 and 5 depending on user settings.

This would be an interesting way to reduce a daily workload in a smart manner.

What do you think?

edit : related post on the anki forum : https://forums.ankiweb.net/t/bury-review-cards-created-next-to-each-other/8930

[thiswillbeyourgithub]

if you are willing to give me pointers I could maybe code it myself. That would be a good learning experience for me too!

[AlexRiina]

Interesting idea. It'd definitely be difficult with the current implementation of this plugin because I've primarily architected for field vs field comparisons. I can think of a few ways to kind of hack something like this together:

• add an extra field for the topic (e.g. disease name) that doesn't get displayed in any card and make a rule based on that
• tag the cards with something like relation_diabetes_retinopathy and use https://github.com/Arthur-Milchior/anki-relation to suppress the cards (pretty sure that plugin conflicts with this one so if you like this one still probably not a good option)

I can see a few ways something like this could go wrong using the timestamp like if you import a deck, it might suppress the entire rest of the deck every time you rehearse.

[thiswillbeyourgithub]

I can see a few ways something like this could go wrong using the timestamp like if you import a deck, it might suppress the entire rest of the deck every time you rehearse.

Hence #25 , the failsafe would ensure we would not loose that many cards. It seems pretty easy to make it not trigger when there are suddendly more than say 3 cards each second that have been created don't you think ?

So I still think that using timestamps is the way to go, as "tagging" all your cards by notion really cannot work at large volume of diverse cards IMO.

What do you think?