Closed ohare93 closed 4 years ago
Hey! Thanks for the report.
I realise I made a mistake when updating element 105 from Hahnium to Dubnium. Anki compares notes based on a guid
, which has to be conserved between updates. I failed to set the correct guid
for element 105. I will fix this ASAP with a new commit and a release, but I need to figure a way to remove the duplicate.
Element 106 also as a guid
set in the src/data.json
file, which is imported into the sqlite3
database that you can browse by opening the .apkg
file with a zip software. I do not know why Anki shows the Note ID field with a different value. I will explore this problem over the end of the week.
Ok so commit 7bde7bf solves this issue partially. I will link to this comment as an update guide from version v2.1
.
If you update from v2.1
to any later version, you need to manually remove the cards with Note ID 1484952780480
. This cards are duplicates for Dubnium cards; so you will find them near Element 105 in the Anki cards browser. To see the Note ID of a card in the browser, right-click on a card and select Info.
I spent more time on this issue today. As far as I can tell, the guid
is the only value that is used to determine if imported cards are news or updates. Note ID and Card ID are internal to each Anki installation:
.pkg
file, have to be consistent from cards to notes (this is managed on creation through genanki
scripts)Thanks again to @ohare93 for reporting the issue. The guid
has been fixed before, I think no more changes are required.
Thanks for the deck, mate. Glad you got it over to a Github repo! 👍
I pulled the latest version, as you suggested. You mentioned that 105 has changed from Hahnium to Dubnium, however my local card did not change, instead I got a duplicate! 😱
Looking at the card info of each (Select the card in the Browser, then click Cards -> Info) gives this for each card.
Old
New
From this it's easy to see that the Note and Card IDs are not generated as proper Guids. The same is true for the new element 106
What I believe is the solution to this:
Thanks again for the deck mate 👍