VisualEditor/Metrics

General

 * Hourly edits

Edit schema
The Edit schema collects all the data we need to analyze the edit funnel.

Things to do:
 * Instrument the editing facility in the apps?
 * James isn't convinced that editing in apps is an important feature
 * Remove unused fields
 * page.length cannot be easily calculated, and has always been recorded as -1.
 * Start actually recording platform type
 * Ideally this would be by directly testing screen size and so on
 * If that's too difficult, we could instead add "MobileFrontend" to integration (maybe we should do that anyway)
 * Figure out why all recently events have not been validated
 * Add switchnochanges as an enum value of action.abort.type
 * Visualize it using a Sankey diagram?
 * Visualize it using a Sankey diagram?

Merge MobileWebEditing schema into Edit schema

 * editor → editor
 * token → ?
 * What type of goes in here?
 * action → action
 * Add instrumentation for init events
 * attempt → ready
 * save → saveIntent
 * submit → saveAttempt
 * success → saveSuccess
 * cancel → abort
 * error → saveFailure
 * switch → abort.switchwith or abort.switchwithout
 * Requires additional instrumentation to distinguish between the two types
 * funnel → action.init.mechanism
 * do we need to support the specific values from MobileWebEditing? article, ctaSignup, leftNavSignup
 * section → ?
 * do we really need this?
 * revId → page.revid
 * pageId → page.id
 * namespace → page.ns
 * userEditCount → user.editCount
 * isTestA
 * Don't need this.
 * username
 * Don't need this as we already have user.id
 * mobileMode
 * Do we need this? Should we generalize the destination property so that it could work for a theoretical desktop beta mode? James says we've never used the alpha or beta modes to test editing features.
 * errortext → action.saveFailure.type
 * What goes in the errortext field?

Editor engagement dashboard
http://ee-dashboard.wmflabs.org/dashboards/enwiki-metrics#
 * Move useful metrics to edit analysis dashboard
 * Hourly edits, broken down by editor (number and %)
 * Maybe add breakdowns by user experience?
 * Should this stay limited to main namespace?
 * Daily unique users of wikitext and visual editors
 * Turn off unnecessary metrics
 * Hourly edits broken down by (outdated) editor types
 * Daily, hourly, and cumulative tagged revisions
 * Hourly main-namespace edits by XLinkBot
 * Hourly main-namespace edits by ClueBot NG
 * New account registrations (reg3_daily)?
 * New mobile account registrations?
 * New account registrations by campaign
 * When turning off, how do we preserve definitions along with the raw data?