-
Notifications
You must be signed in to change notification settings - Fork 6
Onboarding Experts from other area of expertise #3
Comments
About 1: They do need to have a Google account or authentication with Google Cloud endpoints doesn't work to submit/edit data in the tracking app, it doesn't need to be a Google+ account, but Google account and Google+ account share an ID anyway. |
That is my view
|
K understood about 1, edited |
We need to refactor the backend to manage the following new tags, categories and activities Tracking (NEW) Additional product tags for gde (Changes) to existing tags Activity Type Tags Content: #blogpost,#video,#article,#tutorial,#forumpost, |
Making products available by category should be simple (just by adding a My doubt is how we want to manage the "connected with" tags:
|
Answers from Natalie: I'll open an issue for B on the front End to keep track of the request to aggregate the tags for reporting only... maybe will need a |
So we would have a structure like this:
From the reporting side, wouldn't it make sense to offer the user the possibility to view reports on whatever of those levels they want to see. a big overview on "Category" level. a general product specific report, or going down in all detail into product areas? To achieve this it might be useful to create the "Product group" entities like this:
That way, defining the "area" in a post would be enough to uniquely assign it to a product and a category, e.g. just with the tags One thing we have to be careful about (need to discuss this with Natalie/Ola) is that we don't run into the same "problem" with using |
I think picking up posts with #experts + category + area can be safely the new minimum... if I'm making a post with #gde #experts #polymer ... even if I'm not making an activity... I probably should |
As i work through this I am adding a couple of properties to the We need to ensure that #area is unique across the PG's I also pushed all the tags from the PG AT AG sheet I have uploaded a test implementation on firefly which can be observed here Have a look and let me know what you guys think. https://10-dot-gdetracking.appspot.com/#/ Pushed some code to my fork which can be seen here |
I have run a complete update cycle for all the tasks, everything seems to be working, I am inclined to push the new tags and the harvesting code to the existing API so we can tell Ola and gang that they can start pushing new users to us and they can start using the app, reporting their activities. What you say @Scarygami @SmokyBob |
Sounds good to me 👍 |
Sorry for the late response. I think the PG should be considered correct, only if the PG.category matches the expert.Category Going to open an issue about updatint the Experts Masterlist to create accounts with other categories and validate the configured PGs by Category. |
But wouldn't that limit the activities of e.g. Android GDEs who already now post amazing stuff about (material) design/ux without being a UX/Design-Expert by name? Those activities would (in my opinion) be interesting for the UX-reports as well. This is basically the same discussion we had in the beginning with GDEs having activities in other than their "assigned" PG, where the decision then was to track all activities across PGs. |
I see tour point but in my understanding the category on pgs is to filter and see how many activities each expert group have... But I might be mistaken.. I'll ask as soon as I've finished lunch |
I also think we should not exclude post that are across pg's rather we can Patrick Martinent On 13 July 2015 at 17:47, Mauro Solcia notifications@github.com wrote:
|
Ok so an example post tagging could be and they'll both count in 2 categories and 3 PGs? Mail to Nat coming in seconds with the same example P.S. Sorry for being telegraphic |
Sorry for writing only now, busy interviewing another possible Polymer Expert. Just to keep track with what Nat said:
Was starting to work on #13 but remembered that the update_gplus.py service checked the
What are your thoughts on this? |
... or we could infer the Category on the Expert from the first of its PGs, trusting we don't change the Category on the PGs... |
I am happy to make it as simple as possible for you, its just a couple of line here and there in the update service checking for the account type. For now I am going to accept active and all the category types, then when you give me an ok, I can remove the active type from the accept list. I can't seem to see any 'admin' or 'administrator' type anymore. If we are happy with ... 'gde' Then I have pushed the following commit to the backend patt0@53212d2 |
@patt0 Looks good to me. I'll clean up the MasterList and WebApp code to us the account.type instead of infer the category from the account's PGs. |
Today's updated on the tags after the discussing with Nat & Ola some issued on the creation of ux_ui Experts. for UX please use the following # instead: I'll update the tags in the PG AT AG Masterlist and do all the pushes to the backend as soon as I get out of the office (or let me know if you do it before 7 PM CEST) |
DONE does this mean we remove the #uxdesign ? Patrick Martinent On 15 July 2015 at 18:49, Mauro Solcia notifications@github.com wrote:
|
Thx. Yes uxdesign would have been the combination of InteractionDesign and VisualDesign but the "fear" is that if it was available everything was tracked under it. |
This is more of a way to keep track of the TODO than a proper issue, more detailed Analysis/discussion can be done "privately" with Docs and more detailed issues and TODOs will be added to the repo in the future
Currently the app is tailored to fit the "tracking needs" of Technology Google Experts.
The need to track activities is for other area of expertise too so why reinvent the wheel? :)
Some points of discussion about tracking activities for other areas of expertise are the following:
Changes to the current data structure are needed to support the features listed above.
The text was updated successfully, but these errors were encountered: