| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This is not related to sitemap changes, but I was reminded in google
search tools when validating site.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Eg, consider deleting an entity. When viewing the editgroup, want to be
able to click the deleted entity and see the "deleted entity" page
instead of a generic 404.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- 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)`.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
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.
|
| | |
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Small ergonomic changes for datacite releases:
- add a link to live/current datacite metadata (like we do for Crossref)
- expand "extra" metadata fields under 'datacite' dict in metadata view
|
| | |
|
| |
|
|
|
|
| |
This was causing 5xx errors in production and qa. Eg, at:
https://qa.fatcat.wiki/release/aaaaaaaaaaaaarceaaaaaaaaai/history
|
| | |
|
| |
|
|
|
|
|
|
| |
As per [this
issue](https://github.com/Semantic-Org/Semantic-UI/issues/1885#issuecomment-77619519),
text colors are not supported in semantic ui.
To not move text too much, gray out inactive links.
|
| |
|
|
|
|
|
|
|
| |
Two new macros:
* top_results(found)
* bottom_results(found)
wip: move pagination into macro
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The "deep paging problem" imposes some limit, which currently is a
hardcoded default value, `deep_page_limit=2000` in `do_search`.
Elasticsearch can be configured, too:
> Note that from + size can not be more than the index.max_result_window
index setting, which defaults to 10,000.
-- https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-body.html#request-body-search-from-size
|
| | |
|
| | |
|
| | |
|
| | |
|
