Create a Simple Solicitation from JSON for

• VLA
• GBT

not implemented/requirements not in a story:

• modify parameters such as frequency ranges on bands

Can set override flags for Target Override Matrix to allow Capability Parameter Specifications to be overridden

• The correct overrides are shown in the TOM per Capability

As an Author, I would like to view my proposals.

• in a list
• in a detailed view (Card)

• (ahc)There is a superset of elements for Field Sources but their behavior diverges between the capabilities. Notably, the fields reset themselves in the VLA and do not in the GBT

Modifying the TOM affects the Science Target List and the OS generation

• (ahc) VLA: Sometimes this is true. Sometimes it is not true. The behavior is the same in real VLA and GBT Capabilities. Sources are being dropped from the TOM → STL.
• (db) GBT: working

• (ahc) the simple partitioning appears to be working, as well as the simple calibration strategy; The time calculation isn't displaying the information correctly in the GBT capability sometimes. I haven't tested the math behind the calculation.
• (db) GBT: RMS and requested time calculation appears to be correct in Observation Specification but not in the Science Target List

As a Product Owner, I would like the STL to contain the correct Source and Hardware Configuration name to reflect what is specified by the Capability Request + TOM

• The Science Targets should have a Source name, which is specified by the Field Source
• The Science Targets should have a Hardware Configuration name, which specified by the Spectral Spec