Merge pull request #27 from brianjgeiger/master

Got partway through fixing #23
Terminate file with carriage return
Specify a type for REC-TYPE
Replace duplicate description with an accurate one
Eliminate trailing whitespace
Include table xref code in YAML

We previously only had a boolean field to indicate whether a column was
reliant on a foreign key present in file 1 (the table file). This was
retaining the logic present in the SCC’s file, which just uses a “+” to
indicate the same thing. The difficulty is that there is no mechanism
to determine *which* foreign key was to be used. Previously we’d tried
renaming the column to use the same identifier that’s found in table 1,
but that’s troublesome—it leads to less-descriptive column names,
swapping out less precise terminology.

Now we’re improving on the presence of the boolean field (which wasn’t
even really boolean before—instead of “false,” the field just wouldn’t
be included) by including the table code, so that there’s no question
as to which foreign key should be used.
Fix case
Make all field identifiers lowercase

Per #24.
Lowercase field

Per #24.
Drop all rec-type fields

No longer necessary, now that the file is broken up into its
constituents. Close #35.
Properly separate JSON elements

Wildly inelegant. Fixes #37.
Lowercase name
Remove unnecessary JSON parameters
Produce individual JSON files for each record

Per #39.
Remove to-do items

Those are issues on GitHub now.
Add a carriage return between each record

Closes #42.
Make output directory a command-line option

Closes #31.
Make input file a command-line option
Only atomize JSON if instructed to

Closes #38.
Replace some tabs with spaces