SmokyBob
commented
9 years ago +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. What do you think?
P.S. Do you think it's a good idea to ask for feedback on how to integrate SO in the GDE community?
patt0
LindaLawton
Scarygami
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.