diff options
-rw-r--r-- | Makefile | 2 | ||||
-rw-r--r-- | fatcat_scholar/query_citation.py | 2 | ||||
-rw-r--r-- | fatcat_scholar/templates/help.html | 2 | ||||
-rw-r--r-- | fatcat_scholar/web.py | 2 | ||||
-rw-r--r-- | notes/scaling_works.md | 4 |
5 files changed, 6 insertions, 6 deletions
@@ -24,7 +24,7 @@ pytype: ## Run slow pytype type check (not part of dev deps) pipenv run pytype fatcat_scholar/ .PHONY: fmt -fmt: ## Run code formating on all source code +fmt: ## Run code formatting on all source code pipenv run isort --atomic fatcat_scholar/ tests/ pipenv run black --line-length 88 fatcat_scholar/ tests/ diff --git a/fatcat_scholar/query_citation.py b/fatcat_scholar/query_citation.py index 83717e8..79eceef 100644 --- a/fatcat_scholar/query_citation.py +++ b/fatcat_scholar/query_citation.py @@ -93,7 +93,7 @@ def fuzzy_match( - WEAK - AMBIGUOUS - Eg, if there is any EXACT match that is always returned; an AMBIGIOUS + Eg, if there is any EXACT match that is always returned; an AMBIGUOUS result is only returned if all the candidate matches were ambiguous. TODO: actually do something with timeout diff --git a/fatcat_scholar/templates/help.html b/fatcat_scholar/templates/help.html index fb26740..c4d0256 100644 --- a/fatcat_scholar/templates/help.html +++ b/fatcat_scholar/templates/help.html @@ -94,7 +94,7 @@ apply range queries like <code>year:>1989 year:<2000</code>.{% endtrans %} <tr><td style="font-family: monospace;">stage: <td>eg, "published", "submitted", "accepted", "draft" <tr><td style="font-family: monospace;">lang; - <td>value is a 2-character lower-case ISO lanuage code) + <td>value is a 2-character lower-case ISO language code) <tr><td style="font-family: monospace;">country: <td>value is a 2-character lower-case ISO country code <tr><td style="font-family: monospace;">access_type: diff --git a/fatcat_scholar/web.py b/fatcat_scholar/web.py index 4e21ecd..495ae98 100644 --- a/fatcat_scholar/web.py +++ b/fatcat_scholar/web.py @@ -530,7 +530,7 @@ app.include_router(web) for lang_option in I18N_LANG_OPTIONS: app.include_router(web, prefix=f"/{lang_option}") -# Becasue we are mounting 'api' after 'web', the web routes will take +# Because we are mounting 'api' after 'web', the web routes will take # precedence. Requests get passed through the API handlers based on content # negotiation. This is counter-intuitive here in the code, but does seem to # work, and results in the OpenAPI docs looking correct. diff --git a/notes/scaling_works.md b/notes/scaling_works.md index 60b4597..e9881e1 100644 --- a/notes/scaling_works.md +++ b/notes/scaling_works.md @@ -411,7 +411,7 @@ with highlighter. to allow query and highlight fields to be separate? or perhaps even a separate highlighter query. query "everything", highlight specific fields. -scoring/boosting large reponses (more than a few hundred thousand hits) seems +scoring/boosting large responses (more than a few hundred thousand hits) seems expensive. this include the trivial '*' query. some fulltext phrase queries seem to always be expensive. look in to phrase @@ -699,7 +699,7 @@ encoding: xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 40, column 1122 Root cause was an issue in GROBID, which seems to have been fixed in more -recent versions of GROBID. Patched to continue, and separately commited patch +recent versions of GROBID. Patched to continue, and separately committed patch to fatcat-scholar code base. Ran several retries, manually. |