Improve usability of export functions

[davidskalinder]

As discussed in #122 and #123, the UI button to export the long-format table of coder-level annotations is borked for any deployment with a DB larger than slightly-smaller-than-either-currently-live-deployment's-DB. So if we want that function to work for larger DBs, we'll probably need to find a whole different way to run that export from the UI in a way that Apache/mod-wsgi can handle without choking.

However, this elides another point, which is that our team at least occasionally uses several other exports that there's no way to run from the UI.

Here's a summary of all the exports we use from time to time:

• Long-format table of coder-level annotations
  • Produced by UI button (for small DBs only) or by running generate-coder-table.py
  • Used by @alexhanna's reports and by @olderwoman's Stata scripts for monitoring coder work
• Long-format table of article-level annotations
  • Produced by running a save MySQL query and then doing (I think) s/\\"/""/g to clean up escaped quote marks
  • Used by @olderwoman's Stata scripts for monitoring coder work
• Wide-format joined table of article- and coder-level annotations
  • Produced by running scripts/by_coder_and_event_by_annotation.py
  • Used by @johnklemke to import data into Pass 2

122 means that in effect right now all of these can be run by developers but not UI users.

First step is to assess the value of making it so that users can run each of these from the UI. Rough idea of the cost will be tricky since finding the right design (which will then determine the workflow) is probably the hardest part... But for now I'll put this on our next team meeting agenda.

[davidskalinder]

So catching up with the team this morning, it seems clear that proper UI functions for this stuff probably aren't necessary as long as these can all be run from the back end by a fairly technical user with a good set of instructions.

So the tasks involved for that are:

• Improve the export process for article-level annotations so that it can be done with a one-liner like python scripts/do-this-thing.py
• Write instructions for running each/any export
• Meet with @olderwoman and/or @limchaeyoon to make sure they can execute those instructions.

I should probably create separate issues for each of these (the first two at least) and make this issue into an Epic containing the others).