Thread:Talk:Requests for comment/New sites system/First-class data or index/reply (2)

Mmmmm... ok, yeah I was starting to lean a little towards somewhere in the middle a little earlier.

How about some notes/changes to that:
 * Note that if we get the web UI out and make it the recommended method the site table will quickly turn into something that is always treated as an index.
 * This web UI is actually probably going to end up used for editing the local stuff even when you're using something like Wikidata to fill it.
 * How about instead of making it a firstclass/index boolean we call it a 'source'. If the source is the string that the web UI uses it knows that it can edit the global data since it inserted it. If the source is something like 'wikidata' then it knows that it can't edit it and must only let the user modify the local data that it manages.
 * If you don't mind, while we're not aiming for multiple sources here we could actually put source as a column in the database. It could be useful to deal with some situations like a wiki transitioning from local to global data. So that we know what sites from a wiki being turned into one that just reads the global data have not been put into the central database yet. It would also let us safely purge data from an old source without damaging new data added to the table.