IGDB Data Switch Discussion

[peter]

@mmuffins

Also, users will likely be confused as to why there are suddenly a bunch of duplicate games.

Hopefully I’d mitigate this issue by just not surfacing the old data anymore. The only place you’d see it is on user’s profiles and shelves.

@mmuffins

Having clear new/legacy (or something along those lines) indicators to distinguish data from different providers

For sure. I have a new game page designed for the IGDB entries, so it would look way different than the existing entries.

@mmuffins

Encouraging users to use the new igdb entries rather than the existing giantbomb ones, e.g. by making old data read only, or putting up banners

Yeah, I would definitely make the old games read only.

@mmuffins

Using that crowd sourced data to gradually improve data quality. Like, if a few dozen people want to migrate data between the same source and target game, it might be safe to automatically merge them

I like this. I can create some kind of system that keeps track of migrations.

There’s just so many ways to screw this up! It’s why I haven’t finished anything It’s sad too because the data linkage in IGDB is pretty fun to use. I have downloaded a bunch of the data on my development machine, and clicking around between games is fun. It’s fun to try and play seven degrees of Kevin Bacon with games.

[WerqKween]

For reasons mentioned and more, absolutely do not have two contiguous databases

[paycheck_stevens]

Would it be feasible to set up a prompt via email and when people log in or and send them to a place where they can shift their data to IDGB as of a certain date in order to lessen the impact of mmuffins first point: * One is aggregated data like user ratings or completion times will be incorrect because that data will be split between existing game entries and new ones.*

Basically a cutover date? Those who care about preservation of their info can help ensure its safety or trust the work of others?