Add business logic for `isPrimary` and `isSubstrate` in COGs

[grantfitzsimmons]

With the introduction of Collection Object Groups (COGs), we added two new fields in the CollectionObjectGroupJoin(COJO) table:

• isPrimary: Represents only the important CO in a COG
• isSubstrate: Represents the CO in a COG that acts as the substrate for the other COG children

Business Logic:

• In each COG, isPrimary and isSubstrate can only be set to True for a single CO.
• COJOs that link to a child COG instead of a child CO cannot check either the isPrimary or isSubstrate fields.
  • These are only for COJO records that link to a CO.
  • These fields can be rendered as read-only or hidden, however it is done best
• When checked, IsPrimary is set to True for one CO in a COG. All other COJO records will have IsPrimary set to False.
• When no CO has IsPrimary set to True, it is NULL for all COJO records in the COG.
• The first COJO CO will automatically have isPrimary set to True when the COG type is 'consolidated'

Behavior

Users should be able to count the number of physical specimens in their collection by searching:

Base Table: Collection Object Query Line: Collection Object --> COJO --> IsPrimary = True or NULL

This should return all Collection Objects that are members of a COG where they are the primary CO or COs that are not members of a COG

[sharadsw]

The first COJO CO will automatically have isPrimary set to True when the COG type is 'consolidated'

First COJO CO by order of entry or first COJO CO determined by the precedence field?

[grantfitzsimmons]

First in the order of entry