Like the title says, the data in the program export under speakers/ makes no mention of the keynote speakers.
This seems to be because they're not present in the DB as "speakers" per se; rather there's a CMS page (https://us.pycon.org/2016/admin/cms/page/52/) where their details are manually input.
The solution to this may be as simple as changing the process for updating the keynote speaker bios to require that the person performing the update to also create/update "proper" speaker bios for them (which are then just not linked to any talk). Alternatively, the CMS page could be ditched and the bio data pulled from regular, standard, speaker bio entries.
Since the program export data is used to populate the mobile app, it would be great if these speakers could show up normally in the exported data. This is not critical for this year, as I can just populate the mobile app manually if necessary, but it would be nice to get as much as possible automated for future years.
Like the title says, the data in the program export under
speakers/makes no mention of the keynote speakers.This seems to be because they're not present in the DB as "speakers" per se; rather there's a CMS page (https://us.pycon.org/2016/admin/cms/page/52/) where their details are manually input.
The solution to this may be as simple as changing the process for updating the keynote speaker bios to require that the person performing the update to also create/update "proper" speaker bios for them (which are then just not linked to any talk). Alternatively, the CMS page could be ditched and the bio data pulled from regular, standard, speaker bio entries.
Since the program export data is used to populate the mobile app, it would be great if these speakers could show up normally in the exported data. This is not critical for this year, as I can just populate the mobile app manually if necessary, but it would be nice to get as much as possible automated for future years.