myw/sehrvy

Tutorial Perl project to familiarize ourselves with servers and databases in Perl, and visualization in JavaScript. Create a series of visualizations of electronic health record software usage, based on data from data.gov.

sehrvy's Issues

Pick a testing framework

It seems like, for our simple purposes, Test::Simple and Test::More will do the trick. I propose making t/Foo.t files for every module we need, and maybe the scripts, too. They can then be run with the prove command from the directory with the module files. An individual .t file can use whichever testing module it needs to.

Although this structure is not explicitly enforced by the testing framework, we should try to make tests not too interdependent. And we should comment what every test is doing at the start of the testing block, for example:

# Check equality of exponentiation
my $foo = 3*3;
my $bar = 3**2;
ok($foo == $bar, 'exponentiation works');

Thoughts?

Modelines/Local variables and consistent spacing throughout files

Files should be indented with spaces, with a tab-stop size of 2 spaces. All Perl, JavaScript, and HTML files should have appropriate vi-style and emacs-style modelines/local variable lines, commented-out, at the very end

The vi-style line is: vi:sw=2 ts=2 sts=2 et:. The emacs-style line is (should be?) : -*- indent-tabs-mode: nil; tab-width: 4; indent-line-function 'insert-tab; -*-

JavaScript and front-end functionality

This is a good place to discuss front-end related issues.

API for queries through the `/query` URI

Queries will be of the form: query/query category/query type?q=query string . For example, to query all products from vendor Foo, which has hug foo, the URI would be query/vendor/products?q=foo. Or, to see the prevalence of that vendor by state, the query would be query/state/vendor?q=foo.

The API will return JSON, formatted to work with Google Chart Tables API.