Add business logic for MOTs

[grantfitzsimmons]

Component of #4640

Review the full business logic described in the main topic and let me know if there are any questions.

Business Logic & Requirements

• Each collectionobjecttype would be scoped to a particular collection

• An objectType would be chosen from a pick list on the Collection Object form

• When creating a new Determination record, the system should check the objectType.taxonTreeDef field to find the tree to search for the user's entered name when searching in the taxon or preferredTaxon query combo boxes

• objectType should not be a required field but can be made to be using the form editor.

• Conditional forms must be able to use the value from the objectType field to determine the layout in an intuitive way for users

  • If the user can define a form definition as follows:

    <cell type="panel" coldef="100px,2px,76px" colspan="6">
      <rows>
        <!-- This view definition will be displayed in Specify 6, or if all other conditions don't match -->
        <row>
          <cell type="label" label="Without any object type, this will display." />
        </row>
      </rows>
      <rows condition="objectType=Rock">
        <row>
          <cell type="label" label="This is a rock!" />
        </row>
      </rows>
      <rows condition="objectType=Mineral">
        <row>
          <cell type="label" label="This is a mineral!" />
        </row>
      </rows>
    </cell>

  That would be satisfactory. This would enable users to create forms or display subviews based on the value, which would also enable users to create specific determination forms or collection object attribute forms based on the value of objectType.