Salary Coefficient

referenced: [1]

[1] -> http://oregonstate.edu/dept/fa/manuals/pay/ex3
Even if we would want to implement the factor table, we would certainly not hardcode the fractions. They are not universal, so if at all then this needs to be stored as triples.

Then, of course, the actual table would depend on the organisation and of course on the staff type/level, probably even on the employment contract type (very likely), and in the VNRC case even on merits, education level, awards received etc. - regulations in and within different countries and cultures can vary massively.

So massively that we do not even intend to store the whole table (or table/s/ as it would actually be) and if we would, then we would need to also track all the data required for the lookup, with no generic lookup mechanism possible (nor have you implemented a lookup mechanism yet).

Could it be that the OSU table was given to you as an example and you have just implemented it as-is without first looking at other cases and developing a proper model?