Hi, Marshall: I read your email again and more carefully this time. I think I misunderstood what you meant by "previous selection". I am understanding you better now.
What you are looking for is essentially a staged filtering based on multiple features and their values. Such criteria are joined by "and" operator as condition for filtering. A typical example is a website like the following: http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=100008120%2050001183%2050001077%20600414917%20600414918&IsNodeId=1&name=129GB%20-%20256GB where the products are filtered by "manufacture" and "capacity" features. What I did was essentially a use case with filtering by a single feature. I think it would be very nice to have the capability to filter by multiple features and values. But it would be a major makeover of the annotation viewer. Shall we review and accept the current enhancement before we considering implementing the more advanced functionality? Thanks! James On Mon, Dec 9, 2013 at 7:51 PM, James Jichun Zhu <[email protected]> wrote: > Hi, Marshall: > > Thanks for the time looking at this enhancement. > > Yes, you are quite right about what the new feature does. The requirement > arose from an inconvenience when we use the annotation viewer to examine > the annotations in our work. For a certain type of annotation, we can > potentially have a large number of such annotation objects. So by filtering > them by annotation type is not sufficient to help us narrow down to the > specific annotations we'd want to examine in details. The enhancement I > implemented helps solve the problem. > > If we allow user to choose more than one type, and for each type to choose > more than one feature to filter by, then we may be looking at large number > of feature values mixed together from different types and different > features, which will be hard to render as checkboxes for user to turn > on/off. > > Since we have to highlight the annotations differently depending on the > current type, feature, and feature value chosen by user, if we still want > to keep track of user's previous selection of type, feature, and feature > value and somehow render them highlighted on the text pane, it can be > confusing to the user. It is also a challenge to render the previous user > selection of type/feature/feature values on the radio button and checkbox > panels without confusing with the current user selection of > type/feature/feature values. > > If you have any idea on designing the UI to allow the user to filter by > multiple types and multiple features' values simultaneously, and/or keep > track user's previous selection of type/feature/feature values, I will > happy to consider implementing it. > > Thanks again. > > James > > > On Mon, Dec 9, 2013 at 2:16 PM, Marshall Schor (JIRA) <[email protected] > > wrote: > >> >> [ >> https://issues.apache.org/jira/browse/UIMA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843613#comment-13843613] >> >> Marshall Schor commented on UIMA-3374: >> -------------------------------------- >> >> hi, I'm looking at this again. The new "features" mode has a usage >> pattern where the user >> 1) first selects a type >> 2) then selects a feature (of that type) >> 3) then selects one or more feature values (of that feature). >> >> What is shown is the colored annotations as before, but filtered by the >> selected feature -values. >> >> Is this correct so far? >> >> Is there a use case for selecting >> * in step (1) more than one type? >> * in step (2) more than one feature? >> >> It seems to me, that since the usage pattern is to do multiple >> specifications for the filter, that it would benefit the user to see on the >> screen some representation of their previous selection. (like many >> "shopping" websites do, now). WDYT? >> >> > A new mode for annotation viewer based on feature values >> > -------------------------------------------------------- >> > >> > Key: UIMA-3374 >> > URL: https://issues.apache.org/jira/browse/UIMA-3374 >> > Project: UIMA >> > Issue Type: Improvement >> > Components: InternalTools >> > Affects Versions: 2.5.0SDK >> > Reporter: James Zhu >> > Assignee: Marshall Schor >> > Priority: Minor >> > Labels: annotation, feature, filter, type, value, viewer >> > Attachments: CasAnnotationViewer.java, EntityResolver.java, >> screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg >> > >> > Original Estimate: 504h >> > Remaining Estimate: 504h >> > >> > I'd like to propose adding a new "view mode" in the UIMA Annotation >> Viewer so that user can pick a specific type of annotations, and then pick >> a specific feature, and pick specific feature values available so user can >> see a subset of those annotation objects that have the specific feature >> values. >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.1.4#6159) >> > > > >
