You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case: in some cases, users want to be notified when we add papers to the database that match their query terms and are not necessarily recently published.
Current behavior: we automatically add entdate:[XX TO YY] pubdate:[YYYY-00 TO *] to a given query, where YYYY is the current year, as we assume that users only want notifications of recent papers.
Proposed fix: in the general-type query notification setup (from the search results page), add a flag to allow users to enable historical results (or, conversely, a flag to only return new papers; this would be set by default). If historical results are allowed, do not add pubdate:[YYYY-00 TO *] automatically to the query when generating notifications.
The text was updated successfully, but these errors were encountered:
Use case: in some cases, users want to be notified when we add papers to the database that match their query terms and are not necessarily recently published.
Current behavior: we automatically add
entdate:[XX TO YY] pubdate:[YYYY-00 TO *]
to a given query, whereYYYY
is the current year, as we assume that users only want notifications of recent papers.Proposed fix: in the general-type query notification setup (from the search results page), add a flag to allow users to enable historical results (or, conversely, a flag to only return new papers; this would be set by default). If historical results are allowed, do not add
pubdate:[YYYY-00 TO *]
automatically to the query when generating notifications.The text was updated successfully, but these errors were encountered: