In R&H, active linear events can legitimately be:
- contiguous & non-overlapping
- contiguous and overlapping
- non-contiguous & overlapping
- contiguous & overlapping
Editing behaviour options like retire overlap and merge coincident events should be set differently by the technicial for each to avoid unwanted duplicates or avoid unitentional retirement of overlapping events. Attribute sets if designed properly, will group these like event types. If attribute sets could be stored/deployed with retire/merge preferences, the user would not need to remember to check/uncheck controls, adding more safeguards to data integrity.
