Verified Rigor RecordRigor Reviewed

Rigor-Reviewed Manuscript

The trouble with triplets in biodiversity informatics: a data-driven case against current taxonomic name usage

Name: Verified Rigor Record — The trouble with triplets in biodiversity informatics: a data-driven case against current taxonomic name usage
Item: The trouble with triplets in biodiversity informatics: a data-driven case against current taxonomic name usage
Rating: 94
Author: Αlpha¹

Paper source

Open DOI

Αlpha¹ Editorial

This rigor review was examined and confirmed by Αlpha¹ Editorial · July 5, 2026

Αlpha¹ Rigor Review

Rigor Reviewed

PASS

Rigor holds up · Computational Study

Eight dimensions — click a segment for details

Critical

High-priority

Model-reported confidence: highReviewer agreement: moderateEngine: 7.5.0Source: full text

Not verified in this report

No reported statistical tests were found to recompute.

This Αlpha¹ Rigor Review uses AI Rigor Reviewers trained on a curated corpus of high-fidelity and retracted papers, with expert supervision and curation. It can still make mistakes; verify each finding against the source before relying on it.

This published computational study is methodologically sound with exemplary data/code sharing practices. The main robustness concern is a small arithmetic discrepancy in the tabulated counts (Tables 1 vs 2 for GenBank and BOLD), which warrants an erratum. Software versions are not explicitly stated in the paper text, though a Docker container captures the environment. The study's descriptive conclusions are proportional to the evidence presented.

The evaluation considered six applicable rigor dimensions (scientific premise, study design, key resources, statistical analysis, data code availability, reporting transparency). Two dimensions (biological variables, ethical approvals) were rated not applicable. The three independent reviewers generally agreed, with the main divergence on study design (one 'warn' vs two 'pass') and key resources (one 'warn' vs two 'pass'), resolved here by weighing the evidence. The 'statistics' verification component found no inferential tests to recompute. Five references could not be located in Crossref/OpenAlex (flagged as potential fabrication signals).

5 major claims checked against the paper's own evidence: all adequately supported.

2 integrity concerns flagged (0 high).

Rigor

Eight Dimensions5 pass · 1 warn

5 major claims1 partial4 supported

The introduction cites the GBIF 2009 report and other papers on identifier challenges, acknowledges limitations of prior discussions (theoretical only), and states a clear rationale for empirically testing identifier deployment. The study addresses a gap by quantifying real-world usage.

Sub-criteria

prior work citedADEQUATE

premise rationaleADEQUATE

limitations addressedADEQUATE

Per reviewer (3) — the votes behind the verdict

PASSReviewer 1· 95% conf

The paper clearly establishes its scientific foundation by citing relevant prior work on biodiversity identifiers and logically linking it to the study's goal of evaluating current identifier practices.

Evidence

direct quote[Introduction, last paragraph]

“The goal of our study was to determine how the DwC Triplet is used in practice and whether currently available DwC Triplets are sufficient to link digital biodiversity records from one data publishing platform (e.g., VertNet) to records from another platform (e.g., Barcode of Life or GenBank).”

direct quote[Introduction, paragraph 2]

“The Global Biodiversity Information Facility released a 2009 report developed by a global panel of experts whose first words are "GBIF has identified the provision of identifiers for biodiversity objects as one of the central challenges to developing a global bioinformatics infrastructure", a sentiment shared by others.”

paraphrase[Introduction, last paragraph]

“The authors note that problems with DwC Triplets have been noted from first principles, but what has not been clear is how idiosyncratically they are deployed in practice, which this study quantifies.”

PASSReviewer 2· 95% conf

The paper clearly establishes the scientific foundation: it cites prior work on identifier challenges, provides a logical rationale for studying triplet quality, and acknowledges limitations of prior approaches.

Evidence

direct quote[Introduction, paragraphs 2-6]

“The Global Biodiversity Information Facility released a 2009 report developed by a global panel of experts whose first words are 'GBIF has identified the provision of identifiers for biodiversity objects as one of the central challenges to developing a global bioinformatics infrastructure'”

direct quote[Introduction, paragraph 6]

“The goal of our study was to determine how the DwC Triplet is used in practice and whether currently available DwC Triplets are sufficient to link digital biodiversity records”

direct quote[Introduction, paragraph 6]

“Much less clear is how well DwC Triplets are deployed in the wild. Do current curatorial practices lead to the creation of DwC Triplets that serve the needs of linked data?”

PASSReviewer 3· 95% conf

