Best practice to defining logins for correct sector matching

[capzDE]

We are currently in the process of completely overhauling our available sector splits in EDGG and I was wondering what the best practice would be to effectively match sectors on map tools using this dataset without having to individually define dozens of logins in the dataset.

With current plans, for positions bandboxing more than one sector group, the first one or two letters of the middle part of the login will indicate the covered area while the last letter will indicate whether only lower airspace is covered or both lower and upper airspace, as well as serving as a replaceable letter for relief positions or mentors.
For example, a position covering a given lateral area may use the login EDGG_SOx_CTR, with x being the replaceable part.
EDGG_SOL_CTR would just cover lower airspace.
EDGG_SOH_CTR would cover both lower and upper airspace.
EDGG_SO1_CTR would be a relieving controller.
EDGG_SOM_CTR would be a mentor.

My original idea was to just define the sector as EDGG-SO|Langen|EDGG_SO|EDGG-SO, assuming that map tools would match everything beginning with the respective definition (i.e. anything beginning with EDGG_SO would match for this sector), but it has recently been brought to my attention that this may not be the case and that map tools may instead only be looking for exact matches (i.e. only EDGG_SO_CTR would match, while EDGG_SOH_CTR, e.g., would not be matched). If this is the case, we would need to define a significantly larger amount of logins to roughly accurately match just the positions we expect to be opened quite regularly, let alone the ones we expect to see only every now and then.
What would be the best approach to get sectors matching reasonably correctly in this case without having to "flood" the dataset with dozens of login definitions?