| scopus_plan | R Documentation |
A plan is a fully specified, inspectable description of one or more 'Scopus' queries to run. Splitting the act of describing a search from executing it makes workflows reproducible (the plan can be saved, reviewed and version controlled) and lets large retrievals be partitioned, for example one cell per year, so they can be cached and resumed.
scopus_plan(
query,
years = NULL,
field = NULL,
view = c("STANDARD", "COMPLETE"),
page_size = NULL,
partition = c("none", "year")
)
is_scopus_plan(x)
query |
Character scalar. The base search expression, without field tags
or year filters (these are added through |
years |
Optional integer vector of publication years to restrict to, for
example |
field |
Optional character scalar naming a 'Scopus' field tag to wrap the
query in, for example |
view |
Either |
page_size |
Integer number of records to request per page, or |
partition |
Either |
x |
An object to test or print. |
A tibble of class scopus_plan, one row per cell, with columns
cell, query (field-wrapped), date (year range string or NA), year
(integer or NA), view and page_size. Plan-level settings are stored as
attributes.
is_scopus_plan() returns a length-one logical.
scopus_fetch_plan() to execute a plan, scopus_count() to size it.
scopus_plan("quantum computing", years = 2015:2022, field = "TITLE-ABS-KEY")
scopus_plan("immunotherapy", years = 2010:2020, partition = "year")
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.