Journal coverage in production is calculated for ISSN, and in staging for journal id
Background
In production, all coverage statistics for a journal are calculated for a given ISSN. For example, coverage for ISSN 1762584X (https://api.crossref.org/journals/1762584X) reports 41 DOIs in total:
"counts": {
"total-dois": 41,
"current-dois": 0,
"backfile-dois":41
}
This is consistent with requests:
https://api.crossref.org/journals/1762584X/works -> 41 results
https://api.crossref.org/works?filter=issn:1762584X -> 41 results
In staging, coverage statistics for a journal are calculated for journal id rather than ISSN. ISSN 1762584X belongs to journal 27878. In staging, in coverage we have (https://api.staging-legacy.crossref.org/journals/1762584X) 12 DOIs in total:
"counts": {
"current-dois": 0,
"backfile-dois": 12,
"total-dois": 12
}
This is not consistent with ISSN filters:
https://api.staging-legacy.crossref.org/journals/1762584X/works -> 1 result
https://api.staging-legacy.crossref.org/works?filter=issn:1762584X -> 1 result
But is consistent with journal id filter:
https://api.staging-legacy.crossref.org/works?filter=journal:27878 -> 12 results
The difference is related to two ISSNs belonging to this journal id. In staging, out of 12 DOIs of this journal id, 11 have ISSN 02460343 and 1 has ISSN 1762584X.
Definition of ready
-
Product owner: @ppolischuk1 -
Tech lead: @dtkaczyk -
Service:: label applied -
Definition of done updated -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available via a staging URL -
Knowledge base reviewed and updated -
Acceptance criteria met -
journal coverage statistics are calculated for a given ISSN, not journal id, matching production behavior
-