1042067 - Make it easier to identify events hosted by key partner organizations

Status: RESOLVED FIXED

(Webmaker Graveyard :: Events, defect)

Description

[Matt Thompson (@OpenMatt :OpenMatt)]

CONTEXT
* Partnerships are key to overall Maker Party success. We are now starting to follow up with key partners and Super Mentors on a daily / weekly basis. 

* Data is key to supporting this. We need to be able to tell whether these partners are actually following through on their commitments to host events.

CHALLENGE

* right now, there's no easy way to tell which / when partner orgs are throwing events. It requires manual detective work by pouring over the CSV export, looking at the "email" and "organizerID" field.

* We need an easier way to track and manage this. We can be creative with how we approach this. Let's find an approach that requires the least work with best result.

Comment 1

[Matt Thompson (@OpenMatt :OpenMatt)]

POTENTIAL APPROACHES:

* a) Add an 'organization' field
** currently there is an e-mail field + an organizerID field. But no "organization" field.

* b) Encourage the use of "organizational" webmaker accounts 
** Spur partner orgs to create a Webmaker account. if the Partner had an account, with an intuitive logo and name, (e.g., "CoderDojo") then it would be more obvious

* c) Use ReferrerID tags
** Get partners to include them when they register an event? Put that as an optional field on the form?

* d) Something else

Comment 2

[Matt Thompson (@OpenMatt :OpenMatt)]

* I wonder if JBuck's leaderboard prototype is relevant / helpful here....

Comment 3

[Michelle Thorne]

I like (b). 

Partner org makes a webmaker account which is then added as co-organizer. 

Here are examples from Hive Toronto: 

* https://events.webmaker.org/#!/events/4210
* https://events.webmaker.org/#!/events/4233

Comment 4

[Matt Thompson (@OpenMatt :OpenMatt)]

* (b) is also the least amount of work. as in: no real development work at all. BUT: will (b) alone solve the problem?

Comment 5

[Matt Thompson (@OpenMatt :OpenMatt)]

* We'll wait to hear further from Geoff /  Chris  / Michelle before proceeding on anything

Comment 6

[Matt Thompson (@OpenMatt :OpenMatt)]

* Gavin just pointed out that event *tags* can also help with this. Admins could add a tag like "Scouts" or "MacArthur" or "Coder Dojo" to help associate like events

Comment 7

[Matt Thompson (@OpenMatt :OpenMatt)]

* Geoff still prefers (c) referrer ID for this. Trying to understand what / how we would implement that.

Comment 8

[Matt Thompson (@OpenMatt :OpenMatt)]

* Claw has a strong proposal here. Him and Geoff are going to help lead next steps.

PROPOSAL:

1) Start by identifying most active *even hosts*. Individual people / user accounts.

2) Then, associate those with their organization. "e.g., we now know that [e-mail] = Coder Dojo"

3) Log that info. In the right spreadsheet. (And maybe file a bug against it?)

4) We can then trigger various event platform updates / mechanisms / batch updates based on that. 

Such as:

* adding co-organizer. adding the organization account as a *co-organizer* to the events. e.g., "Coder Dojo" gets entered as a co-organizer on "[e-mail]'s" events.

* adding tags. We can also add "Coder Dojo" as an event tag. This may be overkill -- but it's one more way to easily sort and discover like events.

5) This triggers various benefits
* It makes the Coder Dojo profile page a rich hub for all their events. good storytelling / functionality there.
* It triggers various responses that can help our contributor numbers go up
* It requires no new development work

Comment 9

[clawrence]

Here is my remix of the above:

PROPOSAL:

1) Start by identifying most important Event Partners. (Combo OF: Amira, Michelle, John, Geoff, Chris, An-Me, Melissa)
- Which ones are network hubs and those need to nodes tracked and linked to hub
- Which ones are one entity and really were committing to one event, or > 5

2) When applicable then, associate those with their organization. "e.g., we now know that [e-mail] = Coder Dojo"

3) Log that info. In the right spreadsheet or directly into events platform. (And maybe file a bug against it?)
 - add hub organizations/networks as "co-organizers" to their members events


4) We can then trigger various event platform updates / mechanisms / batch updates based on that. 

Such as:

* adding co-organizer. adding the organization account as a *co-organizer* to the events. e.g., "Coder Dojo" gets entered as a co-organizer on "[e-mail]'s" events.

* adding tags. We can also add "Coder Dojo" as an event tag. This may be overkill -- but it's one more way to easily sort and discover like events.

5) We come up with targeted "asks" for the follow-ups
- Did you run the events you committed to, why not, what help do you need etc
- For the events you have listed did you know you can: Add mentors, organizers, track RSVPs..."Make the most out of the tool"
- Have you run your events? Did you know you can: send badges, collect webmaker makes, highlight photos etc

This triggers various benefits
* It makes the Coder Dojo profile page a rich hub for all their events. good storytelling / functionality there.
* It triggers various responses that can help our events, contributor and account sign-ups numbers go up
* It requires no new development work

Comment 10

[Brett Gaylor [:brett]]

OK, Michelle if this is the approved approach can you please close this bug?

Comment 11

[Michelle Thorne]

Yes, this is the way to go about it and we've started this with the account mgmt team.