magfest / ubersystem

MAGFest's Ubersystem - handles ticketing, staffing, analytics, volunteers, and tons more
http://magfest.org
GNU Affero General Public License v3.0
48 stars 55 forks source link

Guidebook Information Update: It Might Be Nice If... #2267

Open seatsmachine opened 7 years ago

seatsmachine commented 7 years ago

Currently, the Guidebook app information provides only the name of the panel/event, the location of the panel/event, and the description of the panel/event under each entry, which I imagine looks something like this in spreadsheet form: current

Unless I am very mistaken, Guidebook has the capability to include presenters to each panel as a separate data line, which allows that to be a searchable metric either via a tab on the main menu of the schedule or via clicking on a panelist's name in an event description. (If memory serves, it displays with or near the location of the event.) This would probably look like the following: proposed

Steph Prader has confirmed she can add information if given to her. An additional check might be required to confirm the functionality of adding the "People" tab to the menu, just for sanity's sake.

BlueHat-GURU commented 7 years ago

I'll get this to Steph; I don't think she checks github much.

seatsmachine commented 7 years ago

Thanks Dave!

binary1230 commented 7 years ago

I actually do think this issue belongs in github. @BlueHat-GURU if you'd like though, make a JIRA task and link to this task. Steph wouldn't be the one to complete this task, it would be a code task

binary1230 commented 7 years ago

and this would be a pretty simple code task potentially too

binary1230 commented 7 years ago

but yea you're right that Steph would likely need to sign off on the format and information going out, and then a coder would have to write this export

BlueHat-GURU commented 7 years ago

Is this before event, or for next year?

seatsmachine commented 7 years ago

This would be for the MAGFest in several days.

binary1230 commented 7 years ago

this is going to be a slightly lower priority but might be something a newer coder could tackle in the runup to event.