The score service “listens” for events such as a blog post rating or a new page view, then recalculates the scores they relate to. The service supports community engagement reflecting participation and quality.
- The score service is used by other services (including like or rating) to measure content value in the context of social engagement.
- The score service is part of the core functionality of this release.
The score service is the glue that holds other core services together and creates meaningful comparisons with them. Users rely on scores such as Author Quality or Content Quality to gauge the correctness of content or the expertise of authors. Users are also encouraged to contribute their own content, to ask/answer questions, and blog.
The score service measures (with metrics and score modifiers such as weight and decay) the content quality; author quality; and member engagement with content. Scores are used to rank members in widgets like Users - Top Quality Author Groups widget or to rank higher quality content in search results.
Scores consist of metrics, which can be added or removed and weighted according to community requirements for a customized score. For example, a Content Quality score is partly derived from metrics such as bookmarks; comments; downloads; being featured; forum replies; likes; ratings; suggested answers; tags; user subscriptions; verified answers, and views.
The weight (influence) of a metric within a score is configurable on a sliding scale(from lower to higher) that determines its relative importance. For example in a gaming community, you might weight the download and like metrics more heavily (that is, higher on the "more" end of the slider) than you weight views. (The screen capture shows the slider in the "normal" range, which is the default for all metric weights.)
Metric weight can only be set at the site level for the entire community; it's not configurable at the group or application level.
Decay is another component in scores. This tool is designed to counter content stagnation by reducing scores over time - older content can have lower scores than newer content and thus newer content places higher in search results.
If you enable decay, it uses a value called half life to determine when the score is automatically reduced. For example, a forum post that initially receives a high content quality score would have that score reduced by 1/2 after it has aged to the specified half life. The default decay half life is 30 days, but this can be changed.
The default decay half life is 30 days, but this can be changed. You can set the decay rate for a score at the site level - for example, you might want to age author quality more slowly (thus setting a longer half life such as 90 days) than you would age content quality (by specifying a lower half life number such as 30 days).
An underlying premise of reputation is that community participation affects community quality - whether by surfacing high-quality authors (author quality score) and content (content quality score) in search, or maintaining the integrity of the community by reporting (abuse reporter score) and evaluating spam (abuse creator score).
Zimbra Community 8.0 has two widgets that list and group users on the basis of quality scores and allow community members to click through to profiles, mentions, and groups:
- The high-quality authors in a group are listed by the Group - Members List widget configured for sorting by group author quality score.
- Groups in which the author is a top-quality author are listed in the Users - Top Quality Author groups widget.
To learn about developing with the score service, please see this article.