Notes on Outline first draft

[gregelin]

@feomike

Questions

• Who is in the audience? I'm assuming mix of lawyers, analysts, and economists.
• Have we worked out how people will actually interact with the data? Will each individual or subgroup be making local copies, or will there be read-only to a server? Are there individual accounts, or just a common read-only account everyone uses?
• What the most likely queries, activities the audience (or audience subgroups) will be doing?

Thoughts

• Good decisions on what to leave out
• Outline is not as clear as to how deep you diving into particular areas. First draft has lots of information about dependencies (which is pretty geeky)
• Does getting data in/out about generally getting data in/out of database or about getting access to specific data set in specific context at a specific org?
• Maybe avoid mentioning specific data sets in outline, though you can certainly use close to actual data nomenclature.
• Maybe avoid too much detail on clients and connecting and instead focus on a half-dozen illustrative queries example (select, simple join, simple grouping, simple filtering)
• Show an example of you tend to manage your queries and results and how you use the resources.

[feomike]

@gregelin perfect. thanks. great feedback. i will revise. btw, this is the best workflow. here is something, comment, either inline or set up issue. :+1:

[gregelin]

New version with "Here is where I..." looks much better. Feels more mentoring and allowing people to pick up different aspects.

[feomike]

thanks. i have moved it along a little. i am giving this at 1pm today to some internal folks. if you have time, would be great if you sit in.