summaryrefslogtreecommitdiffstats
path: root/python/fatcat_web/templates
Commit message (Collapse)AuthorAgeFilesLines
* container view: only show OA indicator when knownBryan Newbold2020-09-171-5/+1
| | | | | The "is_oa:False" could be that we just don't know; aren't actually distinguishing between false and blank.
* web container view: hide preservation when no releasesBryan Newbold2020-09-171-8/+6
|
* coverage search: pretty display for ES query errorsBryan Newbold2020-09-171-0/+7
|
* coverage: clarify available/accessible terminologyBryan Newbold2020-09-171-1/+1
|
* homepage: small grammar tweaks (The/the)Bryan Newbold2020-09-111-3/+3
|
* remove typo (isbn:) from metadata DC.language fieldBryan Newbold2020-08-211-1/+1
|
* remove placeholder description meta tagBryan Newbold2020-08-201-1/+0
|
* fix SearchAction nesting in WebSite (schema.org)Bryan Newbold2020-08-201-5/+2
| | | | | This is not related to sitemap changes, but I was reminded in google search tools when validating site.
* web: add links to deletion pages from edit pagesBryan Newbold2020-07-314-0/+13
|
* editing: withdrawn_status, release_yearBryan Newbold2020-07-311-6/+20
|
* implement webface entity deletionBryan Newbold2020-07-311-0/+49
|
* routes: handle case of viewing deleted entity in editgroup contextBryan Newbold2020-07-302-6/+8
| | | | | | 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.
* wire up new TOML viewsBryan Newbold2020-07-3011-21/+43
|
* generic HTML views for TOML editingBryan Newbold2020-07-304-0/+80
|
* control shadow preservation display with a flagBryan Newbold2020-07-301-3/+9
|
* release search: fix fulltext_only checkbox (from query object)Bryan Newbold2020-07-301-1/+1
|
* search: 'recent' mode for coverage searchBryan Newbold2020-07-301-0/+14
|
* first iteration of flexible search coverageBryan Newbold2020-07-303-2/+83
|
* update container view statsBryan Newbold2020-07-303-80/+148
| | | | | | - show release type counts - new-style preservation status (single bar) - show release_type preservation break down on coverage page
* preservation coverage updates (first round)Bryan Newbold2020-07-301-22/+38
| | | | | | | | | | - 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.
* experimentally update semantic-ui to fomantic-ui 2.8.6Bryan Newbold2020-07-301-4/+4
| | | | | | | | | | 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.
* update front-page countsBryan Newbold2020-07-281-3/+3
|
* switch SERP stage coloring to brown uppercaseBryan Newbold2020-07-281-13/+11
| | | | To match fatcat-scholor, where this scheme has been successful.
* error handling: use 400 page with error passed instead of flash()Bryan Newbold2020-07-281-4/+14
|
* generic API error pageBryan Newbold2020-07-281-0/+20
| | | | | | | | | | 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)`.
* search: catch ES errors and display betterBryan Newbold2020-07-283-13/+19
|
* refactor search macros into new fileBryan Newbold2020-07-284-45/+72
|
* refactor release and container searchBryan Newbold2020-07-243-23/+23
| | | | | | | | | | 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.
* make fulltext-only label clickableMartin Czygan2020-06-161-2/+2
|
* use ES 'best_url' in file download pagesBryan Newbold2020-06-041-2/+2
| | | | Similar to recent change for release download pages.
* re-use 'best pdf url' for release green buttonBryan Newbold2020-06-041-2/+2
| | | | | | | 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.
* Merge branch 'bnewbold-search-tweaks' into 'master'bnewbold2020-04-273-92/+132
|\ | | | | | | | | tweaks to search result pages See merge request webgroup/fatcat!50
| * web search: tweak release search result styleBryan Newbold2020-04-231-25/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * web search: improve indentation, fix missing div tagsBryan Newbold2020-04-232-67/+81
| | | | | | | | These are back-ported fixes from covid19.fatcat.wiki
* | web: fix ident=None broken linksBryan Newbold2020-04-233-6/+10
|/ | | | | | 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.
* web: small corrections to subtitle/original_nameBryan Newbold2020-03-281-2/+2
|
* Merge branch 'bnewbold-translation-view'Bryan Newbold2020-03-281-0/+3
|\
| * web: display container original titlesBryan Newbold2020-03-261-0/+3
| |
* | improve citeproc/CSL web interfaceBryan Newbold2020-03-251-2/+1
|/ | | | | | | | | | | | | | 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.
* container lookup: link to issn portal searchMartin Czygan2020-03-181-4/+3
| | | | | | | | | 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
* update front-page statsBryan Newbold2020-03-171-3/+3
|
* filter out shadows-only files in webfaceBryan Newbold2020-02-131-2/+3
|
* pagination: use correct endpoint in navigationMartin Czygan2020-01-182-6/+6
|
* datacite release links and metadata expansionBryan Newbold2019-12-202-9/+13
| | | | | | | 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
* initial 'Save Paper Now' web formBryan Newbold2019-12-122-1/+98
|
* fix delete release history viewBryan Newbold2019-12-091-1/+1
| | | | | | This was causing 5xx errors in production and qa. Eg, at: https://qa.fatcat.wiki/release/aaaaaaaaaaaaarceaaaaaaaaai/history
* add missing underline in deleted entity web viewBryan Newbold2019-12-091-1/+1
|
* gray out inactive navigation linksMartin Czygan2019-11-141-2/+2
| | | | | | | | 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.
* move pagination into macrosMartin Czygan2019-11-143-43/+51
| | | | | | | | | Two new macros: * top_results(found) * bottom_results(found) wip: move pagination into macro
* Add basic pagination to search resultsMartin Czygan2019-11-082-3/+42
| | | | | | | | | | | | 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
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-12 10:42:10 +0000