{"ops":[{"insert":"I'm fairly new so this may be something I'm completely overlooking, but it would be nice when you add new cards into your collection that it automatically added it to a listing of the same card if there is one. I've been switching my collection over from Manabox slowly, 100 cards at a time, to make sure I have each and every one correctly scanned and set/number/etc correct and every time I upload a csv file that contains a card that was on another csv file (I.E. Satyr Wayfinder) it creates a whole new listing for the same card even though I already have one in my collection. I shouldn't have to manually delete all the other listings and add the cards up onto one, it should be able to condense the 3 separate listings I have of 1 card each into 1 listing of 3 cards. I think this would make an excellent QoL for the collection to make it a little more easy to look through.\n"}]}
1
{"ops":[{"insert":"Assuming you're importing cards using the CSV importer, then you're not missing anything. We used to offer a way to import CSVs and update existing matching records, but there were some issues with it. \n\nFor one, it was "},{"attributes":{"italic":true,"bold":true},"insert":"slow"},{"insert":", needing to check every card to see if another card existed before running the import made certain imports take too long to process (I'm talking like 20k - 30k unique records). While some would be fine attempting to do a 30 minute upload for a collection of that size, running those kinds of queries on our prod database would slow down the site for everyone else. \n\nBeyond just the scaling factors of it, the experience wasn't great due to how finicky the matching could be You'd end up with records that some were merged, others weren't it as a whole thing. You can still see this while importing cards from data sources that don't use scryfall data 1:1. We attempt to match things as well as we can, but more often than not (again, depending on the data source), you'll end up with some ambiguous cards.\n\nWhat this turned into was users not using the matching & squishing features anyway because if you're coming from a data source that doesn't match ours (aka, not using scryfall data), you wouldn't trust it to update your entire collection. So what users would do is exactly what you're suggesting, exporting their collection, reconciling it themselves, then reimporting it. \n\nIt's because of all of that, that I removed the merging feature on importing. \n\nAll that said, I do want to reimplement a merging feature in the collection that exists separately from import. One with a better UI that can more clearly spell out what cards are being merged and how. It's just something that's gotten backburned as I'm currently rewriting the collection page to use a more modern UI, support stuff like dynamic columns, etc. So it might be a bit before we see this feature.\n\nFor now the intended behavior is for imports to be treated as only imports. It helps keep not only the UI more organized for users, but it allows me to keep the code more maintained and snappy as well. \n\nIf the intent is to add cards one by one, there's already a way to add cards while updating existing, it just can't be done in bulk.\n\nAll in all, your idea is a good one. But we've tried it, and ended up with a handful of logistical hurdles that make it challenging to support.\n"}]}
1