<?xml version="1.0" standalone="yes"?>
<Paper uid="W02-1901">
  <Title>Scenario forms for web information seeking and summarizing in bone marrow transplantation</Title>
  <Section position="3" start_page="0" end_page="0" type="intro">
    <SectionTitle>
3 Implementation
</SectionTitle>
    <Paragraph position="0"> Nearly the whole user interface is coded in JavaScript. The scenario interpretations and the ontology are stored in an XML database. For processing, scenarios are transferred with the user input in an XML structure defined by a general DTD describing the common pattern of all scenarios. After processing the user input, for every field marked as a question, extracts of the retrieved documents as well as links to the corresponding full text documents are inserted in the scenario structure. In this way, exactly the same data structure is used both for  age (patient, 21- 50) &amp; treatmentCharacteristic (allogeneic BMT) &amp; timeperiod (bone marrow transplantation, , &gt; 12) &amp; suffer (patient, acute GvHD grade 1) ist (age (patient, 21- 50) &amp; treatmentCharacteristic (allogeneic BMT) &amp; timeperiod (bone marrow transplantation, , &gt; 12) &amp; suffer (patient, acute GvHD grade 1) &amp; isMainDisease (patient, chronic myelogenous leukemia) &amp;  At the time of writing, our current scenario library comprises 40 scenarios. We expect to have a manageable set (less than 100 of them) when we finish. They serve recurrent situational structures. A catch-all scenario deals with cases where no prefabricated scenario is appropriate. It passes users to PubMed and Google.</Paragraph>
    <Paragraph position="1"> Our BMT ontology currently comprises about 4400 concepts, 2800 propositions, and some 1400 contexts. This should be mentioned, since the ontology is crucial for the usability of the system and the user interface.</Paragraph>
    <Paragraph position="2"> Scenario engineering is carried out in cooperation with a BMT specialist. We adhere to formative evaluation (Scriven, 1967). Currently, we are starting retrieval tests. Summarization trials will follow. A serious restructuring that will change the usability features of the interface is envisaged for later when we shall move it to a mobile hand-held device.</Paragraph>
    <Paragraph position="3"> Conclusion In this article we have shown how user-based scenario forms support users' interaction with information during information seeking. Thus we comply with a core requirement for user-centered information-seeking interfaces, and we manage to obtain structured questions that set up a reasonable target structure for multi-document summarizing.</Paragraph>
  </Section>
class="xml-element"></Paper>