Drastic change of the exported data and column headers

[Mazata]

Hi,
Back in October 24 when I last exported a playlist, I had the following columns in the export.
I had the artist URI, the album cover URI, the track URI (that last one can be easily built from the trackID I'll admit).
I was wondering if you could bring these columns back or what the rational was behind remove them in the first place.
Cheers

[pavelkomarov]

Those columns didn't seem particularly useful to me, and they often held a lot of repeats, so I removed them for the sake of schema simplicity. What's your use case?

[pavelkomarov]

I have considered bringing back the full song URI instead of just the track IDs, since you can copy and paste the URIs over to a playlist in the Spotify desktop app, and it'll know what to do with them. It's just a lot of repetitive "spotify:track:" in that column, which I don't love, but maybe better than making users prepend a string if they want that functionality, for those who don't script.

[pavelkomarov]

Okay, done in caa88a6, and I've added a discussion item to help users #84

[Mazata]

Hi there, I must apologize! I have gotten exportify.net confused with exportify.app. The .app version is the one that had all the columns that my scripts rely on.
Thanks for taking the time to answer and for bringing back the track URI.
Cheers and thank you for the awesome tool!

[pavelkomarov]

Hope you start using mine instead. I originally created it because the other was dysfunctional for large playlists (no accounting for rate limits), and I'd just read Marijn Haverbeke's Eloquent JavaScript and wanted to hone my chops. After I'd finished, the other author came back and improved his, but refused to merge my PR. Been bitterly trying to take his user share ever since lol.