Jalama

Support multiple tables

Three Cases

A -

1) Lookup tables (follow the EML references to get enumerated values out of a
table). This is probably just a case of writing rules to do it - should be
possible without any architectural changes

2) Normalized data - foreign key constraints between tables:
Context versus measurements (e.g., site table versus plot measurements table)

3) Orthogonal tables - no foreign key constraints - just need to generate
mutliple unrelated UIs into individual XUL forms (currently, all tables appear
in one form)