Baloo: Difference between revisions

Baloo (view source)

Revision as of 15:53, 28 February 2014

3,102 bytes added , 28 February 2014

→‎Adding a new system

Ppapadeas

canmove, Confirmed users, Bureaucrats and Sysops emeriti

1,783

edits

@@ Line 29: / Line 29: @@
 Baloo deals with Contribution Data. Contribution Data are defined using the established [[Wormhole/Schema|Schema]] of the Community Building Team.
 === Adding a new system ===
-TBA
+Several steps are needed in order to add a new system in Baloo. They can be broken down to two different sections. Porting historical data, and implementing live pushes
+==== Adding Historical Data ====
+Once a system is identified holding historical contribution data, the following should be done to import those to Baloo. Note that this should be an one off procedure given that live-pushes are also implemented in a system.
+# Identify *what* do you want to track in your system. Write down all possible contributions that are happening in your area.
+# Talk to your principal webdev or technical people, on how this info is stored in your database.
+# Tweak/amend the [[Wormhole/Schema|Contribution Schema]] to fit your tracking needs. (Contact Pierros or join Systems and Data WG meeting for help)
+# Open a new bug on [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Metrics&component=Data/Backend%20Reports Mozilla Metrics::Data/Backend Reports] describing the location of the data and the schema/mapping your are about to use
+# Data and BI team will be following up with you on imports
+==== Adding Live Pushes ====
+# Make sure you follow steps 1,2 and 3 above.
+# Coordinate with your principal webdev or technical people on implementing the code on your system side that produces and pushes the JSON contribution tracking payloads.
+# Open a new bug on [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Metrics&component=Data/Backend%20Reports Mozilla Metrics::Data/Backend Reports] so we can track the implementation process.
+# Tryout staging the code using the following <pre>curl -v -X POST -d '{"test":"hello"}' http://10.22.28.101:8080/submit/baloo/</pre> If the operation successful we will return 201.
+# Once you are ready for production you may use the production url:  https://data.mozilla.com/submit/baloo/
+{{admon/note|All data is in raw format till this point| If any or both of the above is implemented for your system, you have raw data in our HBASE. Although this is available for crunching, you still need to establish your contribution area conversion points so we can start tracking active contributors}}
+==== Tracking active contributors ====
+Once one or both of the processes above are complete we now have raw contribution data about your area. Raw data is cool, but we need to start making sense out of them. For that reason we need to establish Conversion Points to understand the type of contributions and identify Active contributors.
+# Have a meeting with your CBT contact person to identify (if not already done) your contribution pathway.
+# Navigate to our [[Contribute/Conversion_points|Conversion Points]] wiki page and add/edit your contribution area with all relevant info.
+# Once the conversion points are up to date, open a bug on [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Metrics&component=Data/Backend%20Reports Mozilla Metrics::Data/Backend Reports] so we can create the aggregation scenarios and start crunching the raw data.
+# Magical numbers will flow in, and become available in Tableau (and APIs!) for usage!
 == Meetings ==