You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Someone who is maintaining a lab website may want articles that score only with a very high level of evidence whereas a librarian who is troubleshooting ReCiter might want to see all possible articles.
We're going to be mucking about with ReCiter evidence scores for quite some time, so we want to shield users from the change in scores as we optimize the value of the evidence constants.
The way we do this is through transforming raw scores into standardized scores.
totalArticleScore-nonStandardized - score of individual article
totalArticleScore-standardized - range of score 1-10; rawIndividualArticleScore can be mapped to a standardizedScore using the lookup table in application.properties (see below)
Workflow
Prerequisite: As described in issue #232, we computed totalArticleScore-nonStandardized.
For each individual article, map to a totalArticleScore-standardized.
Here's how:
Find the highest standardizedScoreMapping where standardizedScoreMapping >= totalArticleScore-standardized.
Lookup the totalArticleScore-standardized.
Example: an article has totalArticleScore-nonStandardized-excludingFeedbackScore = 8.4. That would map to this row in application.properties, because 8.4 > 8, but < 10:
totalArticleScore-standardized:8,7
Therefore, the totalArticleScore-standardized is 7.
The text was updated successfully, but these errors were encountered:
Background
Someone who is maintaining a lab website may want articles that score only with a very high level of evidence whereas a librarian who is troubleshooting ReCiter might want to see all possible articles.
We're going to be mucking about with ReCiter evidence scores for quite some time, so we want to shield users from the change in scores as we optimize the value of the evidence constants.
The way we do this is through transforming raw scores into standardized scores.
Properties
Include these in application.properties:
Variables
Workflow
Prerequisite: As described in issue #232, we computed
totalArticleScore-nonStandardized
.totalArticleScore-nonStandardized-excludingFeedbackScore
.Here's how:
Example: an article has totalArticleScore-nonStandardized-excludingFeedbackScore = 8.4. That would map to this row in application.properties, because 8.4 > 8, but < 10:
Therefore, the totalArticleScore-standardized is 7.
The text was updated successfully, but these errors were encountered: