diff options
author | Bryan Newbold <bnewbold@robocracy.org> | 2020-07-23 14:47:56 -0700 |
---|---|---|
committer | Bryan Newbold <bnewbold@robocracy.org> | 2020-07-23 14:48:00 -0700 |
commit | a05ecb7959bc57b8f1c3607e1c941e8e25d9a87b (patch) | |
tree | 1ea23eddff08b4e0e098a6019a1c118ed240ac3f /rust/migrations/2019-01-01-000000_init/up.sql | |
parent | 6a87b3d2e1b315d35ccaa13457571d73afaf5e6b (diff) | |
download | fatcat-a05ecb7959bc57b8f1c3607e1c941e8e25d9a87b.tar.gz fatcat-a05ecb7959bc57b8f1c3607e1c941e8e25d9a87b.zip |
make in_kbart transform inclusive of last year
Frequently when looking at preservation coverage of journals, the
current year shows as "un-preserved" when in fact there is robust KBART
(keepers, eg CLOCKSS/Portico) coverage. This is partially because we
don't update containers with KBART year spans very frequently (which is
on us), and partially because KBART reports are often a bit out of day
(eg, doesn't show coverage for the current year. For that matter, they
probably take a few months to update the previous year as well, but that
is a larger time span to fudge over.
This patch means we will count Portico/LOCKSS/etc coverage for "last
year" to count as coverage of publications dated "this year". Note that
for this to be effective/correct, it is assumed that we will update
containers with coverage year spans at least once a year, and that we
will re-index all releases at least once a year.
Diffstat (limited to 'rust/migrations/2019-01-01-000000_init/up.sql')
0 files changed, 0 insertions, 0 deletions