| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\
| |
| |
| |
| | |
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.
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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 is mostly changing ingest_type from 'file' to 'pdf', and adding
'link_source'/'link_source_id', plus some small cleanups.
|
| |
|
|
|
|
|
|
| |
This was causing 5xx errors in production and qa. Eg, at:
https://qa.fatcat.wiki/release/aaaaaaaaaaaaarceaaaaaaaaai/history
|
| |
|
| |
|
|
|
|
|
|
| |
The more complete fix is to actually render the JATS to HTML and display
that. This is just to fix a nit with the most common case of XML tags in
abstracts.
|
|
|
|
|
|
|
| |
Test in previous commit.
This fixes a user-reported 500 error when creating a file with
SHA1/SHA256/MD5 hashes in upper-case.
|
|\
| |
| |
| |
| | |
Add basic pagination to search results
See merge request webgroup/fatcat!4
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
| |
Caught one of these in sentry. Probably due to a crawler? Or typing
gibberish in the token form.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This makes it possible to, eg, past an arxiv identifier or SHA-1 hash in
the general search box and do a quick lookup.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Have run in to several issues with IA screenname being invalid fatcat
usernames (eg, containing whitespace).
This probably won't catch all such issues, but hopefully most of them.
|