Skip to content
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

Clarify the description of the contract value distribution #42

Closed
jpmckinney opened this issue Mar 9, 2020 · 6 comments
Closed

Clarify the description of the contract value distribution #42

jpmckinney opened this issue Mar 9, 2020 · 6 comments
Assignees
Labels
dataset checks Relating to dataset-level check pages documentation Improvements or additions to documentation
Projects
Milestone

Comments

@jpmckinney
Copy link
Member

The double usage of percentages confuses people:

The sum of the top 1% of tender values doesn't exceed 50% of the sum of all tender values.

We can try using words like 'rank' or 'percentile' – or split the description into 2-3 sentences to describe the steps of: ordering values, summing all values, summing top 1% values, making comparison.

@hrubyjan
Copy link

Any suggestions? Feel free to update it in the source code @jpmckinney. I think you have rights to created merge requests and even merge those :)

@jpmckinney
Copy link
Member Author

Instead of:

The sum of the top 1% of tender values doesn't exceed 50% of the sum of all tender values.

Make it:

The sum of tender values in the 99th percentile is greater than the sum of the remaining values.

@duncandewhurst @yolile What do you think of?

@duncandewhurst
Copy link

I think people are more likely to understand % than percentile as the former is commonly used but the latter requires some (basic) knowledge of statistics.

How about:

The sum of the top 1% of tender values doesn't exceed the sum of the remaining values.

Alternatively, I think this is easier to read but leaves the ranking by value somewhat implicit:

The total value of the top 1% of tenders doesn't exceed the total value of the remaining tenders.

Another option could be to provide a more 'plain english' description which sacrifices some accuracy before the more accurate description:

The value of the biggest tenders isn't out of proportion to the rest of the tenders: the sum of...

@jpmckinney
Copy link
Member Author

jpmckinney commented Sep 30, 2020

The 1st and 2nd options are fine with me. The UI is presently for trained analysts interested in precise methodology – not for less technical users who just want a general description of the check.

@yolile
Copy link
Member

yolile commented Sep 30, 2020

The 1st and 2nd options are fine with me.

Same!

@jpmckinney
Copy link
Member Author

@hrubyjan Let's go with:

The total value of the top 1% of tenders is less than the total value of the remaining tenders.

@jpmckinney jpmckinney transferred this issue from open-contracting-archive/pelican Sep 14, 2021
@jpmckinney jpmckinney added dataset checks Relating to dataset-level check pages documentation Improvements or additions to documentation labels Sep 14, 2021
@jpmckinney jpmckinney added this to To do in Pelican via automation Sep 14, 2021
@jpmckinney jpmckinney moved this from To do to In progress in Pelican Sep 14, 2021
@jpmckinney jpmckinney added this to the Cleanup milestone Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dataset checks Relating to dataset-level check pages documentation Improvements or additions to documentation
Projects
No open projects
Pelican
In progress
Development

No branches or pull requests

4 participants