{'fraction_non_alphanumeric': 0.040697674418604654, 'fraction_numerical': 0.0011627906976744186, 'mean_word_length': 5.888, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Object-Oriented Data Warehousing

Data warehousing has largely developed with little or no reference to ObjectOriented Software Engineering (OOSE) [1]. This is consistent with (a) its development out of two-tier client/server relational database methodology, and (b) its character as a kind of high-level systems integration, rather than software development, activity. Data Warehousing assembles components, rather than creating them. The initial top-down centralized data warehousing model with its single database server, limited middleware, and GUI front-end, could get by with a pragmatic "systems integration" orientation at the global level of component interaction, while restricting explicit object-orientation to the various GUI, middleware, analysis, web-enabling, data transformation, and reporting tools that comprise the data warehousing arsenal.