Stack Overflow API Integration #211
Comments
|
+1 on Everything. I was thinking that we might want to add an "Option" page to enable GDEs to update the SO user_id and in the future other fields as more sources get harvested, this way we can avoid having to manage all this ids in the master_list and leave the GDE the ability to choose which plug-ins to use. P.S. Do you think it's a good idea to ask for feedback on how to integrate SO in the GDE community? |
|
Yes an options page will be of use and the field can provide a marker for processing data extraction. We will request feedback when we are a little further down the line, our previous attempts have not been very fruitful, so I think we are better off doing this in consultation with the team at google who want to get some measurements. |
|
Finally got this going, changing the approach to getting answers for a period and then finding out the tags from the associated questions and created an activity record. Harvest Interval is weekly with a possibility to harvest retro actively from a particular date, while this is going to duplicate some tasks added manually its probably worth asking individual GDE's to delete those. ( This is done on Firefly to get an idea of what is looks like on the front end and in the raw data extraction ) Pushed the code to OMEGA in order to update the Product Group tags so harvesting can happen for those that have supplied their SO id. We can get the GDE to fill up our spreadsheet and push that number higher when we launch. Once the PG where updated, I copied the data from OMEGA 2 FIREFLY and ran the harvest from 1st January 2015. Check out your harvest tasks https://10-dot-gdetracking.appspot.com/#/ Raw export test available (242 activity record creation from 75 gde's with SO id's) https://docs.google.com/spreadsheets/d/1p1goP2PKCjbd7XvqCKvDwGKpeeTfNON-SKILarc1oL0/edit#gid=729453407 |
|
Everything looks good to me |
|
more tags Google-api you could just do a search on Google in tags http://stackoverflow.com/tags?tab=name |
|
Looks like you are only checking from Jan 1, something up with it. Even looking only at the tags you appear to be grabbing. I have answered 3 Google+ (#googleplus), 3 app script (#googleappsscript) and an android (#android) question. They aren't listed. in your sheet. Nor are the older questions that get new +1's or accepts. |
|
@LindaLawton at this time we are only harvesting the questions for the ProductGroup of the particular GDE which explains why the routine may have not picked up these answers. We will need to see with Program Management how they want to deal with impact measurement with relation to GDE being polyvalent. In this harvest I started at Jan 1 2015 indeed, I need to check with Marie what she wants to do with previous periods data, when we may have a duplicate entry issue. I will be launching the feature over the weekend with a FAQ and a Survey and will solicit feedback. That is a good point to raise. |
|
So I am locked into a single product group being Google-Analytics? At the very least please add Google-Analytics-api I don't even think 5% of my answers are analytic's related. Guess I am not a very productive GDE . |
|
I'll take it up for discussion with Ola and Gang in my next meeting.
|
|
I don't think it really matters. This is just for Google to track right. It does make sense that the Analytics team would only be interested in what I do analytics related. Anything I do in the other tags probably isn't valid info for them. That being said looks good :) |
|
One thing I noticed looking at my data on staging: For historic data it would be good to have the |
|
Yes that makes sense, I will make the record take the date of the last day Patrick Martinent On 20 April 2015 at 14:04, Gerwin Sturm notifications@github.com wrote:
|
|
Are you recording all the tags or just the first tag? I seam to be very Android active for a non android person. What happens with a question tagged #android #goggle-Analytics ? What happens if its the other way around? |
|
Best to wait for @patt0 to answer, but looking at his source it will be counted for both product groups. So if you have a question like in your example you will have one SO activity in #android and one in #google-analytics no matter in what order they appear in the question. |
|
@patt0 could you create a PR for your pending changes (even if you still have some additional changes planned before merging), just so it's easier to find the way there :) |
|
Yeah its a little strange, running some test, as you said it should create I did a sanity check against this and got 11 answers for the period Jan http://stackoverflow.com/search?q=user:1841839+[android] So it got the Android tags OK but it did not get Analytics in some case. Been running a test on a month for Linda only and it does seem to work ... I will also do a push of my fork and a PR if I don't find anything in the Thanks both. Patrick Martinent Patrick Martinent On 20 April 2015 at 19:30, Gerwin Sturm notifications@github.com wrote:
|
|
Found the issue, was a classic case of Eventual Consistency as I moved to I have run the harvest from 2014 Jan on stage for Gerwin and Linda so we Patrick Martinent On 20 April 2015 at 19:36, Patrick Martinent patrick.martinent@gmail.com
|
We need to add the SO user_id to the Accounts entity in the backend, and in the Accounts master spreadsheet to update the datastore. We should also identify the SO tags that are relevant for various product groups and teams.
This assumes that an aggregate monthly score is sufficient.
Using the SO https://api.stackexchange.com/docs/top-user-answers-in-tags and the date range query operator, we should be able to automatically create a monthly (other interval?) record for each GDE.
The activity record will not have an associated G+ activity post, and could be entitled
"Monthly SO Activity Record - April 2015"
Perhaps we can define the usage of the impacts for SO as follows:
What we now call Social Impact could hold the number of questions answered / accepted
What we call Total Impact could hold the number of views on the questions, with an understanding that this will grow and that impact is a rolling window.
Its probable that as we move out of G+ into harvesting, we may need to refactor the way we name and collect the metrics we want, killing the one size fits all social metric associated with google+ posts.
The text was updated successfully, but these errors were encountered: