| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
datacite importer had errors otherwise
|
| |
|
|
|
|
|
| |
May be possible to upgrade both of these libraries together, but that
isn't the purpose of current development.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Eg, instead of container-specific year histogram, have the histogram
fetch function take a ReleaseQuery.
This is in preparation for more generic coverage visualization pages.
|
| |
|
|
|
|
|
| |
These were being added to many views which didn't need them (eg,
metadata, editing views)
|
| |
|
|
|
|
|
| |
Instead of always enriching container entities with random articles,
only do so for the primary container view.
|
| |
|
|
|
|
|
|
| |
- show release type counts
- new-style preservation status (single bar)
- show release_type preservation break down on coverage page
|
|
|
|
|
|
|
|
|
|
| |
- new by-year chart with stacked histograms of all 4 preservation
statuses
- new-style single progress bar showing overall preservation status
- new by-volume query and chart
Old endpoints are left as-is, with the intention of having them
"deprecated" for some time span until entirely removing them.
|
|
|
|
|
|
|
|
|
|
| |
fomatic-ui is a "community fork" which has had more active recent
feature additions, though i'm not sure whether the quality has been as
good as the main semantic-ui project.
the proximal motivation to upgrade/switch is to get multi-bar progress
bars, to display overall preservation status in a single bar as a
fraction.
|
| |
|
| |
|
|
|
|
| |
also shuffle around search/coverage test files
|
| |
|
|
|
|
| |
To match fatcat-scholor, where this scheme has been successful.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This error handler and view page currently works much better than the
"flash()" infrastructure built-in to flask, which uses cookies and
mostly does not work with our views and layouts.
Would like to gradually migrate almost all API errors in the web
interface to just raising errors that get rendered on an error page,
instead of calling `abort(ae.status)`.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Moved all the request_cache=True param calls to just before ES request
exectuation. The former ordering "just worked", but pylint didn't like
it, and I suspose it was not as idiomatic as it should have been.
|
| |
|
| |
|
|
|
|
|
|
| |
Instead of using 'responses' mock of 'requests' library.
Tried using 'elasticmock' helper but it didn't work.
|
|
|
|
|
|
|
|
|
|
| |
Based on fatcat-scholar refactoring.
This doesn't include refactoring of stats, aggregates, or histograms
yet, just the direct queries.
Don't have any test coverage yet; intend to try elasticmock or figuring
out how to ingest mock JSON results directly.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
more lint fixes
See merge request webgroup/fatcat!69
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Oh no!
This bug may actually have had significant negative impact on metadata
in fatcat, in terms of missing container_id associations with pubmed
entities. There are about 500k release entities with a PMID but no
container_id. Of those, 89k have at least a container_name. Unclear how
many would have matched to ISSN-L and thus to a container.
|
| |
| |
| |
| | |
We are python3.7 now, so this isn't needed.
|
| |
| |
| |
| |
| |
| | |
These should not have any behavior changes, though a number of exception
catches are now more general, and there may be long-tail exceptions
getting thrown in these statements.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The pytest fixture syntax interacts weirdly with flake8 tests, so ignore
the "redefinition" and "unused variable" errors more carefully for .py
files under ./tests/
|
| |
| |
| |
| | |
Thanks @martin
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|