cardsman {"ops":[{"insert":"Hi, \n\nfrom time to time I export my collection from Manabox and upload it to Archidekt. Everytime I do that I have to fully delete my current collection. (Unless im missing something). I would appreciate the option to update my collection by creating a read diff between my current collection on Archidekt and the CSV file im providing. Thank you!\n"}]}
0
{"ops":[{"insert":"I've considered this in the past, but it's a bit harder than you'd expect unfortunately. \n\nSo the only way to do it is a diff as you suggest, as in general we don't build UIs that update things without showing the user what's about to change. But there therein lies the issue. If someone attempts to upload a 1000 file CSV, we're now having to show user's a 1000 file diff. 1000 "},{"attributes":{"italic":true},"insert":"might "},{"insert":"be doable (even this is a stretch I think since we'd have to load an pull down 1000 collection records at once), but 5000, 10k, etc, no way. \n\nWe could limit it, but then we're building features that actively punish the poweryest of users, which generally I'm not a fan of. \n"}]}
1
{"ops":[{"insert":"thanks for your response and the explanation. what if you make an exception and e.g. offer a checkmark \"update my collection\" in the collection interface, with an explainer text \"Updating the collection only adds cards that werent previously in your collection\"? i understand its important to have design rules but does one have to follow them 100% of the time? Especially this decision to show all changes will then hamstring any futher development you would want to make to the collection tools.\n\nbut to be fair the current way also works with little overhead. its more that my collection tracking isnt clean and i sometimes add singular cards manually and i never remember if my manabox csv actually has all the cards :D.\n"}]}
Edited 8/19/2026, 3:33:01 PM
0