Feature hierarchy

2 posts, 0 answers
  1. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 15 Nov 2012 Link to this post

    Currently your Analytics supports only 2 level hierarchy, where every feature has one category - FeatureCategory.FeatureName. I guess that more than 2 level hierarchies are in your roadmap but if there is a way to simulate such behavior I would be glad if you share it with me. Let's assume that when I say command I mean feature. So I need to know whether a command (feature) had been executed from the UI menu or from a keyboard shortcut. Also the commands (features) are divided in categories. That means a hierarchy of 3 levels. In this case we will need to have 2 kinds of report. The first kind will be of type ExecutedFrom.CommandCategory (statistics about command categories executed from the UI menu or a keyboard shortcut) and the second will be CommandCategory.Command (separate statics about commands executed for each category) Thank you in advance for the assistance.
  2. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 15 Nov 2012 Link to this post

    Hi Rumen We've had requests for deeper feature hierarchies in the past so it is on our radar for sure. Allow me to paraphrase your scenario to make sure that I understand what you want to achieve and how our solution limits you from doing this: What you really want to register is a feature named ExecutedFrom.CommandCategory.Command for a number of different values of ExecutedFrom, CommandCategories and Commands (for instance "Keyboard.File.SaveAs", "UI.File.SaveAs" or "UI.Edit.PasteSpecial") and be able to both get a distribution for the different commands executed with a specific category (e.g. File.SaveAs, File.Save, File.Open) as well as the categories from the execution origin (Keyboard.File, Keyboard.Edit vs UI.File, UI.Edit). However, as our own solution only groups items using a single level you are unable to get both of these. Does this sound about right? Our current implementation uses the 2 level dotnotation in our to provide conviniently grouped features out of the box. You are however able to design your own view of your data by picking out the specific individual features that you would like to have visualized and you can aggregate multiple individual features into a single item. All this functionality is available under the Feature Views report where you can create a new View (note that you need to be an Administrator to do so) where you can select a number of features that you want to aggregate into a single item and another number of features to aggregate into a second item. These will then be shown as two items in a chart. From my understanding of your scenario, you would be able to design the views described above. It does require a bit of manual work to go and pick out the individual items (and it is something that we want to improve on by e.g. providing a searching ability when selecting items) but you should be able to group the existing feature registration into meaningful aggregates (based on similar categories or execution origin) and have the items plotted. We realize that picking out your own visualization is a very static and manual process (and we really want your feedback on improving this) but as for the current state of our service, this would be our recommendation. Hope this helps Best regards Soren EQATEC Team
Back to Top