| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Similar to recent change for release download pages.
|
|
|
|
|
|
|
| |
I thought this was the existing behavior, but it looks like we were just
taking the first link from the first file.
In the future may refactor this out even further.
|
|\
| |
| |
| |
| | |
search: assume * when q is not set or empty
See merge request webgroup/fatcat!51
|
| |
| |
| |
| | |
An example would be a blank search from a container details page.
|
|\ \
| |/
|/|
| |
| | |
tweaks to search result pages
See merge request webgroup/fatcat!50
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is also back-ported from covid19.fatcat.wiki, though with some more
tweaks on top.
The changes are:
- show original title if available (usually non-English)
- move release_type label to title line suffix, and only show if not a
"paper"
- show publication status and withdrawl as text after the journal title,
not as a label
|
| |
| |
| |
| | |
These are back-ported fixes from covid19.fatcat.wiki
|
|/
|
|
|
|
| |
On web interface views for revisions, we had a bunch of broken links
because the ident is "None". This commit fixes these by removing the
links.
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Thanks to Martin for suggestion
|
| | |
|
| |
| |
| |
| |
| | |
The release view will display subtitles, but it needs to be in the
correct "location".
|
|\ \
| | |
| | | |
Correct spelling mistakes
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
catch ApiValueError in some generic API calls
See merge request webgroup/fatcat!35
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The motivation for this change is to handle bogus revision IDs in URLs,
which were causing 500 errors not 400 errors. Eg:
https://qa.fatcat.wiki/file/rev/5d5d5162-b676-4f0a-968f-e19dadeaf96e%2B2019-11-27%2B13:49:51%2B0%2B6
I have no idea where these URLs are actually coming from, but they
should be 4xx not 5xx.
Investigating made me realize there is a whole category of ApiValueError
exceptions we were not catching and should have been.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This tries to show the citeproc (bibtext, MLA, CSL-JSON) options for
more releases, and not show the links when they would break.
The primary motivation here is to work around two exceptions being
thrown in prod every day (according to sentry):
KeyError: 'role'
ValueError: CLS requries some surname (family name)
I'm guessing these are mostly coming from crawlers following the
citeproc links on release landing pages.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Example:
https://fatcat.wiki/container/lookup?issnl=2007-1248 - the linked
https://portal.issn.org/2007-1248 yields a "page not found", while
search yields results:
https://portal.issn.org/api/search?search[]=MUST=allissnbis=2007-1248
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
The other fields are now "copy_to" the merged biblio field.
|