How should we represent SE creations?

[WalterSimoncini]

In the database schema, we have the is_se field, which indicates whether a transaction concerns the creation of an SE company. According to the excel sheet an SE can be created via merger, conversion, holding-SE, subsidiary-SE, or unsure when this information is unknown.

Would it make sense to represent this information via the transaction's class (aka type) by classifying these transactions as "SECreation" with the following subclasses?

• SECreationConversion
• SECreationHolding
• SECreationMerger
• SECreationSubsidiary

And when we do not know the SE creation subtype (equivalent to "unsure") we would assign the umbrella class "SECreation".

This structure could allow users to write more expressive queries (instead of querying on the boolean is_se and the se_type fields), what are your thoughts on this?

[kodymoodley]

Thanks @WalterSimoncini , I defer this issue to @marcus-meyer-maas and @pedrohserrano . They indicated that this is an important issue to resolve. Let's hear their thoughts.