Here’s just a note on what I’ve found out:
- community rating is a float with 1 d.p. (i.e. 3.5, 4.6, etc.)
- you can set rating:2.1. If you set rating:2, you’re going to miss out all other ratings that might have been round off to 2. i.e. rating:2 doesn’t include 1.9, etc.
- currently comparative operator doesn’t work on community rating. I consider that as a bug: https://community.logos.com/forums/t/179258.aspx
- using 4904 resources as a sample, one can find the PDF and KDE of this:

Logos Community Rating PDF and KDE
This clearly shows 2 clusters, and one can use it to “discern between good and bad” and added that as a collection rule or search rule for example. (Only if the bug mentioned above is fixed, to facilitate the use of rating>2.1
)
The original data is manually entered by filtering using Library. This is an example of what would becomes much easier to do if scriptable API to interface with Logos is provided. (Imagine this analysis is updated when new resources are added, and also community ratings themselves are updated.)
P.S. if one pays very close attention, there might have been 3 clusters. Or it may just be noise. Can’t tell unless more data is fed!