As per Mule Design's ThinkUp 2.0 redesign, ThinkUp will support the ability to view information about multiple service users in one view.
For example, an administrator on the White House ThinkUp will see the whitehouse Twitter account, White House Facebook Page, and White House Google+ page in a single dashboard or event stream.
This requires several major database migrations. The new table list could look like this:
Since this is such a major db restructuring, we will probably want to do it in phases. This temporary table can exist between releases if needed:
So, starting from a naive question: Why does this require these db migrations? Couldn't we use a lookup to list which services a user has access to, and then merge together data from each of the services on the client side? For example, I can imagine requesting the most recent 5 posts from each service using the ThinkUp API and then interleaving those all into a display similar to Suth's timeline plugin -- couldn't we do that within the app as well, and leave the data in their current tables?
The database is our default storage place for data. So the application has to know what service users are associated with what profile, and what profiles a ThinkUp user owns. Where store that data if not in the database?
I should also note: many of the existing table renames listed here aren't necessary to support the new feature, but they will help developers understand the data model better, especially since we're introducing yet another term.
Right now, no one really understands what the difference between an instance and an owner and an user is, and this feature introduces profiles into the mix. So the renames are for developer clarity, and the new tables are to support the new feature.
Closing due to inactivity