Skip to contents

Citing scopusflow

If you use scopusflow in published work, please cite it.

Bernabeu, P. (2026). scopusflow: A reproducible workflow layer for ‘Scopus’ bibliographic searches. R package version 0.3.0. https://doi.org/10.5281/zenodo.21252669

@Manual{scopusflow,
  title  = {{scopusflow}: A reproducible workflow layer for '{Scopus}' bibliographic searches},
  author = {Pablo Bernabeu},
  year   = {2026},
  note   = {R package version 0.3.0},
  doi    = {10.5281/zenodo.21252669},
  url    = {https://doi.org/10.5281/zenodo.21252669},
}

Download .bib

R users can also retrieve this citation directly with citation("scopusflow").

The developer

Pablo Bernabeu is a researcher in the Department of Education at the University of Oxford, with hands-on experience of behavioural experiments, EEG, corpus analysis, computational modelling and statistics. He develops open, reproducible research software in R and Python, and is a Fellow of the Software Sustainability Institute. scopusflow and its Python twin are part of that work, keeping a search reproducible and its results legible across both languages.

Licence

scopusflow is released under the MIT licence. ‘Scopus’ is a trademark of Elsevier. scopusflow is an independent client and is not affiliated with or endorsed by Elsevier.

Versioning and archival

Releases are tagged on GitHub and archived on Zenodo. The concept DOI 10.5281/zenodo.21252669 always resolves to the latest archived version, so a citation stays current without naming a version. The changelog records what changed in each release.

Contributing and support

Bugs and feature requests are best raised on the GitHub issues page, and the contributing guide describes the development setup and the conventions the package follows. Because the package works with an Elsevier API key, please never paste a key or any other secret into an issue.