The naming conventions within the current ssd schema is not ideal for onward work, might also prevent less-tech users from (more easily)accessing and understanding the data. The current double prefix came about via a need to uniquely name fields that were otherwise duplicated across tables.
Views could be packaged with existing ssd script, and would be expected to be no/negligibly heavier in the data footprint than what we currently have.