The paper establishes a clear scientific premise by citing prior work on identifier challenges, providing a logical rationale for the study, and addressing limitations of previous discussions.

Evidence

direct quote[Introduction, paragraphs 1-4]

“The biodiversity informatics community has discussed aspirations and approaches for assigning globally unique identifiers (GUIDs) to biocollections for nearly a decade.”

direct quote[Introduction, final paragraph]

“The goal of our study was to determine how the DwC Triplet is used in practice and whether currently available DwC Triplets are sufficient to link digital biodiversity records...”

direct quote[Introduction, paragraph 5]

“what has not been nearly as clear is just how idiosyncratically Darwin Core Triplets are deployed in practice”

The paper provides detailed methods for data assembly from VertNet, GenBank, and BOLD, including specific URL sources, parsing algorithms (regular expressions for canonical triplets, a multi-step algorithm for coerced variants), and matching procedures (shell scripts and SQL). Power analysis is not applicable for this type of data mining study. Randomization and blinding are not applicable. Inclusion/exclusion criteria are defined through filtering steps (e.g., excluding bacterial divisions from GenBank, filtering based on specimen_voucher field existence). Data curation steps are described, and controls are inherent in the comparative analysis across repositories.

Sub-criteria

controlsINADEQUATE

power analysisN/A

blinding levelsN/A

outlier handlingNOT REPORTED

randomization unitN/A

inclusion exclusionADEQUATE

randomization methodN/A

replicate distinctionN/A

independent replicationN/A

Per reviewer (3) — the votes behind the verdict

WARNReviewer 1· 70% conf

The study design is descriptive and data-driven but lacks a pre-specified analysis plan and power justification; inclusion/exclusion criteria for data filtering are not fully pre-specified.

Evidence

absence[Materials and Methods]

No sample size or power analysis is reported.

direct quote[Materials and Methods, GenBank data assembly]

“We then filtered these records by first checking for existence of the specimen_voucher field, parsing and then removing those records that were clearly not from vertebrate biocollections based on expert-opinion of two of the authors.”

direct quote[Materials and Methods, Recognizing Darwin Core Triples]

“A regular expression to accept canonical DwC Triplets is “[A-Z]{2,8}\:[A-Z][a-z]+\:.*[0-9]+.*”.”

PASSReviewer 2· 90% conf

The computational study design is well-described, with clear data assembly procedures, parsing algorithms, and matching criteria across three repositories.

Evidence

direct quote[Materials and Methods, all subsections]

“URLs for DarwinCore Archives ... were taken from http://ipt.vertnet.org:8080/ipt/(mid-August 2013)”

direct quote[Materials and Methods, Recognizing Darwin Core Triples in Datasets]

“Break a text value suspected of containing a DwC Triplet into fragments by semicolons and open parenthesis ... Partition each fragment into tokens ...”

absence[Materials and Methods]

No explicit handling of outliers or anomalous data records is reported

PASSReviewer 3· 90% conf

The study design is appropriate for computational analysis with clear data assembly and matching methodology.

Evidence

paraphrase[Materials and Methods, VertNet data assembly, GenBank data assembly, BOLD data assembly]

“The authors describe how they harvested VertNet records from an IPT instance, filtered GenBank records by division and specimen_voucher field, and downloaded BOLD Chordata records.”

direct quote[Materials and Methods, Recognizing Darwin Core Triples in Datasets]

“A regular expression to accept canonical DwC Triplets is “[A-Z]{2,8}\:[A-Z][a-z]+\:.*[0-9]+.*”.”

direct quote[Materials and Methods, Determining matches across repositories]

“We used shell scripts in the filesystem and SQL in a PostgreSQL relational database to ascertain matching DwC Triplet between repositories.”

The study focuses on identifier strings and does not involve living organisms, animal models, or human participants. No reporting of sex, age, strain, or housing conditions is needed.

Sub-criteria

demographicsN/A

sex reportedN/A

sex justifiedN/A

age weight healthN/A

housing conditionsN/A

species strain sourceN/A

Per reviewer (3) — the votes behind the verdict

N/AReviewer 1· 95% conf

The study analyzes metadata records, not biological subjects; thus biological variables are irrelevant.

N/AReviewer 2· 95% conf

The study analyzes text identifiers and metadata records, not biological subjects, so biological variable reporting is not applicable.

Evidence

direct quote[Abstract]

“We gathered Darwin Core Triplets from a subset of VertNet records, along with vertebrate records from GenBank and the Barcode of Life Data System”

