Get AI summaries of any video or article — Sign up free
Free Scopus Data Extraction || Publish or Perish Software ||  Scopus API key Integration thumbnail

Free Scopus Data Extraction || Publish or Perish Software || Scopus API key Integration

eSupport for Research·
5 min read

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.

TL;DR

Generate a Scopus API key on Elsevier’s developer platform, then paste it into Publish or Perish to enable Scopus extraction.

Briefing

Scopus data can be pulled into Publish or Perish without manual copying—by generating a Scopus API key, integrating it inside Publish or Perish, and then running both author/publication lookups and keyword-based document searches. The payoff is a structured export of citation metrics (including h-index and g-index) plus publication metadata, delivered in downloadable formats like CSV, so researchers can build literature reviews or evaluate scholarly output even when Scopus full access is limited.

The workflow starts with Publish or Perish’s interface, where users select Scopus as the data source and choose identifiers such as Scopus ID and ORCID ID (ORCID can be used for integration). Publish or Perish then prompts for an API key—because Scopus access for automated extraction requires API authentication. That key is obtained from Elsevier’s developer platform: users register, log in, generate a free API key, and copy it back into Publish or Perish. Once the key is accepted, Publish or Perish begins extracting results tied to Scopus author identifiers.

After integration, the software produces citation metrics and publication lists in two main modes. In the basic search flow, it returns author-level output arranged by publication details such as first/last author names, year, and a set of indices. The transcript highlights that h-index and g-index appear in the generated matrices, along with other index-related parameters relevant to citation impact. Users can then save results and download them in multiple formats, including CSV and “.bibtex” style outputs (the transcript mentions CSV and a BibTeX-like download option), which helps with downstream analysis and reference management.

An extended search adds richer metadata per record: paper titles, author names, journal or source information, site scores, DOI links, and other bibliographic fields such as volume and issue. The export is positioned as practical for researchers who need structured datasets for analysis rather than just a list of papers.

The second major capability is document search for literature review workflows. Users run a new Scopus query using keywords (the transcript references an example keyword like “ECG signal analysis”), then export matching records. Even when full-text access is unavailable, the approach still supports progress: abstracts and related URLs can be used to refine inclusion/exclusion criteria, and individual record pages can provide enough bibliographic detail to support screening and synthesis. The transcript also notes that users can refine searches by setting inclusion/exclusion parameters (including selecting ranges like 20–30 or 50 documents) and then export the results for writing.

Finally, the transcript frames the method as an alternative route to reach conclusions without being blocked by paywalled full-text access: citation metrics and bibliographic metadata are extracted via API, then used to build a review dataset and support research decisions. It also suggests that Publish or Perish can be configured for other sources (e.g., Semantic Scholar, Web of Science) if additional videos or integrations are followed, but the core focus remains Scopus API key integration for automated extraction and export.

Cornell Notes

Publish or Perish can extract Scopus author and document data automatically once a Scopus API key is generated from Elsevier’s developer platform and pasted into the software. After integration, users can run author/publication searches that return citation impact metrics such as h-index and g-index, along with downloadable publication lists. An extended mode adds richer bibliographic fields like titles, journal/source details, DOI links, and other record metadata, typically exportable as CSV and BibTeX-style files. For literature reviews, keyword-based document searches return matching records so researchers can screen using abstracts and metadata even without full-text access. This matters because it turns Scopus results into structured datasets for analysis and reference management.

Why does Publish or Perish require a Scopus API key for extraction?

Scopus automated searching and data retrieval in this workflow depends on API authentication. Publish or Perish flags that API integration is needed for Scopus-based extraction, then requests an API key. The key is generated on Elsevier’s developer platform after registration and login, and it is copied into Publish or Perish so the software can query Scopus and pull author/publication records.

What outputs does the workflow produce after a successful Scopus author search?

Once the Scopus API key is integrated, Publish or Perish extracts author-linked records and computes citation metrics. The transcript specifically highlights h-index and g-index appearing in generated matrices, alongside other index-related parameters. It also returns publication information arranged by fields such as author names and year, and it supports saving results and downloading them (including CSV and BibTeX-style outputs).

How does “basic” vs “extended” search change the exported information?

In the basic mode, the export emphasizes author-level results and index-related matrices, with core publication listing details. In the extended mode, the export includes more complete bibliographic metadata per record—paper title, author name, journal/source information, site score, DOI link, and additional fields such as volume and issue—making it more useful for building a structured literature dataset.

How can keyword-based document search support a literature review when full text isn’t accessible?

Keyword searches return records that match the query (the transcript uses an example like “ECG signal analysis”). Even if full-text PDFs are unavailable, the workflow still provides abstracts and related URLs plus bibliographic details. Researchers can use abstracts to apply inclusion/exclusion criteria, refine the set of records (e.g., selecting 20–30 or 50 documents), and then export the screened results for writing and synthesis.

What role do ORCID and Scopus IDs play in the integration?

The transcript describes selecting identifiers such as Scopus ID and ORCID ID. ORCID can be integrated with Scopus within the workflow, helping connect author identity across systems. Users then supply the Scopus ID to run the extraction for the correct author profile.

Review Questions

  1. What steps are required to generate and insert a Scopus API key into Publish or Perish before any extraction can run?
  2. Which citation metrics are highlighted as being calculated and where do they appear in the results?
  3. How does the document-search workflow help with screening and refining a literature review set when full-text access is limited?

Key Points

  1. 1

    Generate a Scopus API key on Elsevier’s developer platform, then paste it into Publish or Perish to enable Scopus extraction.

  2. 2

    Select Scopus as the data source in Publish or Perish and use Scopus ID (and optionally ORCID ID) to target the correct author records.

  3. 3

    Use the author/publication search to retrieve citation impact metrics, including h-index and g-index, presented in generated result matrices.

  4. 4

    Switch to extended search to export richer bibliographic metadata such as titles, journal/source details, DOI links, and fields like volume and issue.

  5. 5

    Download results in structured formats (CSV and BibTeX-style outputs) to support analysis and reference management.

  6. 6

    Run keyword-based document searches to build literature-review datasets using abstracts and metadata, even when full-text PDFs are not accessible.

Highlights

Scopus extraction in Publish or Perish hinges on API authentication: a free Scopus API key must be generated and integrated before searches can run.
The workflow surfaces citation impact metrics—explicitly h-index and g-index—along with publication lists that can be saved and exported.
Extended search adds record-level detail (DOI links and journal/source metadata), making exports more usable for systematic review workflows.
Keyword-based document search supports screening via abstracts and related URLs, reducing dependence on full-text access.

Topics

  • Scopus API Key
  • Publish or Perish
  • h-index
  • g-index
  • Literature Review Search

Mentioned

  • API
  • DOI
  • ORCID
  • CSV
  • h-index
  • g-index