Differences in counts-type/all in coverage between staging and production
Background
In staging, counts-type/all
is a sum of counts-type/backfile
and counts-type/current
. For example, for member 237 we have:
"counts-type": {
"all": {
"journal-article": 1414,
"posted-content": 30
},
"current": {
"journal-article": 208,
"posted-content": 30
},
"backfile": {
"journal-article":1206
}
}
In production, for the same indexes sample, this member has an additional DOI counted in counts-type/all
:
"counts-type": {
"all": {
"journal": 1,
"posted-content": 30,
"journal-article": 1414
},
"current": {
"posted-content": 30,
"journal-article": 208
},
"backfile": {
"journal-article": 1206
}
}
This additional DOI of type journal
has no issued date, that's why it is not included in current or backfile.
Such DOIs without issued dates are included in counts-type/all
in production and nit included in staging.
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 -
Public documentation reviewed and updated -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Acceptance criteria met -
In ES REST API, DOIs without issued dates should be included in counts-type/all
, like the production behavior
-
Notes
Edited by Patrick Polischuk