Build a tool for users to be able to migrate their existing profile data into ComposeDB

[alalonde]

Existing Ceramic data cannot be automatically ported over to ComposeDB. Thus, we'll need to build a backend flow for users to trigger exporting their own data from Ceramic and importing it into ComposeDB. Ideally this is just a click of a button and signing a few transactions.

This sort of thing is inherently error-prone, so we will need to est, troubleshoot and maintain the tool for ~6 months after launch.

[dysbulic]

Do you want to just use the Hasura cache, or do you want to maintain a legacy Ceramic tiles server?

[alalonde]

Great question. We should only support migrating for a certain amount of time, so we could in theory just keep the existing Tile server as the original "source of truth" for ~6 months. However it seems like our Hasura cache is probably good enough? @dysbulic What do you think ?

[dysbulic]

Yeah. So I think there should be a button that populates your profile form with the deprecated values, and you just submit it like normal.

An outstanding question is what to do about the fact your profile is updated through several different dialogs. We could either develop a single-paned, perhaps tabbed, UI, or we could just put a button on each individual dialog to load in the previous data.

[dysbulic]

Especially since self.id has started breaking, so, other than our system, I don't know how one would make changes to their legacy Ceramic profile in any case.

[alalonde]

So I think there should be a button that populates your profile form with the deprecated values, and you just submit it like normal.

Yes, the question is where to put this button? It is probably not urgent to get the data from Hasura -> ComposeDB, but there should probably be a call to action on at least a player's own profile page, if not on the megamenu somewhere. I think we should push people through our UI to submit their data to our ComposeDB models for other projects to use.