change the presentation of keywords, theme, and references

[gbinal]

From Issue #20, the actionable deliverable would be to change the way that the generator parses the contents of the keywords, theme, and references field so that they can be entered into the field with commas but then presented in the json as an array of strings. See below.

The generator makes every field "standard JSON" i.e.

'{ "keywords":"this, that, the other" }'

This is not compliant with the standard, which has more specific requirements for how to represent the objects. For example:

'{ "keywords": ["this", "that", "the other"] }'

[gbinal]

Actually - note the clarification that Charles made on issue 20. We should factor in his points.

[cew821]

@kinlane's to-do list was:

• Check for comma separate and convert to array.
• Then on display, display simple and named arrays.
• And of course export as arrays properly.

[cew821]

The fields where "special" handling (mostly string needs to be put into an array of strings) needs to happen are:

• bureauCode
• programCode
• keywords
• theme
• references
• language

Also, dataQuality needs to be a boolean, not a string, i.e. true not "true"