Is there a way to pull Affiliate data through an API from the campaigns product extension?
Use case: As part of the event registration creation process (see see the campaigns product team page), we are asking campaign organizers if the event page registration that they are setting up is associated with a chapter, organizing partners, user groups, affiliate, or other organization outside Wikimedia (T322332). Currently this is a yes/no question with an open text field that unfurls if the organizer chooses yes. Open text answers pose a few challenges.
Ideally we could pull affiliate names and provide organizers a way to select which affiliates are connected to an event.
Note: There is a precedent for events including this information on their related event pages as images or free text see the bottom of Projeto Mais Teoria da História na Wiki/Mais Pretas and Alto!_Mujeres_trabajando.
We'd like like to allow organizers to log this information on the campaigns product extensions' registration tool. And, we'd like capture this information in a way that assures data quality and which improves the tool and experience in addition to providing the affiliate information.
For example, this WikiGap RDC event, which was set up on the registration tool, had a few fields that organizers filled out: name, organizers, start/end time, location, event_type (online, in-person, hybrid), group chat link. We would like organizers to also be able to add related affiliates to the event. This will help us understand campaigns, grants, and affiliates impact as well as improve event discoverability for events set up using the campaigns extension tooling.
Current ways to pull affiliate information.
- through Hive: by querying GDI.affiliate_data_input_metrics - The campaigns extension, and mediawiki extentions generally, cannot access kerberos data. So for now the first option is off the table, unless the GDI data is not behind Kerberos.
- through Quarry I see queries on affiliates and user groups https://quarry.wmcloud.org/query/runs/all?search_term=affiliate -
Are there current wmf_powered tools that are accessing Quarry data through API? Connecting with someone using that data for a tool would be helpful. Are there issues to keep in mind under this Quarry endpoint data access method?
I'm also seeing from the Quarry main page that there is work going into replacing quarry with a superset instance. When could we be looking at the Quarry to Superset transition executing? In that scenario, might Affiliates and user group data (we're interested in names of the broad groups...so Wikimedia Brazil or Egypt_Wikimedians NOT user x in either of those groups) be available to a public Superset instance? With Superset we can access a virtual dataset using a /dataset/export endpoint.
Are there issues to keep in mind under this Superset endpoint data access method?
See the related conversation on Slack's Working with Data channel
