Page History

...

• visualizing the collected information
  In this documentation, we will focus on the GUI part of the visualization from the end-user's perspective.

2. Development Process

The development will be done as a tooling project of Apache UIMA with the participation from the community. Since there are a lot of codes in the CAS Viewer (submitted as a contribution to Apache UIMA) that can be reused, we propose to develop the visualization of CAS/Index Journal as the extension to the CAS Viewer.

3. Proposed User Interface

In the following proposed GUI mockup, we use "deploy/as/MeetingFinderAggregate.xml" from uimaj-example of the UIMA AS package with some modification to its behavior to illustrate the design. This aggregate AE has the following structure:
    MeetingFinderAggregate
        Collection Reader
        TokenAndSentence AE
        MeetingDetector Aggregate
            RoomNumber AE
            DateTime AE
            Meeting AE
        Cas Consumer
 
We assume that, after running MeetingFinderAggregate with an input document, the following basic information is produced:
 (1) A list of calls to AEs
 (2) Within the call to each AE, a list of new FSs created by this AE and a list of modified FSs
 (3) Within the call to each AE, a list of add/delete/modify FS operations to index repository
 
The issue here is how to visualize the above three kinds of basic information to the developers?

Note that, for the initial implementation, we propose to only preserve the final value for a FS (intermediate values are not kept).
 
Based on the above example and assumptions, the following shows some screen-shots of the proposed GUI used to visualize the journal information.

3.1 Viewing Changes to CAS

The information about CAS changes is visualized by the FS Journal tab as shown in Figure 3.1.
The sequence of AE calls is showed in the top section of the tab and is organized as a hierarchy (the key string defined in the aggregate descriptor will be used to identify the AE). The number next to the AE's name is the total number of FSs added or modified by the AE. For example, "Meeting AE (2 FSs)" means that there are two FSs added or modified by the Meeting AE.