{'fraction_non_alphanumeric': 0.021331058020477817, 'fraction_numerical': 0.0, 'mean_word_length': 5.445054945054945, '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}}
WHEN USERS MEET TECHNOLOGY: THE MEETING BROWSER DEVELOPMENT HELIX

This paper shows how the task of assistance to fact-finding has gradually become central to the field of meeting browsing. Requirements elicitation studies could not lead alone to a precise specification, because they depend on the preliminary assumptions of each study. Therefore, user studies were gradually focused towards the most promising task, namely fact finding or verification in multimedia meeting recordings. This task answers significant user needs, has enough theoretical interest, and is within reach of current technology, as illustrated by a variety of meeting browsers, including end-user products for conference recording and browsing. Assistance to fact-finding has been evaluated using the Browser Evaluation Test, and a set of reference scores are now available. The analysis of these findings departs from the view that a system’s lifecycle forms a closed loop, alternating requirements elicitation with design, implementation, and evaluation. Instead, the paper proposes a helix model that moves forward towards more and more refined systems, sometimes branching out to a new task.