Closed Bug 1047299 Opened 10 years ago Closed 9 years ago

Import data from mofointegration to Baloo

Categories

(Community Building :: Systems and Data, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
2014Q4

People

(Reporter: adam, Assigned: scabral)

Details

(Whiteboard: [Baloo][Q3][data: ETL])

The tables to import which will be used in the aggregations are: * vw_adhoctribution * vw_mozfest * vw_transifex * vw_webmaker_events * vw_webmaker_events_coorganizers * vw_webmaker_events_mentors These views should match the Baloo Schema 0.1, with any additional columns explained in the Schema Documentation: https://wiki.mozilla.org/Baloo/Schema/0.1 DB Access info is in: Bug 1042057
Adam - Are there contributor conversion points yet? They all seem to have "tbc" under them in the conversion points documentation, including mozfest, the info from the ad-hoc logger (which I assume is in the vw_adhoctribution table), transifex, and webmaker events. https://wiki.mozilla.org/Contribute/Conversion_points#Mozilla_Foundation_.28MoFo.29
The "tbc" were for other columns on the wiki page about recognition and contributor pathways, but the conversion points are in the first column of each of the teams on that page (the metrics datasource column). This ticket was just for the loading of the raw data (sorry if splitting this out caused confusion). Loading those 6 tables in their entirety will give you the raw data needed for building the aggregations specified in separate bugs for each MoFo team. This bug for example is for aggregations for Webmaker: https://bugzilla.mozilla.org/show_bug.cgi?id=1047309 In there is a link to an etherpad with example queries for how to match the 'generally phrased' conversion points on the wiki page with the specific data in those 6 tables from the integration DB.
Whiteboard: [Baloo][Q3] → [Baloo][Q3][ETL]
Whiteboard: [Baloo][Q3][ETL] → [Baloo][Q3][data: ETL]
Target Milestone: --- → 2014Q4
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.