Is there a way to avoid importing duplicates when regenerating identical/updated cards? about anki-apkg-export HOT 6 CLOSED

I think this is the only solution here. But I'm not sure how it will play for nested decks as in Anki we can create them by using :: separator: Parent::child.

from anki-apkg-export.

Just an idea: Anki requires the front side of a card to be unique. It looks like it's using it as ID. Are you sire your front sides are completely identical in all imports?

from anki-apkg-export.

@amorriscode big thanks for the patch, I've just released v4.0.3

from anki-apkg-export.

@ewnd9 I realized this doesn't actually resolve the issue completely. While it does update duplicate cards that get added, if the deck was previously created, it does not get edited.

I guess we should be able to load a deck and then add/update cards.

from anki-apkg-export.

@amorriscode How could we load a deck before updating as now its guid is generated based on unique value (Date.now())?

from anki-apkg-export.

Perhaps the deck could have an ID based off of the deck name instead of using Date.now(). I will try to do this locally and see how it goes.

from anki-apkg-export.