{'fraction_non_alphanumeric': 0.023776223776223775, 'fraction_numerical': 0.0, 'mean_word_length': 4.774193548387097, '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}}
Some Large Questions about Very Large Data Bases

There are now in use many data bases, each containing billions of bytes, which have evolved with no reference to any of the topics discussed at length in data base conferences. Examples are the U.S. Census, UTLAS, PRESTEL, PLATO, MEDLARS, ORBIT and SITA, to name a few. What can be done to prevent data bases from going the way of programming languages, where most of the world continues to use Cobol and Fortran? Perhaps evolutionary models are needed; perhaps data base specialists have to pay more attention to communications. Certainly they have to do more experimental work on operational systems and establish credibility with managers of existing data bases.