Non-geo metadata editor requirements

[torrin47]

This issue exists to aggregate all the various requirements for a web-base non-geo metadata editor into a single story. Individual development issues will reference this parent issue.

Requirements:

• [ ] Simple, clean, modern web-based editor
• [ ] Clear delineation between mandatory and optional elements
• [ ] Built-in validation
• [ ] Dropdown menus with choices matching EPA Metadata Technical Specification
• [ ] Compact but intuitive layout - probably requiring several panes

The page should have the structure of a basic HTML form with a submit button (this is designed to allow the page to be incorporated into other tools). In the standalone context the submit button should not post the form fields back to the server, instead it should generate a valid data.json file on the client side that a user can save locally.

[torrin47]

Let's divide this task up into some reasonable chunks. The first push, represented by this ticket, will simply be to get all the form elements onto a single web page. The attached spreadsheet contains notes on the form elements and domains. Other tasks will be tracked as separate tickets.
NonGeoWebFormNotes.xlsx Since many of the elements have very long domains that might change over time, it would be ideal if the values for the elements not be hard-coded on the page but rather loaded dynamically from separate JSON files that we could maintain. This would mean that the form elements would have to be populated on pageload via javascript - we can assume the availability of JQuery, and if there are JQueryUI modules or JQuery plugins that would be beneficial, let's use them.