Rentcaps are currently stored as date ranges + a percentage. Making this more dynamic will require uploading a CPI matrix and writing a data connector for that, and then refactoring the rentcap connector to store and apply formulas.
This should be hidden from things that use the rentcaps; they should still be able to request a location and get back date ranges + caps.
We probably also want to allow a manual override (ie we store a raw number that supersedes), in case we find out cities are making one-off exceptions to their formulas.
Rentcaps are currently stored as date ranges + a percentage. Making this more dynamic will require uploading a CPI matrix and writing a data connector for that, and then refactoring the rentcap connector to store and apply formulas.
This should be hidden from things that use the rentcaps; they should still be able to request a location and get back date ranges + caps.
We probably also want to allow a manual override (ie we store a raw number that supersedes), in case we find out cities are making one-off exceptions to their formulas.