CASRAI Dictionary

Tag: iThenticate

  • Elsevier’s Research Integrity Screening Process

    Elsevier screens research submissions for integrity issues through a layered pipeline: automated tools such as Check Integrity and Crossref Similarity Check flag plagiarism, duplicate submissions and image anomalies at intake, specialist Research Integrity and Publishing Ethics (RIPE) analysts investigate confirmed concerns, and outcomes range from correction through expression of concern to full retraction, following guidelines set by the Committee on Publication Ethics (COPE).

    Research integrity screening is the set of technical checks and human review stages a publisher applies to a manuscript, before and after publication, to detect fabrication, falsification, plagiarism, undisclosed image manipulation and paper-mill activity. At Elsevier, that pipeline runs continuously from the moment a manuscript is submitted to the point, if necessary, of retraction.

    How Elsevier’s research-integrity pipeline works, from submission to retraction

    Elsevier operates one of the largest editorial screening operations in scholarly publishing. In 2025, the publisher received 4.2 million manuscript submissions across roughly 3,000 journals and published 795,000 after validation and peer review, according to Elsevier’s own account of its editorial process. Elsevier states that its published output accounts for over 18% of global research output and 29% of citations — a scale that shapes why it has invested heavily in both automated screening and dedicated integrity staff rather than relying on peer review alone.

    The pipeline runs across four broad stages, each with a different primary tool or team responsible for catching a different class of problem.

    Stage Primary tool or team Typical trigger
    Submission intake Check Integrity screening tool; Crossref Similarity Check (iThenticate) Text overlap, duplicate manuscript, unauthorised authorship change
    Peer review Editors, external reviewers, RIPE analysts Implausible data, reviewer-flagged inconsistency, suspicious image reuse
    Post-publication monitoring Research Integrity and Publishing Ethics (RIPE) team Reader or whistleblower reports, cross-journal pattern analysis
    Enforcement Editors-in-chief, following COPE-guided process Confirmed fabrication, falsification or plagiarism

    What does Elsevier screen for at the point of submission?

    Every manuscript submitted to an Elsevier journal is routed through automated checks before an editor sees it. Check Integrity, Elsevier’s proprietary screening tool, had been expanded across more than 2,000 journals as of March 2026, according to trade press coverage in Research Information. The tool automatically reviews submissions for red flags — including unauthorised authorship changes, undisclosed conflicts of interest and signs of duplicate or template-like submission — and routes anything flagged to specialist integrity analysts, freeing editors to focus on scientific merit.

    Plagiarism screening runs in parallel through Crossref Similarity Check, powered by iThenticate, which compares submitted text against a large index of published articles and web content. There is no fixed similarity percentage that automatically triggers rejection; editors interpret each report to distinguish appropriate citation from genuine textual misconduct.

    Paper-mill detection layers on top of these checks. Integrity analysts look for patterns that recur across industrialised fraud, including:

    • Formulaic, template-like titles or methods sections
    • Unusual or inconsistent author affiliations and contact details
    • Data or experimental descriptions that do not match the stated methodology
    • Systematic image reuse across ostensibly unrelated papers
    • Irregular peer-review patterns, such as reviewer suggestions tied to the same small pool of contacts

    How does Elsevier detect image manipulation and data-integrity problems?

    Image screening combines editorial guidelines with a mix of manual and software-assisted checks. Elsevier’s policy permits minor adjustments to brightness, contrast or colour balance only where they do not obscure or eliminate information present in the original image; the use of generative AI to create or alter a figure is prohibited outright. Where manipulation is suspected, editors can apply forensic image-analysis tools of the kind recommended by the US Office of Research Integrity, and will typically request the original, unprocessed image files directly from the authors.

    Elsevier has also published on the scale of automated flagging behind these checks. At the 8th World Conference on Research Integrity in 2024, Elsevier data scientist Yuri Kashnitsky presented on large-scale flagging of integrity misconduct across the publisher’s portfolio, noting that all system-generated findings are manually checked and confirmed by investigators before any corrective action is suggested to editors — underscoring that software narrows the search space, but a human analyst still makes the determination.

    Who investigates confirmed misconduct, and what enforcement follows?

    Once a concern is substantiated, Elsevier’s in-house Research Integrity and Publishing Ethics (RIPE) team leads the investigation, working with journal editors and, where warranted, the authors’ institutions. Elsevier states that it follows retraction guidelines developed by COPE, and confirmed problems resolve into one of three outcomes: a correction or erratum for errors that do not undermine the paper’s conclusions, an expression of concern where the investigation is inconclusive but doubts remain, or a retraction where the findings are no longer considered reliable.

    A recent case shows this enforcement ladder operating at scale. In a statement updated in May 2026, Elsevier disclosed that a comprehensive, multi-year audit of the journal Heliyon — using Check Integrity screening combined with manual review by RIPE analysts — had produced approximately 1,100 corrections to the scientific record, affecting around 3% of everything the journal had published across 12 years. Those 1,100 actions spanned corrections, expressions of concern and retractions; impacted authors were notified and given the chance to respond before editors made a final determination. Following the audit, Web of Science removed an indexing hold it had placed on Heliyon, and Elsevier said it was applying lessons from the case to workflows across its wider journal portfolio.

    Common questions about Elsevier’s integrity screening

    Does Elsevier use iThenticate for plagiarism screening?

    Yes. Elsevier’s journals route submitted manuscripts through Crossref Similarity Check, which is powered by iThenticate, comparing text against a large index of published articles and web content. Editors, not the software alone, judge whether flagged overlap reflects proper citation or genuine plagiarism before any editorial decision is made.

    Who investigates allegations of research misconduct at Elsevier?

    Elsevier’s in-house Research Integrity and Publishing Ethics (RIPE) team investigates confirmed concerns, working alongside journal editors and, where relevant, the authors’ institutions. Investigations follow COPE guidelines and typically involve requesting raw underlying data before any corrective action is taken.

    What is considered the most serious form of research misconduct?

    Fabrication and falsification of data are generally treated as the most serious forms of misconduct, alongside plagiarism, because they directly corrupt the reliability of the published record. Elsevier’s policies place these above lesser breaches such as citation gaming or unresolved authorship disputes.

    What happens after a research-integrity investigation confirms a problem?

    Confirmed issues lead to one of three outcomes: a correction for errors that do not undermine the findings, an expression of concern where evidence is inconclusive, or a retraction where the results are no longer considered reliable. All three are published and linked to the original article, per COPE guidance.

    What this means for institutions, authors and integrity offices

    For research administrators, the Heliyon case is a reminder that publisher-side screening is a complement to institutional processes, not a substitute for them. When a journal’s RIPE team contacts an institution about a flagged submission or published paper, that request typically triggers — and depends on — the institution’s own research-integrity office and record-keeping, an area covered in more detail in CASRAI’s research administration resources and its wider research-integrity dictionary entries. Authors, in turn, should expect to be asked for raw, unprocessed data or images at any stage, including years after publication, and should retain those records accordingly.

    Elsevier is not acting alone: it collaborates with other publishers through the STM Integrity Hub to detect duplicate submissions across the wider industry, reflecting a broader shift toward cross-publisher, not just single-journal, integrity infrastructure. As automated screening tools mature, the balance is likely to keep shifting toward earlier detection at submission — but the Heliyon audit shows that human RIPE analysts, not algorithms, remain the ones who make the final call on correction, expression of concern or retraction.

  • Plagiarism Detection: iThenticate vs Turnitin

    Plagiarism detection software for research integrity offices splits into two distinct product lines from the same corporate family: iThenticate, built for pre-publication manuscript and dissertation screening against scholarly literature, and Turnitin, built for coursework screening against a global repository of student papers. Choosing between them depends on what is being screened — a manuscript bound for a journal, or a student thesis — not on which tool has the higher marketing score.

    Plagiarism detection software is a text-similarity system that compares a submitted document against a reference database — web pages, journal articles, or previously submitted papers — and returns a similarity report for human review, not an automated verdict of misconduct.

    What are iThenticate and Turnitin, and how do they differ?

    iThenticate and Turnitin are sibling products of Turnitin, LLC (formerly iParadigms), sharing an underlying text-similarity engine but built for different markets. iThenticate targets researchers, faculty and publishers screening manuscripts, theses and grant applications before submission or publication, while Turnitin targets instructors screening student coursework, typically through a learning-management-system integration such as Canvas or Blackboard.

    Turnitin was acquired by Advance Publications, the media group that also owns Condé Nast, in 2019 for a reported $1.75 billion — a detail worth knowing because both product lines now sit under one commercial parent, which shapes how licensing bundles and feature roadmaps (including AI-writing detection) are rolled out across the two tools.

    How does grey-literature and database coverage compare?

    Coverage is the single biggest practical differentiator for a research integrity office, and it is where most consumer-facing “best plagiarism checker” roundups say nothing useful, because they compare tools built for essays, not manuscripts.

    iThenticate’s index is weighted toward licensed scholarly publisher content rather than student submissions. A large share of that access runs through Crossref’s Similarity Check service (originally launched as CrossCheck in 2008), which lets participating publishers cross-reference manuscripts against one another’s published content using the iThenticate engine. Turnitin’s index, by contrast, is anchored by its own repository of previously submitted student papers, built up over two decades of institutional use — a strength for catching student-to-student collusion, but a weaker signal for detecting overlap with the peer-reviewed literature.

    Neither tool has comprehensive built-in coverage of grey literature — preprint servers such as arXiv, bioRxiv and SSRN, institutional repositories, conference proceedings, or non-English regional journals — by default. Research integrity offices handling multidisciplinary manuscripts should treat both as a first-pass screen and budget for supplementary manual searches for grey-literature-heavy submissions, particularly in physics, computer science and economics, where preprint-first publishing norms are strongest.

    Factor iThenticate Turnitin
    Primary audience Researchers, faculty, publishers Instructors, students
    Core database strength Scholarly publisher content via Crossref Similarity Check Global repository of student-submitted papers
    Typical workflow entry point Stand-alone web app or publisher submission system LMS integration (Canvas, Blackboard, Moodle)
    Submission repository add-back Private, user-managed folders by default Papers commonly added to the global student repository
    AI-writing detection Added with iThenticate 2.0 (2024) Live since April 2023
    Grey literature / preprint coverage Limited; not comprehensive by default Limited; not comprehensive by default

    How should offices handle false positives and similarity scores?

    A high similarity score is not, by itself, evidence of plagiarism, and treating it as one is the most common misuse of these tools by inexperienced reviewers.

    Both engines flag methods sections, standard nomenclature, ethics-declaration boilerplate, direct quotations and reference lists as “matches” even when correctly cited — a false-positive pattern that is worse in STEM disciplines with formulaic methods language. The Committee on Publication Ethics (COPE) has published discussion guidance on text recycling warning that similarity percentages must be interpreted by a human reviewer against citation context, not treated as an automated pass/fail gate. The ICMJE Recommendations similarly treat overlapping and duplicate publication as an editorial judgement matter, not a software output.

    Practical guardrails research integrity offices commonly apply:

    • Exclude quotations and bibliography from the headline similarity score, and review flagged matches individually rather than acting on the aggregate percentage.
    • Use a similarity band (many institutions apply an initial screening range around 15–20% overall similarity, excluding quotes and references) purely as a triage trigger for closer human review — never as an automatic misconduct threshold.
    • Distinguish self-plagiarism (recycled text from a researcher’s own prior publications) from third-party plagiarism; the two require different institutional responses and different policy citations.
    • Route AI-writing-detection flags through the same human-review step as similarity flags — both tools’ AI detectors are probabilistic classifiers, not proof of misconduct, and both vendors publish accuracy caveats for their own models.

    What are the institutional licensing differences?

    Licensing is negotiated at institutional or publisher level for both tools, not purchased per document — a common procurement mistake is assuming individual-researcher pricing applies.

    iThenticate is typically licensed directly to a research office, graduate school or publisher, with API integration into manuscript-submission platforms (such as Editorial Manager or ScholarOne) the standard deployment pattern for journals and university presses. Turnitin is typically licensed at whole-institution level through the teaching and learning technology budget and bundled with the LMS, so a research integrity office wanting Turnitin for thesis screening often negotiates access through that existing contract rather than procuring it independently. Offices should confirm whether AI-writing detection, added by both vendors as a distinct module rather than a default feature, is included in the base licence or billed separately.

    Which tool should a research integrity office choose?

    For pre-publication manuscript, dissertation and grant-application screening, iThenticate is the better-fitted tool: its scholarly-publisher-weighted database and default private-folder handling protect the confidentiality of unpublished work, which matters when a submission may still be under active peer review elsewhere.

    For undergraduate and taught-postgraduate thesis screening, where the goal includes both integrity checking and student education, Turnitin’s LMS-integrated workflow and student-paper repository are the better fit, provided the office has a clear policy on whether submissions are added to the global repository — a live consideration for a thesis that a student may later adapt into a journal article.

    Many research-intensive institutions run both: iThenticate for faculty and doctoral output heading toward publication, Turnitin for coursework and taught-programme theses, coordinated through the same research integrity office policy rather than treated as competing tools solving the same problem.

    Answer-first Q&A

    What is the best plagiarism detection software for research integrity offices?

    There is no single “best” tool; the right choice depends on document type. iThenticate is better suited to pre-publication manuscripts, dissertations and grant applications because of its scholarly-database weighting and confidential handling. Turnitin is better suited to coursework and taught theses because of its LMS integration and student-paper repository.

    Which software can detect plagiarism in grey literature?

    Neither iThenticate nor Turnitin offers comprehensive built-in coverage of preprints, institutional repositories or conference proceedings. Research integrity offices reviewing grey-literature-heavy submissions should supplement automated screening with manual searches of preprint servers such as arXiv, bioRxiv and SSRN, particularly in disciplines with strong preprint-first publishing norms.

    Does Turnitin detect AI writing?

    Yes. Turnitin’s AI writing detection feature has been live since April 2023 and is integrated into its standard similarity report. iThenticate gained an equivalent capability with the iThenticate 2.0 platform release in 2024. Both vendors publish caveats that AI-detection scores are probabilistic, not definitive proof of AI authorship.

    Can I check Turnitin submissions for free?

    No. Turnitin does not offer a free public checking tier; access requires an institutional licence, typically bundled into an institution’s learning-management-system contract. Individual researchers or offices without an existing institutional subscription cannot submit documents to Turnitin directly.

    Implications for research integrity offices

    The practical decision is a policy question before it is a procurement one: an office needs a written position on similarity-score thresholds, self-plagiarism handling, repository add-back consent, and AI-detection escalation before either tool is deployed at scale — otherwise reviewers apply inconsistent judgement to functionally identical reports. Coordinating with the institution’s research administration function on licensing, and with policy on authorship disputes where overlap flags intersect with contested co-authorship claims, keeps the tool’s output anchored to institutional policy rather than treated as a standalone verdict.

    As both vendors extend AI-writing detection and publishers expand Crossref Similarity Check participation, the coverage gap between “student work” and “scholarly literature” databases is likely to narrow — but grey literature will remain the persistent blind spot for the foreseeable future, and no procurement decision should assume otherwise.

  • Advanced Plagiarism Detection: Integrity Auditing in the Era of Generative AI

    1. Introduction to the Role of Plagiarism Detection in Scholarly Infrastructure

    In the contemporary landscape of global science, open research practices, and institutional data governance, establishing robust standards is crucial. The integration of Plagiarism Detection represents a landmark advancement in addressing long-standing hurdles in scholarly communication, administrative reporting, and metadata curation. This extensive guide provides an expert-level breakdown of the operational frameworks, specifications, and systemic requirements surrounding Plagiarism Detection in 2026.

    As academic funders and research ministries worldwide enforce increasingly rigid compliance pathways, universities must transition from ad-hoc administrative workflows to unified, persistent-identifier-driven schemas. Implementing Plagiarism Detection is not merely a technical adjustment; it is a strategic necessity that secures institutional research visibility, ensures frictionless metadata reporting, and compounds the impact of scientific investments.

    2. Technical Architecture and Core Specifications

    Underpinning the deployment of Plagiarism Detection is a set of rigorous, machine-actionable specifications designed to operate seamlessly across diverse platforms. This environment relies heavily on how similarity-matching systems like iThenticate and Crossref Similarity Check function on a technical level. By establishing clear, standardized data exchange layers, organizations can bypass the siloed architectures that have traditionally plagued research information networks.

    A key focus of these specifications is the preservation of structural metadata integrity. This is achieved by mapping data payloads to recognized open vocabularies, such as Dublin Core, Schema.org, and custom JSON-LD graphs. This ensures that every scientific output—be it a journal article, a software version, or an administrative record—carries citable provenance tags, enabling automated indexing and cross-referencing by global citation engines such as OpenAlex and Crossref.

    3. Institutional Challenges, Workflows, and Solutions

    While the administrative and scientific benefits of Plagiarism Detection are indisputable, the practical deployment across universities and libraries reveals significant hurdles. Major friction points include addressing the limitations of text matching in the age of generative AI, paraphrasing tools, and securing academic integrity. Faculty reluctance, legacy software limitations (such as outdated CRIS databases), and the high administrative cost of manual curation represent substantial barriers to widespread compliance.

    Overcoming these implementation bottlenecks requires a systemic, top-down commitment to administrative automation. Institutions must deploy modern API middleware to coordinate data transfers between local enclaves and global public registries, eliminating manual data-entry redundancy. Furthermore, university promotion and tenure committees must update their evaluative rubrics to formally credit researchers for complying with these modern curation workflows, establishing a cultural positive-feedback loop.

    4. Technical Evaluation and Integration Matrix

    Integration Domain Primary Objective Core Interoperability Standard Friction Mitigation Strategy
    Persistent Identification Ensure permanent, citable links across registries. Unique URI / DOI Resolve Systems Implement automated metadata harvesting on ingest.
    Metadata Exchange Frictionless transfer between CRIS and repositories. JSON-LD / XML Schema Mapping Deploy standardized REST APIs with OAuth 2.0.
    Compliance Auditing Track, verify, and report on policy adherence. Standardized SQL / GraphQL Querying Generate real-time compliance scorecards for PIs.

    5. Five-Step Institutional Implementation Roadmap

    • Step 1: Institutional Alignment & Sign-off — Establish an official cross-departmental committee representing the library, IT services, and the research office to draft the institutional deployment charter for Plagiarism Detection.
    • Step 2: API & Schema Mapping — Audit existing repository databases and map local metadata schemas to match the international JSON-LD specifications required for Plagiarism Detection.
    • Step 3: Middleware Integration & SSO — Configure enterprise middleware layers to handle automated data harvesting and synchronize access using Single Sign-On (SAML/Shibboleth).
    • Step 4: Training & Support Networks — Deploy interactive workshops, dedicated helpdesks, and online documentation to educate researchers, metadata curators, and administrative staff.
    • Step 5: Automated Verification & Auditing — Launch real-time validation checks and annual data-quality audits to measure compliance rates and automatically identify and correct orphaned records.