N/AReviewer 3· 95% conf

The study does not involve biological subjects; it analyzes data records (identifiers) from biodiversity databases.

Evidence

absence[Entire paper]

No biological variable reporting required; study focuses on identifier formatting.

All data are from public repositories (VertNet, GenBank, BOLD) and no ethics approval is required for such secondary data analysis.

Sub-criteria

iacuc statementN/A

informed consentN/A

irb ethics statementN/A

regulatory complianceN/A

Per reviewer (3) — the votes behind the verdict

N/AReviewer 1· 95% conf

The study uses only publicly available data from databases; no new human or animal subjects data were collected.

N/AReviewer 2· 95% conf

The study uses only publicly available, fully de-identified database records, not human or animal subjects, so ethical approvals are not applicable.

Evidence

direct quote[Materials and Methods]

“We gathered and analyzed Darwin Core Triplets ... from three repositories: VertNet (vertnet.org), GenBank (http://www.ncbi.nlm.nih.gov) and the Barcode of Life Data System (BOLD; http://www.boldsystems.org/)”

N/AReviewer 3· 90% conf

The study uses only publicly available data from major biodiversity databases; no new human or animal subject data collected.

Evidence

paraphrase[Materials and Methods]

“The paper assembled data from VertNet, GenBank, and BOLD, all publicly accessible repositories.”

The study uses no antibodies, cell lines, or biological reagents. The software tools are well-identified: PostgreSQL, Docker, and the text parsing scripts are mentioned with versions and URLs where available. The code repository on GitHub (https://github.com/TomConlin/trouble_w_triples) and Docker container are provided. Data are deposited in Dryad with a DOI (doi:10.5061/dryad.4b115).

Sub-criteria

mycoplasma testingN/A

reagents identifiedN/A

organisms identifiedN/A

antibodies identifiedN/A

cell line authenticationN/A

software tools identifiedADEQUATE

Per reviewer (3) — the votes behind the verdict

WARNReviewer 1· 80% conf

Software tools are identified but without version numbers, limiting reproducibility; no other biological or chemical resources are used.

Evidence

direct quote[Materials and Methods, VertNet data assembly]

“The resulting files were loaded into a PostgreSQL ( http://www.postgresql.org/ ) database.”

paraphrase[Data and code availability]

“The code and data are available on GitHub and in a Docker container, but no version numbers for programming languages or libraries are provided.”

PASSReviewer 2· 85% conf

The paper does not use biological/chemical resources but identifies all key software tools and data repositories with names, versions, URLs, and persistent identifiers.

Evidence

direct quote[Materials and Methods, Data and code availability]

“All data and code used in this project are available on GitHub (https://github.com/TomConlin/trouble_w_triples)”

direct quote[Materials and Methods, Data and code availability]

“All the data is also available in Dryad (http://dryad.org) Data identifier: doi:10.5061/dryad.4b115 for archival purposes”

PASSReviewer 3· 85% conf

Custom code and data are provided in public repositories; software tools are identified adequately.

Evidence

direct quote[Data and code availability]

“All data and code used in this project are available on GitHub ( https://github.com/TomConlin/trouble_w_triples ).”

paraphrase[Materials and Methods, VertNet data assembly, Data and code availability]

“The authors mention using PostgreSQL for database management and Docker for environment reproduction.”

The study uses descriptive statistics and does not perform inferential tests. Software (PostgreSQL) is identified without version. Table 2 totals for GenBank and BOLD do not match the coerced totals from Table 1, indicating possible minor errors in data aggregation.

Sub-criteria

tests namedN/A

exact p valuesN/A

effect sizes ciN/A

data presentationADEQUATE

software identifiedINADEQUATE

assumptions verifiedN/A

mathematical plausibilityWARN

Per reviewer (3) — the votes behind the verdict

WARNReviewer 1· 70% conf

Statistical reporting is largely descriptive and adequate, but software version is not reported, and there are internal inconsistencies in the tabulated counts.

Evidence

paraphrase[Table 1 and Table 2]

“In Table 1, GenBank coerced DwC Triplets count is 281,966. In Table 2, the sum of syntactic only (1,984), missing data only (93,947), and both (186,128) is 282,059, a discrepancy of 93.”

paraphrase[Table 1 and Table 2]

“In Table 1, BOLD coerced DwC Triplets count is 63,350. In Table 2, the sum of the three categories is 64,393, a discrepancy of 1,043.”

PASSReviewer 2· 88% conf

The analysis is primarily descriptive (counts, percentages, classifications) with no inferential statistics, so statistical testing criteria are largely not applicable; the descriptive results are clearly presented.

Evidence

absence[Results]

No inferential statistics are reported

direct quote[Materials and Methods, VertNet data assembly and Determining matches across repositories]

“The resulting files were loaded into a PostgreSQL (http://www.postgresql.org/) database”

direct quote[Results, Tables 1-3]

“Table 1 Summary of DwC Triplets per repository. Repository | Total records examined | Records w/specimen info. | Canonical DwC Triplet | Coerced DwC Triplet”

WARNReviewer 3· 70% conf

The paper presents descriptive statistics only. There is a small arithmetic discrepancy between Tables 1 and 2 for GenBank coerced counts.

Evidence

direct quote[Table 1 and Table 2]

“Table 1: GenBank coerced: 281,966. Table 2: syntactic only 1,984 + missing data only 93,947 + both 186,128 = 282,059.”

paraphrase[Results, Tables 1-3, Figure 1]

“The authors present three tables summarizing counts of canonical/coerced triplets and matches between repositories.”

The paper provides a data availability statement and specifies concrete access routes: GitHub for code and Dryad (DOI: 10.5061/dryad.4b115) for data, plus a Docker container for environment reproduction.

Sub-criteria

code sharingADEQUATE

accession numbersADEQUATE

repository depositADEQUATE

data availability statementADEQUATE

Per reviewer (3) — the votes behind the verdict

PASSReviewer 1· 98% conf

Data and code are fully available and clearly linked, including archival deposition in Dryad and a Docker container for reproducibility.

Evidence

direct quote[Data and code availability]

“All data and code used in this project are available on GitHub ( https://github.com/TomConlin/trouble_w_triples ). ... All the data is also available in Dryad ( http://dryad.org ) Data identifier: doi:10.5061/dryad.4b115.”

PASSReviewer 2· 95% conf

All data and code are fully available: GitHub repository, Docker container, and Dryad archival deposit with persistent DOI.

Evidence

direct quote[Materials and Methods, Data and code availability]

“All data and code used in this project are available on GitHub (https://github.com/TomConlin/trouble_w_triples)”

direct quote[Materials and Methods, Data and code availability]

“All the data is also available in Dryad (http://dryad.org) Data identifier: doi:10.5061/dryad.4b115 for archival purposes”

direct quote[Materials and Methods, Data and code availability]

“we have made the data, source, and functional environment available as a Docker (http://www.docker.com/) container (available here: https://registry.hub.docker.com/u/tomc/trouble_w_triples/)”

PASSReviewer 3· 95% conf

Data and code are fully available: GitHub repository, Dryad deposition with DOI, and Docker container.

Evidence

direct quote[Data and code availability]

“All the data is also available in Dryad ( http://datadryad.org ) Data identifier: doi:10.5061/dryad.4b115”

direct quote[Data and code availability]

“All data and code used in this project are available on GitHub ( https://github.com/TomConlin/trouble_w_triples ).”

Methods are sufficiently detailed for replication; all outcomes are reported; limitations are discussed; conclusions match the evidence; funding and conflicts are disclosed.

Sub-criteria

funding coiADEQUATE

trial registrationN/A

reporting guidelineN/A

methods completenessADEQUATE

all outcomes reportedADEQUATE

limitations discussedADEQUATE

conclusions proportionalADEQUATE

Per reviewer (3) — the votes behind the verdict

PASSReviewer 1· 95% conf

The manuscript is transparent and complete, with detailed methods, funding disclosure, and proportional conclusions.

Evidence

direct quote[Funding Statement]

“This work was formulated as part of this BiSciCol project ... which was supported by the National Science Foundation (DBI-0956371, DBI-0956350, and DBI-0956426).”

direct quote[Competing Interests]

“Co-author Robert Guralnick is a PLOS ONE Editorial Board member.”

paraphrase[Discussion]

“The authors note that for VertNet data not from the curated IPT instance, triplets were much less consistent, and discuss challenges with Linkout data and multiple identifier fields.”

WARNReviewer 2· 88% conf

The paper is generally well-reported with complete methods, proportional conclusions, and funding/COI statements, but it does not reference a formal reporting guideline and the limitations section is relatively brief.

Evidence

absence[Methods]

No reporting guideline is referenced

direct quote[Discussion, paragraphs 2-3]

“The problems with the Darwin Core Triplet have long been noted ... but what has not been nearly as clear is just how idiosyncratically Darwin Core Triplets are deployed in practice”

direct quote[Funding Statement]

“This work was formulated as part of this BiSciCol project (http://biscicol.org/), which was supported by the National Science Foundation (DBI-0956371, DBI-0956350, and DBI-0956426)”

PASSReviewer 3· 95% conf

The paper reports methods in detail, discusses limitations, and provides proportional conclusions.

Evidence

paraphrase[Materials and Methods]

“The methods section spans several subsections detailing how data were assembled from each repository and how identifiers were parsed and matched.”

direct quote[Discussion]

“Our results suggest that DwC Triplets, when present, have hugely varying levels of quality, based directly on the source dataset.”

direct quote[Funding Statement and Competing Interests]

“This work was formulated as part of this BiSciCol project ... supported by the National Science Foundation (DBI-0956371, DBI-0956350, and DBI-0956426).”

2 copyedit issues flagged: mostly consistency, other.

Checked 13 references: 8 verified — 5 unresolved.

Reproducibility

7 data/code links checked; 2 live, 2 dead.

Αlpha¹ Rigor Action ItemsFinal pass before journal submission

As a post-publication audit, this paper is largely robust but has specific issues that an informed reader should weigh: (1) the numeric discrepancy in Tables 1 and 2 for GenBank and BOLD coerced counts requires a correction to maintain data integrity; (2) five references could not be verified in any registry and warrant author clarification; (3) two repository links were dead. The core findings (that DwC Triplets are inconsistently deployed and insufficient for cross-repository linking) are likely valid despite these gaps, but a formal erratum addressing the count discrepancy and reference verification would strengthen trust.

1.
HIGHstatistics
Issue an erratum to reconcile the count discrepancy between Table 1 (total coerced) and Table 2 (sum of subcategories) for GenBank (off by 93) and BOLD (off by 1,043) — verify the raw data and correct one or both tables.
Internal inconsistency in reported counts undermines data integrity; even a small error may erode reader confidence.
2.
HIGHreporting
Verify the 5 references flagged as 'not found in registry' (titles listed in citation check) by checking DOIs or providing alternative citations; if any cannot be confirmed, correct or remove them to avoid fabrication concerns.
Unresolved references are a high-integrity signal; readers and journal editors will expect author clarification.
3.
HIGHdata code
Fix or replace the 2 dead repository links identified by the reproducibility checker (e.g., update URLs or ensure the Docker container is still accessible).
Dead links break the reproducibility promise of the data/code availability statement.
4.
MEDIUMrigor
Add explicit version numbers for all key software tools (PostgreSQL, shell scripting environment, any R/Python libraries if used) in the Materials and Methods section, or add a software environment table.
Versioned software identification improves long-term reproducibility even though a Docker container is provided.
5.
MEDIUMrigor
Expand the Limitations subsection in the Discussion to formally address potential biases such as the restriction to vertebrate records, the snapshot nature of the data, and the completeness of the parsing algorithm.
A more structured limitations section helps readers interpret the generalizability of the findings.
6.
MEDIUMrigor
Add an explicit statement in the 'Recognizing Darwin Core Triples in Datasets' section describing how unparseable or anomalous identifier strings were handled (e.g., excluded from analysis, counted as errors).
Clarifying outlier handling ensures the analysis pipeline is fully transparent.
7.
MEDIUMrigor
Tag the GitHub repository with a specific release version (e.g., v1.0) corresponding to the version used in the paper, and reference that release in the paper.
A stable version tag prevents ambiguity from ongoing repository changes.
8.
LOWcopyedit
Fix the formatting of 'Doublet- Doublet' in Table 3 to 'Doublet-Doublet' (remove extra space) for consistency with 'Triplet-Doublet' and 'Triplet-Triplet'.
Minor formatting inconsistency detracts from professional presentation.
9.
LOWreporting
Consider adding a reference to a formal reporting guideline (e.g., RECORD for studies using routinely-collected data, or a custom checklist for informatics studies) in the Methods section.
While not critical for this study type, reporting guidelines improve transparency and are increasingly expected by journals.
10.
LOWrigor
Provide a flow diagram for each repository's data assembly pipeline (number of records at each filtering step) to improve traceability.
Visual flow diagrams make inclusion/exclusion decisions immediately clear to readers.

Full text (36,012 chars)Analyzed: Jul 5, 2026

Αlpha¹ assesses methodological rigor, not the importance of the findings. See how we calibrate →