Fulfill “who do we know/who do we know at ___?” use case

[brentdur]

This could be as simple as exporting as a csv or a full UI case

[brentdur]

@ethanresnick I had a thought about this that seemed to match the way things are. Rather than add this to the intranet (which til now has maintained the status of a CRUD GUI), why not add it to blueprint (which has been a tool to do analytics on the api). In my mind it makes more sense to keep the CRUD interface separate from the "function" interface. Thoughts?

[ethanresnick]

@brentdur I said all this on slack, but just for better documentation, my feelings are:

1. "who do we know at ___?" can probably be satisfied just be picking the organization in the intranet and viewing the liaisons.
2. It's more of the "who do we know that might be a good speaker for x event?" use case that needs its own ui (e.g. to filter based on presenters' areas of expertise).
3. for that use case, blueprint probably is the logical home for now, but my long-term feelings on blueprint vs. intranet is that they should become the same system, per Merge with intranet? blueprint#11

[ethanresnick]

A related case is: which companies do we know somebody at. That tells us, e.g. which can we target for a freshman circuit tour without having to send a cold email, etc.

[brentdur]

Case 1 being tracked under #145