-
Notifications
You must be signed in to change notification settings - Fork 10
View analytics reports for subset of all pages (ability to filter). #28
Comments
First off , we have wanted to build this kind of functionality for some time - so we have had some concepts in mind for a while... I have looked at the PRs and I think we should discuss your proposal. We have had many ideas on this and I think we can - with very little effort add a I imagine there would also be a I'm happy to create the models I have in mind here if you like. Feel free to follow up with a meeting to discuss with myslef and @ecumike |
Thank you for the feedback! Have just seen the message, and think this makes sense. For a chance to meet, there is one meeting that Ann Marie Fred, Tim Figgins, and I are planning to have today at 10:00 AM to talk about filter functionality at large. Do you think that time would be good for us to discuss also? I apologize for the short notice on that, and of course we could meet at a different time if it would work better Before that time, I will begin to experiment with model-based approach, and hopefully would have something toward that goal to share by then. Thanks again. |
Some of this is internal implementation details, but stepping back from a usability perspective, a simple substring match is the easiest for people to understand. For example:
The trick is in figuring out how the framework can allow for that type of filtering, without it getting too specific to our company internals. |
Would like please to share an initial "gist" or sketch of new models based on comment above. Are these similar to the approach you are thinking about?
Have added an initial one as a test, using some new properties of |
For example, added a temporary property that is pathname0 inside
Please note that this hard-coded way of setting these |
Let me create a PR later today / tomorrow to illustrate. I think the filtering data should be persisted |
That sounds good, thank you! Would like please to confirm, it is correct that this would be replacement for, not a companion to, the current proposal? In other words, are there parts of the existing P.R.'s we would want to retain/use, or should they be closed instead? |
I'll make the models and we can then meet to discuss @rcalfredson I have something working now in #36 if you want to schedule a technical discussion with me, @ecumike and yourself. |
Yes, thank you, that sounds good! Have already been working with the code, and the approach is clear to me. Would you want to meet for it today? I have complete availability. |
I wanted to mention that the service and UI of this new functionality should look like this: a view is created to list all of the Each filter corresponds to a url and view that produces the dashboard at the UrlFilter's name: /url-filters/my-url-filter-for-such-and-such we want to use slugs for the names and make them unique In the UrlFilter view function we have a very simple operation:
The dashboard generation code may need to be pulled into a helper function |
Closing. In |
Agreed, the filters are working. Looking forward to the "AND" and "OR" functionality next! |
Currently, analytics reports aggregate result from all pages. In addition to this existing functionality, users may want a way to specify a subset they would like to analyze.
There could be a variety of ways to specify the desired subset of pages. For example, perhaps users would like to filter down to URLs containing a given subset, or perhaps they would like to input a comma-separated list of URLs they know in advance.
It would be possible for the user to view the dashboard, the report-card tiles and the detailed page summaries using that filtered list.
The text was updated successfully, but these errors were encountered: