Matter Only or Matter Case

Many case management systems have separate objects (areas) for cases v. matters where matters may contain multiple cases. I believe a more accurate analysis of the real-world system is that matters may be composed of other matters. Therefore, the better implementation would be to allow for classification of a matter as a case. As we already support categorized tagging, this could already be done by a user by specifying a category of "Type" and a tag of "Case".

Consider:

1. In a merger, the lead attorney has decided they want to use multiple matters to track multiple different aspects. This allows the lead attorney to delegate leadership roles on a more finely grained level.

2. Attorney is helping Client setup a business. While one attorney may wish to use tasking within one matter, Attorney may wish to use multiple matters.

However, we must consider the implications of allowing submatters within the system. As long as all other objects are constrained to a single matter (no overlap), the remainder of the system should be unaffected as any other objects reference the matter by id which is a Guid and unique.

The implementation will be done by adding a parent id property that will either be null (if root level) or will hold the Guid of the parent object.