{'fraction_non_alphanumeric': 0.024600246002460024, 'fraction_numerical': 0.0, 'mean_word_length': 5.213740458015267, '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}}
Managing medical research data with a Web-Interfacing Repository Manager

This paper describes the Web-Interfacing Repository Manager (WIRM), a perl toolkit for managing and deploying multimedia data, which is built entirely from free, platform-independent components. The WIRM consists of an object-relational API layered over a relational database, with built-in support for file management and CGI programming. The basic underlying data structure for all WIRM data is the repository object, a perl associative array whose values are bound to a row of a table in the relational database. Based on our experience implementing a target application (the Brain Mapper Console), we describe five stages through which a system passes as it evolves from a primitive file hierarchy to a full-fledged repository console.