Hi WikiJournal participants,
Following is the latest report of incoming links by doi codes to our
journals (then registered at Crossref as Wikiversity Journal of Medicine).
Numbers may at least partially be due to web crawlers, but hopefully point
towards an increase in readership lately.
I am now forwarding these reports automatically upon reception to
*Wiki.J.Med(a)gmail.com
<Wiki.J.Med(a)gmail.com> as well for easier future access by WJM board
members. Let me know if you want it likewise forwarded to additional
emails.*
Best regards,
Mikael
---------- Forwarded message ---------
From: <reports(a)crossref.org>
Subject: Resolution Report for prefix 10.15347 from Jun 6, 2019
To: <haggstrom.mikael(a)wikiversityjournal.org>
*Report for Publisher: Wikiversity Journal of Medicine*
*Resolutions for last 12 months.*
We continue to filter out known search engine crawlers. This month they
accounted for 99,820,994 resolutions.
Months 2019-05 2019-04 2019-03 2019-02 2019-01 2018-12 2018-11 2018-10
2018-09 2018-08 2018-07 2018-06 2018-05
Resolution Attempts 11,395 6,881 6,895 7,494 10,669 12,600 12,270 7,780
4,154 2,036 1,878 1,970 1,554
Resolution Successes 10,987 6,607 6,601 6,938 9,975 12,217 11,885 7,394
4,005 2,027 1,845 1,934 1,499
------------------------------
Total Attempts for all members 395,623,227 369,900,409 436,382,337
299,293,001 298,166,923 319,180,558 352,053,795 447,061,465 343,575,811
355,450,288 291,322,494 247,013,737 278,309,967
------------------------------
The overall resolution failure rate for all publishers is 4% and your
failure rate is 3%. These failures may result from deposit errors by the
publisher or from linking errors being made by end users. If your rate is
significantly above zero or the overall average please investigate to
determine the cause.
------------------------------
Top 10 DOIs Resolutions to DOI
10.15347/WJM/2017.003 <https://doi.org/10.15347/WJM/2017.003> 787
10.15347/WJM/2014.010 <https://doi.org/10.15347/WJM/2014.010> 731
10.15347/WJS/2019.003 <https://doi.org/10.15347/WJS/2019.003> 514
10.15347/WJM/2017.002 <https://doi.org/10.15347/WJM/2017.002> 507
10.15347/WJM/2019.001 <https://doi.org/10.15347/WJM/2019.001> 443
10.15347/WJS/2018.006 <https://doi.org/10.15347/WJS/2018.006> 437
10.15347/WJM/2017.007 <https://doi.org/10.15347/WJM/2017.007> 417
10.15347/WJM/2017.008 <https://doi.org/10.15347/WJM/2017.008> 416
10.15347/WJM/2017.001 <https://doi.org/10.15347/WJM/2017.001> 413
10.15347/WJM/2018.001 <https://doi.org/10.15347/WJM/2018.001> 388
------------------------------
Resolutions attempts 11,395
Resolved at Handle 10,987
Handle Failures 408
Resolved at local link server 0
Unique DOIs attempted 93
Unique DOIs resolved at handle 48
Unique DOIs that failed at handle 45
Unique DOIs resolved at local link server 0
------------------------------
Resolution Counts by Publication Title
Publication Title Total Resolutions Unique DOIs
WikiJournal of Humanities 697 5
WikiJournal of Medicine 5,986 30
WikiJournal of Science 4,304 13
The failed DOIs for the most this month can be viewed in a csv format by
clicking here
<http://data.crossref.org/members_only/resolutionReport/10.15347_unres_2019-05.csv>
.
CrossRef has created a system to automatically email publishers statistics
on the number of DOI resolutions through the DOI proxy server (
https://doi.org/) on a month-by-month basis. These numbers give an
indication of the use of your DOIs and the traffic coming to your site from
users clicking DOIs. The DOI links are largely from links in other
publishers' journal references to your articles, but they are also from DOI
links in secondary databases, links from libraries using DOIs, and even
DOIs in used in print versions.
When a researcher clicks on a DOI link for one of your articles, that
counts as one DOI resolution. A DOI resolution is when a DOI is "clicked" -
for example, clicking on
https://doi.org/10.1038/nature02426 counts as one
resolution to Nature. No information is captured about who the user is or
where they are coming from. The information on DOI resolutions is captured
by the web server logs on
https://doi.org/ which is run by CNRI on behalf
of the International DOI Foundation. These numbers are not a precise
measure of traffic to your site - cached articles, search engine crawlers
not following re-direction and traffic that is directed to a locally
appropriate copy through a library link resolver would be included in these
numbers, but would not result in inbound traffic on your website.
Nevertheless, these numbers provide one important measure of the
effectiveness of your participation in CrossRef.
In March 2004, the report on DOI resolutions through the main
https://doi.org/ proxy server was updated. This report now tracks the
number of DOI resolutions based on the owner of a DOI:
- Resolutions : attempted resolutions of DOIs based on the owner of the
DOI.
*Top 10 DOIs* is a list of the most popular DOIs that were successfully
looked up and how many times each was looked up.
*Resolution attempts* is the same at total "Resolutions" above.
*Resolved at handle* is the number of resolutions that successfully looked
up at
doi.org.
*Handle failures* is the number of resolutions that failed to look up at
doi.org, either due to a technical problem or because the DOIs did not
exist.
*Resolved at local link server* counts resolutions that were looked up at
local link servers.
*Unique DOIs attempted* is the number of unique DOIs represented in the
total "resolutions attempted" from above.
*Unique DOIs resolved at handle* is the number of unique DOIs represented
in the "resolved at handle" count from above.
*Unique DOIs that failed at handle* is the number of unique DOIs
represented in the "handle failures" count from above.
*Unique DOIs resolved at local link server* is the number of unique DOIs
represented in the "resolved at local link server" count from above.
The attached file, if present, contains all of the DOIs that failed to
resolve followed by the count indicating the number of times that DOI was
attempted.
*"na" - means that data is not available for that month and type. *
If you have problems with this report, contact support(a)crossref.org.