search

jnf / blinder

We use Blinder to collect and review responses to event RFPs.
MIT License
6 stars 8 forks source link

Handle "built-in" fields differently #66

Open seejee opened 10 years ago

seejee commented 10 years ago

All proposals, regardless of event, will have some set of basic fields. Things like talk title, abstract, and speaker contact info might be best treated as special cases so they can fetched and displayed easily.

For example, as Jeremy has already pointed out, finding the email address for a proposal is not easy and is somewhat brittle.

jnf commented 10 years ago

Super brittle. :(

I don't want to push hard on this during SCRC's CFP process (because it's working), but it's something that definitely needs addressed in a real and meaningful way soon.

For contact/person infos, it seems simple enough to extend the oauthy bits to other providers as a means of identifying and communicating with submitters.

If we wanted to keep the question abstraction really high (and I kinda do, but mostly because it's fun), we could look at marking some Questions with a new identifier (Sortables? Listables?) that tags them for display on management/review screens so I can easily grab them (and use them for hooks for sorting/display options). What do you think?