Max Semenik wrote:
On 15.11.2012, 4:06 Diederik wrote:
I think that the Analytics team would prefer either:
- detect source of edit in the URL
Or 2) have a hook activated after a successful edit and have the data send to the pixel service
Having this data in a MySQL table poses a lot of challenges with respect of importing that data into the analytics cluster
That's for analytics purposes. However, there can be other use cases for which tags in the DB are perfect, for example filter recent changes for edits made only via a particular channel.
Right, which is why a revision tagging system exists in MediaWiki core currently. If someone wanted to, for example, modify the MobileFrontend extension to add a "mobile" tag to edits, it would be trivial to do. The tagging infrastructure is already in place.
Going back to the broader point, I'm completely lost as to why the Analytics team can't handle a structured database.
MZMcBride