Importing my collection (csv file): wrong card versioning

 avatar
peyrandil avatarpeyrandil
{"ops":[{"insert":"Hello,\nFirst, I guess this thread is a good occasion to thank you for this incredible tool :)\nI used to manage my decks with it, but recently considered importing my collection, from some less-known tool I was using - that let me export it with the following infos:\nquantity"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"card name"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"set code"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"foil status"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"multiverse ID"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"condition"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"language"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"I managed to arrange them in a CSV file. I even manually added the \"// xxxx\" additional information in names of all double-sided cards ^^\nThe import was successful (I asked to skip the import in case of ambiguous entry, but none was signalled).\nAnd then, looking at my Archidekt collection, I realised most versions were wrong :(.\nSo I deleted the entire collection and tried with only 2 lines:\n1,\"Otawara, Soaring City\",CNEO,Normal,552124,FR,Lightly Played\n1,\"Otawara, Soaring City\",NEO,Normal,548584,FR,Lightly Played\nAnd even so, in Archidekt, I have the same card twice, the #271 NEO Otawara.\nThere are thousands of such gaps in the total import of my collection and I don't want to adjust every version manually :)\nAm I missing something?\nAgain, thanks for the good work :)\n"}]}
0
 avatar
{"ops":[{"insert":"It'll be tough to tell what's going on without more specific examples. But going off of the "},{"insert":{"card-link":"Otawara, Soaring City"}},{"insert":", we don't have a set code of CNEO, so that wouldn't be found. As for the NEO printing, we don't actually use the multiverse ID to look up cards since it's a pretty inconsistent identifier. Too many cards just aren't given multiverse IDs. So that one is likely being flagged as ambiguous since there's multiple Otawara,Soaring City cards from NEO.\n\nThe thing with MTG data is that it's kinda the wild west. There isn't really a great official source of specific card identifying data since WotC in very inconsistent with providing it. Archidekt (and many other online MTG applications) use scryfall data as their single source of truth which helps immensly. But as I'm sure you can imagine, for sites/ applications that don't use scryfall data, it can be a challenge to align a lot of the specifics (set codes/ names, collector numbers, the formatting for certain card names, etc). \n\nI'm not sure where your info came from, but the CSV importer will try to do it's best to match cards for you, but in the event of a card not matching, that's why we tag them as ambiguous and take our best guess. If you have the option from wherever your exporting from, to export with a scryfall ID, that'll be the most consistent. If you're just entering stuff by hand into an excel sheet, it'd be a tough call on how to streamline that. I think at that point I'd probably imort what I can, filter and delete anything ambiguous, then input those manually.\n\nI'm sorry, I wish I had more of a silver bullet solution for you. Unfortuantely when dealing with large data sets like this, sometimes manual intervention is the only way to clean up the input data. If you give me a larger sample of the file, I might be able to come up with a few ideas, but as mentioned, that'll depend on what the input data looks like.\n"}]}
0
 avatar
peyrandil avatarpeyrandil
{"ops":[{"insert":"Thanks Michael for the fast and detailed answer.\n\nI'm totally OK with the fact that some manual adjustments are required to have a big import completed :).\n\nI also think I misred the disclaimer (orange frame about ambiguous upload), and was thinking that the multiverse ID was OK, while it's the scryfall ID you use.\n\nStill, based on this disclaimer, and as I hadn't chosen the \"unsure tag\" feature, the import should'nt have been announced as successful, should it? It clearly was ambiguous, with hundreds if not thousands of gaps versus my actual collection, and I could have detected it much later.\n\nAnyway, my previous tool doesn't use scryfall ID but its database does contain collector numbers, even if they're not part of the collection export. I managed to automatically extract them and add them to my CSV, then tested the import again with the collector numbers, and There are some errors, but 99% is OK, and looks fine this time :)\n\n"}]}
0
Support us on Patreon to remove ads