CSV Export swaps Tags and Collections columns

When I do a CSV export, my Tags and Collections columns are swapped.

Of course, the REAL solution I'd like to see is a bit feature-ish. I'd like to see the CSV export just run the same bit of code the tab-delimited one does, only with commas. Right now it's just a subset(*) of the tab-delimited one with slightly different column names. Yes, there's a couple of complications because now you have to escape commas in the data. But it's nothing a billion programmers haven't already figured out in the past.

If you used the same code base, you (mostly) wouldn't have to worry about CSV and tab having their own bugs, and it would be more expected behavior for the user. Right now, looking at the export page you'd think it's just two formats for the same exports. Yet they are completely different exports. If I were a new user, I might just try the CSV, see it spit out only a paltry few fields and ditch this whole LT thing because it was so hard to get your data back out once you put it in.

* Well, CSV has Subjects and tab-delimited doesn't. I think that's the only non-subset case, though.

Vote on http://www.librarything.com/topic/101108 ?

I think you might want polls in that RSI thread.

deferred

I have just reproduced this bug today and confirm that it still exists.

FYI, deferred just (generally) means it's a known bug, but they're not fixing it anytime soon. In this case, it's because Tim plans a complete re-write of the exporting (see the link above). That rewrite would come with all new bugs. ;)

I would love to see all these catalog sites come together and create an API that they all can use.

edit: I don't think it'll happen though. We can't even get different softwares to use the RSS API all on the same page.

I also just reproduced today - still exists

Fixed, apparently.

http://www.librarything.com/topic/141290

Marking!