MOTs business logic: Create Collection Object forms and Taxon forms for each CollectionObjectType

[sharadsw]

Related/alternative to #4982

• Each CollectionObjectType would have it's own Collection Object and Taxon forms: eg: Collection Object Rock, Taxon Mineral, Taxon Fossil, etc.
• Since each form would have a predetermined CollectionObjectType, conditional rendering is no longer necessary.
• Like in Add business logic for MOTs #4982: When creating a new Determination record, use 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

[sharadsw]

Summary of the meeting with Caroline & Jason:

• Multiple Forms:
  • Each COType form will need an XML attribute to indicate which COType it is for
    • The value from this attribute can be used to send the COType data to the backend when the resource is saved
  • Data Entry will have a section called Object Types which will list all CO/Taxon COType Forms.
    • We filter all views to find views with the XML attribute mentioned above and use that to list the COType forms in Data Entry
  • Each COType form definition will be defined in App Resources
    • If a COType form definition is not defined, it will display the default CO/Taxon Form
  • When creating a new CO form definition,
    • The ‘create new form definition’ dialog will have a subheader COType containing a list of form definitions for each COType
      • The list of COTypes would be obtained from Schema Config
    • If the user picks a COType form definition from above list, the form will contain the necessary XML attribute
    • If instead the user clicks on ‘New’ instead of a COType form, it will be a normal CO form without the attribute
      • If they want to add the COType attribute, they can do it manually in the XML Editor
• Business Rules approach (see MOTs business logic: Refresh CO form when CO Type changes #5088):
  • For clearing values when COType is changed, refresh the page
  • Cache the new COType before refresh and restore after refresh

Decision taken: Use Business Rules/refresh approach as an initial version/safety net and work on MultipleForms approach after