Release notes

v3.0.0 released 2026-07-27 · data_version 2026.2

v3.0.0 is a corrected release. It changes values in existing columns, not just the schema, so analyses built on v2.6.0 or v2.7.0 need to be re-run. It is the version described in the accompanying paper, and the first whose published bytes match that manuscript.

922,097
Positions
745,125
Unique editors
15,168
Journals
48
Publishers
189
Countries
77
Columns

What changed

1
Fixed

board_pct_female was constant at 0

In v2.6.0 and v2.7.0 this column read 0 for every one of the 922,097 rows, quietly reducing any board-gender analysis to a constant. A gender-wipe regression introduced in v2.6.0 had cleared the per-row gender values that the board-statistics stage reads as its input; because an all-zero result is arithmetically valid, nothing raised an error. The inputs are restored and the denominator now matches the codebook definition: the resolved gender count (male plus female) rather than total board size, so boards carrying many unknown inferences are not artificially depressed.

907,086 rows (98.4%) now carry a non-zero value; the mean board is 31.5% female.

2
New column

editor_key is published

The composite identity key behind the 745,125 unique-editor figure is now a column, so that count is reproducible without reconstructing the key yourself. It resolves in priority order and is prefixed with the tier that produced it: ORCID iD (346,713 records), ROR-resolved institution plus name (294,399), or affiliation plus name (280,985). The ORCID and ROR tiers are the reliable ones; the lowest tier is name-based, so distinct people sharing a name and affiliation string can still collide there.

Requested by a reviewer of the accompanying paper.

3
New column

openalex_author_id restores OpenAlex interoperability

Earlier releases shipped the derived bibliometrics (h-index, publications, citations, academic age) without exposing the identifier they came from, so you could neither audit a match nor join back to OpenAlex. The Author identifier is now published.

Populated on 531,437 records (57.6%), which is 98.7% of the 538,550 records that matched an OpenAlex author.

4
New columns

Provenance flags let you see how a record was resolved

Three columns replace blind trust with a visible match strength. oa_match_method records how the OpenAlex profile was found: orcid (344,957 records), name_ror (107,173), name_only (86,420) or unmatched (383,547). name_is_initials marks records whose given name is initials only, which blocks gender inference and weakens name matching. orcid_shared_flag marks iDs that map to several distinct name strings, usually a data-entry error at the source. Flagged records are retained, not removed.

name_is_initials true on 26,763 records (2.9%); orcid_shared_flag true on 239. For bibliometric work, consider restricting to the orcid and name_ror match tiers.

5
Fixed

role_std contamination repaired, senior_editor added

2,359 IEEE rows carried raw section headings in role_std, a standardized column that should only ever hold canonical values; this inflated the distinct-value count and corrupted any group-by on role. Those rows are re-mapped, and a senior_editor category has been added for 5,005 positions previously absorbed into other.

role_std now holds exactly ten canonical values.

6
Recomputed

Downstream statistics recomputed

All aggregates were recomputed on the corrected data. The largest movement is multi-board editorship, which drops from 25.3% to 15.0% of editors serving two or more boards. The earlier figure came from exact name matching, which merged distinct homonymous individuals into single editors and so overstated multi-board service by roughly ten percentage points. The new figure uses editor_key, which separates them wherever an ORCID iD or a resolved institution distinguishes the people involved.

Treat 15.0% as a corrected estimate: the residual name-tier collisions push in the same direction, just far less.

If you used a previous version

Analyses that touch only the collected columns (publisher, journal, editor, role, affiliation, source_url, scraped_at) are unaffected; those values are unchanged since v2.7.0. Re-run anything that touches the following.

Re-run Why
board_pct_female, and anything derived from it It was constant at 0. Every result conditioned on board gender composition from v2.6.0 or v2.7.0 is invalid, not merely imprecise. This is the one that silently produces publishable-looking nonsense.
role_std group-bys 2,359 rows held non-canonical values and 5,005 positions moved from other into senior_editor. Counts for other and any per-role rate will shift.
Multi-board and editor-count analyses If you built your own identity key by matching on editor name, your unique-editor count is too low and your multi-board share is too high (25.3% against a corrected 15.0%). Switch to the published editor_key.
Any filter on gender == 'andy' The legacy androgynous value is retired. gender now holds only male, female and unknown, so that branch is dead code.

If you used v2.0.0 or earlier, all of the above applies, plus the ISSN resolution fixes in v2.6.0 (71 wrong-ISSN journals) and the WGND 2.0 gender rebuild in v2.7.0.