-
Notifications
You must be signed in to change notification settings - Fork 1
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
Is the tags count correct? #7
Comments
I have used a simple (to not say dumb) request to get the number of tags (and users) and did not checked if they were used, so 1414 is actually the total number of tags existing within the db (as imported from ER), not just the ones used. I will correct this shortly. I can explain the difference in the number of comments as some appears to not have existing parent (post or comment) when imported. Those elements are thus ignored to avoid discrepancy in the database. Do you want to have the number of annotations available with the stats? |
Re tags: OK, that explains it. Re number of comments: can you make an example (need the number of comment id)? Re annotations: yes please. |
The comments all seem to be pretty old (~5years from what I can tell) so I am guessing their parents are not considered as elements of the Opencare project. Here are all the problematic ones: |
Got it. So:
|
I see @jason-vallet has added a list of stats as per #3 . However, I am worried that the number of tags may not be correct. I have my own script that returns a very different number: 3,915 annotations (not computed by the dashboard) with 867 codes (dashboard says 1,614).
There are also small differences in the numbers of comments (my script says 1,688, GraphRyders says 1,633) and users (my script says posts (my script says 316, GraphRyders says 318) The number of posts is the same: 352.
My script for annotations:
The logic is that MySQL returns a lot of duplicates, and even distinct does not always work. So I need to build these checklists of entities I already encountered, and for each entity returned by the view check that it is not already there.
The text was updated successfully, but these errors were encountered: