Scopus Literature Search || Scopus Document Search Strategies || Literature Search Process
Based on eSupport for Research's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Define the research question first, then translate it into multiple searchable concept groups (measurement, condition, and diagnostic intent).
Briefing
A six-step literature search workflow in Scopus is paired with a practical example: combining ECG/Electrocardiogram terms with sleep-disorder concepts (including sleep apnea and related synonyms) to generate a focused query, then refining it using Scopus filters and exporting results for writing and analysis. The core takeaway is that strong search results come less from a single “magic query” and more from a repeatable cycle: define the research question, translate it into concepts and synonyms, combine concepts with Boolean operators, test the query, apply limits/filters, and save the refined search for later reuse.
The process starts by defining the research question clearly—then breaking it into searchable concepts. In the example, the question centers on whether ECG signals can help detect sleep disorders. From that, three concept buckets are built: (1) the signal/measurement concept (ECG/electrocardiogram/electrocardiography), (2) the sleep-disorder concept (sleep disorder, sleep apnea, and related terms/synonyms), and (3) the intended diagnostic framing (e.g., diagnosis, detection, identification, screening). Once those concept buckets exist, the search strategy is developed using Boolean operators—especially AND to require multiple concepts in the same results.
Next comes query construction and testing. The workflow emphasizes starting broad enough to capture relevant literature, then iteratively tightening. Scopus suggestions are used to expand keywords and synonyms, and the query is assembled by combining concept groups. The example query structure includes ECG/electrocardiogram terms AND sleep-disorder terms, with additional diagnostic/detection language added to steer results toward the intended use case.
After running a basic search, the workflow shifts to refinement inside Scopus. Filters and limits are applied to reduce noise and focus on the most relevant subset—such as narrowing by subject area (the example narrows to Computer Science rather than Medicine), restricting document types (e.g., excluding certain categories like conference papers/books), setting language to English, and limiting the publication year range. The transcript also highlights practical checks: ensuring keyword spelling is correct, because Scopus keyword matching can affect results.
The final stage is managing and exporting results. Saved searches can be rerun to reproduce the same dataset later for updates or further refinement. Export options are demonstrated, including downloading results as CSV for spreadsheet work and using bibliographic formats (e.g., BibTeX, RIS, and EndNote-compatible outputs). Exported files retain filter context such as year range, subject area, document type, and other metadata—supporting downstream literature review and systematic-style analysis. The overall message is operational: build a query from concepts, combine them with Boolean logic, validate with test runs, refine with Scopus filters, and export/save the results so the literature review process stays consistent and reproducible.
Cornell Notes
The workflow for searching literature in Scopus is built around a repeatable cycle: define the research question, convert it into searchable concepts and synonyms, combine those concepts with Boolean operators, test the query, then refine using Scopus filters and limits. A concrete example targets whether ECG/electrocardiogram signals can detect sleep disorders by combining ECG terms with sleep-disorder terms (including sleep apnea) and adding diagnostic/detection language. After the initial broad search returns thousands of records, refinement narrows results by subject area, language, document type, and year range. The refined results can be saved and exported (CSV, BibTeX, RIS, etc.) with metadata preserved, enabling consistent literature review and later updates.
How does the workflow turn a research question into a Scopus-ready search query?
Why use Boolean operators like AND when building the query?
What does “test and refine” look like in Scopus terms?
How are saved searches and exports used to support a literature review workflow?
What practical strategy helps avoid overwhelming results after an initial broad search?
Review Questions
- If a research question involves a measurement concept and a disease concept, what three concept buckets would you create before writing Boolean queries?
- When refining a Scopus search, which filters are most likely to reduce noise without eliminating key literature?
- Why is saving a refined Scopus query useful for later stages like systematic review updates or writing a paper?
Key Points
- 1
Define the research question first, then translate it into multiple searchable concept groups (measurement, condition, and diagnostic intent).
- 2
Use synonyms and Scopus keyword suggestions to expand each concept group before combining them.
- 3
Combine concept groups with Boolean logic—especially AND—to require that results match multiple parts of the question.
- 4
Run a basic query, check result counts and relevance, then iteratively refine using Scopus filters (subject area, language, document type, year range).
- 5
Treat keyword spelling as critical; incorrect spelling can reduce matches and distort results.
- 6
Save refined searches so the same dataset can be reproduced and updated later.
- 7
Export results with metadata (CSV and reference-manager formats like BibTeX/RIS) to support literature review and writing workflows.