-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show/export Flow instance usage #2612
Comments
Is the current simple CSV format ok, or should it be an Excel file? |
CSV file is fine, if we make the changes mentioned above to the data. This is a first iteration, so it does not need to be shiny-fancy. |
Do we want to filter the list to only contain the forms the user has access to? Or should this entire report be restricted to certain users? |
I would keep it simple for now and push all forms in the file. Can we restrict it to users who are admin's (user management)? Then we follow the pattern Lumen has where admins only see the usage stats Stellan, where do you think we should place it? I am a bit reluctant about pushing it under the data exports tab as I originally suggested as it might clutter the page. How about another tab under the Data tab? Or do you have other ideas? I also asked @Kiarii to give this some thought |
since we are looking for a quick turnaround, could we just add a "Stats" (or sth similar) page on the top menu just after "Messages"? I think we should separate the instance data from survey data, even if both are exported or downloaded in the same way.. It is also in that stats page that more info on the instance e.g. current package, expiry and so on, will go into in the future.. |
@stellanl if we agree to link the export to the user admin role, how much extra effort is it to add the logic to hide the new 'Stats' tab if the user does not have that permission? If it is too much effort, could we add a subtab 'Stats' under the main 'Users' tab, then the permission will be respected? |
Does not sound very hard to me. Should be able to cut-and-paste the code that hides the users tab. |
Sounds good @stellanl. Let's keep this issue to the minimum and create a new one for your suggestion on using the /rest API |
Here is a report on the dev datastore: |
As agreed w Emmanuel, I will not make a copy-pasted UI in Ember, but make that part a separate issue. |
Any privacy issues with counts from the uat1 datastore? If not I can put an example of the slightly enhanced report here. |
Can you drop the file in the Akvo team Google drive somewhere and share the link? Just to be sure |
@stellanl I took a look at the file shared and have a few remarks. Good initiative on adding the extra stats. Let's see if users find them useful and request more ;) :
|
The first line of the sheet also contains the date range (if selected). I could put that somewhere else, of course. |
I see. Then leave the 1st row as it is. Users can always delete it themselves, just instead on Form instance' let's use 'Form submissions'. |
Issue/2612 usage report (Connect #2612)
[#171]Bump version to pick up akvo/akvo-flow#2610.
So one comment I also made on the UI side of things, currently when you load the Stats page of the UI, it retrieves all reports including the comprehensive, raw data and statistics reports. I think it makes sense to update the reports endpoint slightly and only be able to query for reports of a specific type. e.g. |
All done here! 👍 |
Context
Our SaaS pricing model is based on the number of submitted forms. For the partnership team to be able to track their accounts and for partners to know how much they have spent, they need to be able to know their usage status. Furthermore, sometimes a Flow instance is owned by a partner, who shares it with other organisations. These then contribute to the SaaS payment but the owner organisation then needs to know how many submissions these partners made.
So for Petra, it is important to understand their usage in the context of the contract and how they capture data in general. She also is interested to see the uptake of the product per project. Salim is interested in seeing which forms are being used and how heavily.
Problem or idea
Today Salim and Petra have no easy way to know:
Currently, @stellanl has a script he can run per instance that gives a csv file with the survey path, form name, form ID and number of submissions. This however needs to be requested creating an unnecessary communication pipeline and Stellan needs to run it causing Stellan more work and breaking his flow and deep focus.
Opportunity 1 - download sheet with usage breakdown
The idea is to improve Stellan's sheet and create an option to export the file in the UI through which any user can export the usage per form per a specific period of time.
In the Sheet we should:
User experience:
Opportunity 2 - UI overview + download option
Later we should consider to create a way to see usage in the UI and from this page to be able to download the breakdown overview.
Far future
In the future, how might we take it further and bring their usage in relation to their pricing plan? How can Petra, as a Flow user know how many forms I have left from my contract period without having to contact Akvo?
The text was updated successfully, but these errors were encountered: