PM Point System
PM Point System
PlanetMath Point System - Draft Version
February 9, 2018
This portion contains the various rules on how points are awarded to or deducted from users. (mostly adapted from
The PlanetMath Point System is developed to motivate the PlanetMath users to actively participate in the PlanetMath community in a positive and productive manner.
A user starts with points in his/her account when he/she first signs up with PlanetMath. Each time a user earns points due to a given activity, the points are added to his/her account.
The way the point system works is by having a basic set of “base points” awarded to basic activities (defined below) done on PlanetMath. In addition, more complicated awarding schemes are used with more complex activities.
Certain activities can result in points being forfeited. When such a case occurs, negative points are awarded.
2 Base Points
The following table describes the basic activities and the corresponding base points awarded.
|basic activity||base point|
|addition of a publishable encyclopedia entry||100|
|addition of a publishable non-encyclopedia entry||20|
|addition of a non-publishable entry||10|
|addition of a book||100|
|addition of a paper||50|
|addition of an exposition||75|
|addition of a forum post||1|
|voting in a poll||1|
For example, if a user writes three entries, one is publishable encyclopedic, one is publishable non-encyclopedic, and one is not publishable, the total number of points earned by the user based on the addition of these three entries is 120.
A user may earn additional points based on additional activities that are done to past activities. For example, if a user revises an existing PM entry, certain points may be earned as a result of this activity. The past activity, in this case, is the addition of the original entry. The user does not have to be responsible for both activities to earn the points (please see examples below). Currently, PlanetMath only has provisions for a point system for past activities that are related to entry contribution.
Below is a table that shows the activities and the corresponding additional points that can be earned by a user.
|correction accepted (erratum)||30|
|correction accepted (addendum)||20|
|correction accepted (meta or minor)||10|
|revision of a publishable encyclopedic entry||5|
|revision of a entry that is neither publishable nor encyclopedic||0|
|minor administrative edits (??)||5|
Below are some examples illustrating how the additives work:
A user revises two of his own entries, one publishable encyclopedic, one not publishable: total points earned .
A user revises two publishable entries, one encyclopedic, one non-encyclopedic, neither of which he owns: total points earned .
A user files two correction notices, one of which is minor and is accepted, the other is major (erratum) and is rejected: total points earned .
4 Points associated with an entry
The evaluation of points can be based on a specific object. In most cases, this object is a PlanetMath entry. For example, if publishable encyclopedic entry is added, and two revisions are made to it, then the points associated with that entry is .
Below, we will see some more complicated examples of evaluation of points associated with an entry.
5 Reclassification of an Entry
If an entry is reclassified, the points associated with the entry will be scaled to correspond to its new classification. Define the state of an entry by the pair where denotes whether it is encyclopedic or not, and denotes whether it is publishable or not. Any entry can be in any one of four states at any time of its lifetime.
Given a state of an entry, we associate it with a number, called a scaling factor. The following table shows the matrix of scaling factors:
The way to find the scaling factor of an entry given its classification is evident from the above matrix. For example, if an entry is publishable and non-encyclopedic, its scaling factor is 2.
In order to calculate the points gained (or lost) as the result of a reclassification, do the following:
Let be the points associated with the entry prior to reclassification
Let be the scaling factor of the entry prior to reclassification
Let be the scaling factor of the entry after reclassification
The points gained is
For example, an entry, currently classified as non-publishable non-encyclopedic, and is worth 5 points. Its user changes it to publishable encyclopedic. The points awarded is . It is easy to come up with examples where a user would lose points due to reclassification.
6 Transfer of an Entry
When an entry is transferred from one user to another, some points are transferred from one to another correspondingly. More precisely, the person losing the entry loses “some” of the points associated with the entry, while the person gaining the entry earns the points lost by the other.
Transfers can occur in three ways:
A user voluntarily transfers his/her entry to another user
A user orphans or abandons his/her entry, and the entry is picked up or adopted by another user later
An administrative confiscation (takeover) of an entry from a user.
The exact way “some” is calculated is as follows: find the base points associated with the entry to be transferred in its current “state” (defined in the previous section). Let this number be . Then the person losing the entry will lose
points, while the person getting the entry will receive points.
Below are a series of examples illustrating how transfer works:
For example, if an entry is transferred from to . At time of transfer, it is worth points. However, its state is publishable non-encyclopedic. As a result, only points will be transferred. In other words, will lose points, while will gain just points.
Continuing from the example above, if changes the entry from publishable non-encyclopedic to publishable encyclopedic and transfers it to , then loses points and gains points in the process.
orphans the entry. Just prior to orphaning it, the entry is publishable encyclopedic. Therefore, will lose points. The points remains with the entry, until picks up or adopts the entry later. He will then receive the points.
7 Entry Deletion
If an entry is deleted, most of the points associated with the entries are deleted. The “most” portion is calculated as follows: find the base points of the entry at its current state prior to deletion, let this number be . The points to be deleted are
where is determined by the following schedule
|entry originally added by|
Below are two examples illustrating how this works:
User deletes one of his entries, written by himself. When it was first written, it was non-publishable and non-encyclopedic. Just prior to deletion, its state is publishable encyclopedic. He will thus lose points.
As in the previous example, if the entry was adopted or transferred to from user who first added the entry. will lose points instead.
Again, as previously, if the entry was transferred back to , who wrote the entry originally, then will lose points.
8 Points associated with an entry - Revisited
With the additional situations (reclassification, transfer, deletion), it can be a bit tricky to calculate the number of points a user has associated with a given entry. We give one long example to illustrate how the points associated with an entry are calculated.
An entry is created by user , initially set as non-publishable encyclopedic. After two revisions, the entry becomes encyclopedic. Subsequently, three additional revisions take place, one as a result of self edit, two as a result of correction notices received by others. The entry is subsequently transferred to user , who makes a single revision.
How many points associated with the entry does each user have?
Solution. earns 10 points for initially adding the entry as non-publishable encyclopedic. Two revisions later, the entry is still worth 10 points. When the entry becomes publishable, however, the entry is worth 100 points. Three additional edits result in 15 points added to the entry. Before the entry is transferred to , it is worth 115 points. After the transfer, loses points and gains points. When makes an edit on the entry, 5 point is awarded to him. So, in the end, has points and has points.
If transfers the entry back to user , how many points associated with the entry does each user have?
Solution. When transfers the entry back to , he loses points since at time of transfer the entry was publishable encyclopedic. After the transfer, has points and has points.
If deletes the entry instead, how many points associated with the entry does each user have?
Solution. Again, since the entry was publishable encyclopedic prior to deletion, loses points, since he did not add the entry in the first place. In the end, still has points, and only has points left.
Interestingly, if transfers the entry back to and deletes it, then only has points left and still just has points.
9 Cash Cow
Administrators: the last example in the previous section leads to an interesting cash cow (loophole) in the PM system, and it seems like this loophole also exists in the current PM system. Please correct me if I am wrong, as I am going to exhibit some examples.
Users and are good friends. Neither one of them really want to work very hard. They figure out a way to earn PM points without contributing to entries. writes an entry worth 100 points. He transfers it to and asks to delete it for him. In the end ends up with points. Later asks to do the same thing for him too, so also ends up with points. Neither of them own any entries, and they both end up points more.
Possible fix 1: When a transfer of entry occurs, do not apply the factor to , but use all of instead (refer to section 6 on detail on transfers). Furthermore, when deleting an entry, again do not use , but use in all cases (refer to section 7 for detail on deletion).
However, the possible fix 1 does not really fix the problem. We have users and again. User writes a bogus entry initially worth 100 points. He makes 10 empty edits himself and transfers it to . He loses 100 points as the result of Possible fix 1. But he retains points from the edits. deletes the entry for him, so is left with points. does the same later and he receives points. Again, neither of them have any entries left but they are points richer.
Possible fix 2: In addition to Possible fix 1, a transfer of entry should also transfer all points associated with the entry at time of transfer.
In other words, the PM system has to be able to figure out exactly how many points are associated with every entry now. I am not sure the PM system has that ability now. If not, it will be a desirable thing to have, because I think Possible fix 2 will solve the Cash Cow problem.
Moved Point System from the PM Community Guidelines (6-16-2007) –[[Cwoo]]