E.g. for us (EfA - in Germany) the feetback feature, with detaild and realistic amounts for each shop and each foodsaver, is crucial and we use it all the time.
Especially if so many foodsaving groups are working in a different manner
an algorithm to built an everage or what ever will confuse people, would make the system less detailed and correct but more complicated.
In our group we often pickup the staff with several persons and in most cases, about 90% will be carried e.g. to varous Kindergarden and so on. Only about 10% is for private use.
For example 3 foodaver are picking up the total amount of about 50 kg net weight of goods (excluding the rubish) in one market.
1 foodsaver is carrying 45 kg fruits and vegetable for Kindergarden No1,
1 is taking 5 kg chocolate for Kindergarden No2, the other foodsaver helped but carried 0 kg.
We would prefere, if everyone can state the real amount and may give comments.
Statistic should show 50 kg as tolal amount, and nothing else (not a total of 25kg and not a total of 15kg fruit-vege-late).
Oh, what a heated discussion! Iād like to take a step back and would be interested why the pickup weight is useful and/or important to you. That would help me a lot to implement good statistics
Pickup weights are quite importtant for us,
because we report exactly
how much and what we received from each market in total,
how much and what everyone of us has taken,
and how much and what we have given to each institution.
Since we are a registered non-profit organisation we are obliged to report that we spend most of the stuff we received.
A well working statistic-tool in karrot is the best instrument to proof our obligations.
Iām definitely not making a big deal of how the feature should be and how statistics should be collected, but Iām making a big deal of the following points:
Not every group works the same and we should take that into account when designing and changing this feature. Maybe we should ask for more input from other groups? If most groups would like amounts to be set individually then I see no problem; But, more importantly:
If you donāt get the semantics correctly, thereās no point in having this feature if people are not understanding and using it accordingly. It became clear that people were misled by some bad translation, and if the feature changes it should be clear on what exactly it is asking for when you set an amount and how it calculates. If changed, it should state āHow much food did you individually carry home or to a sharing spot?ā. That should do the work fine in groups where you require foodsavers to always give feedback (since one feedback missing might already affect considerably the outcome) and not so much on groups that like to use this feature just to have a rough estimate.
There are no explanations for the user in karrots.
The use is intuitive.
Therefore the rule for every feature should be āwhat you see is what you getā.
If every person of the pickup-team is asked for feedback by the system and all feedbacks of the members of a pickup-team are shown, the user must assume, that his feedback will be used āpureā, without any hidden or additional algorithm.
I guess the phrase @bruno is refering to is this one:
The German version is equally clear stating āMenge des insgesamt geretteten Essensā, whereas the Polish version indicates that itās just about the amount that you yourself saved. Just for contextā¦
(And Iād like to point out that intuition works differently from one person to the other. The use of this feature is the perfect example to illustrate that imhoā¦ )
Iām revisiting this topic just now and I thought a feedback export feature might be useful to you. You would be able to download a CSV file that you can import in LibreOffice or Excel. This would be per place or for the whole group.
You could use this file to calculate all kinds of statistics, e.g. weekly weight, average weight per pickup or weight per user.
Would it be also possible to extract CSV files with data other than feedbacks? E.g. history of pickups in a place or a history of userās actions, etc.?
Sure, we just need to figure out what columns the file should contain and which types to include. History data is a bit hard to work with because every type has its own payload/context.
Hey you statistics people! I released the first version of the CSV feedback export. Itās just a URL for now; there is no clickable link in Karrot (yet).
Iāve extracted a file for Foodsharing Warsaw (group=39) and successfully imported it into Excel which is great The only comment which I have is that a file doesnāt have CSV extension after downloading it. Itās an uknown format but it still works.
I find extract with feedbacks very useful but I donāt hide Iām really waiting for the extracts with history. Have you already had a chance to work on this? Maybe you have something which works to some extent but could already be used/tested?
Hey @mzpawlowski - I have a code branch that implements the basics, however I still need to rewrite old history entries to contain the same data as new ones and implement a fallback where this isnāt possible.
Chances are good that I will get around to do it in the next weeks, now that Iām almost done with upgrading Quasar, our user interface library. That took more than a month already and Iām looking forward to code something more fulfilling But it made pretty clear to me how much the Karrot grew in the last yearsā¦
)
The only comment which I have is that a file doesnāt have CSV extension after downloading it. Itās an uknown format but it still works.