| 1 |
|
−% part03_data — to be written (Phase 7) |
|
1 |
+% ============================================================================ |
|
2 |
+% Part III — Data and Systematic Review Protocol |
|
3 |
+% Written by Agent L (Part III instance), 2026-11-03. Every corpus number is a macro from tables/numbers.tex |
|
4 |
+% (generated by tables/make_numbers.py from data/metadata/prisma_counts.json and linkage_report.json). |
|
5 |
+% Sources of truth: RESEARCH_PLAN.md §2–§3, protocol/PROTOCOL.md, protocol/amendments.csv, |
|
6 |
+% reports/PHASE0_FEASIBILITY.md, data/raw/README.md, ingestion/*.py, systematic_review/define_corpus.py. |
|
7 |
+% ============================================================================ |
|
8 |
+ |
|
9 |
+\section{Information sources and conditions of access} |
|
10 |
+\label{sec:data-sources} |
|
11 |
+ |
|
12 |
+A field-level mapping study stands or falls with the bibliographic databases on which it is built. The choice |
|
13 |
+of sources determines which works can be observed at all, how reliably they can be dated and typed, whether |
|
14 |
+citation links are available, and under what licence derived data may be redistributed. This part documents |
|
15 |
+these choices for WP44 and reports, stage by stage, how the mapping corpus was assembled from the raw |
|
16 |
+sources. The exposition follows the order of the pipeline (identification, linkage, deduplication, |
|
17 |
+eligibility, scope, dating) and closes with the quality indicators and the research-integrity procedures that |
|
18 |
+govern every later analysis. The reporting structure is modelled on the PRISMA 2020 items that apply to a |
|
19 |
+mapping study \citep{page2021prisma,page2021prismaee}; items concerned with risk of bias and effect measures |
|
20 |
+have no counterpart in a bibliometric design and are replaced, as PRISMA-ScR does for scoping reviews |
|
21 |
+\citep{tricco2018prismascr}, by indicators of metadata quality and coverage (Section~\ref{sec:data-quality}). |
|
22 |
+The search-reporting recommendations of PRISMA-S \citep{rethlefsen2021prismas} are followed to the extent |
|
23 |
+that a database-scope strategy without keyword queries permits. |
|
24 |
+ |
|
25 |
+\subsection{Why a multi-source design} |
|
26 |
+ |
|
27 |
+No single database indexes computer science completely, and the gaps are not random. The venue-centred |
|
28 |
+coverage of DBLP, the publisher-centred coverage of Crossref, the preprint-centred coverage of arXiv and the |
|
29 |
+aggregating coverage of OpenAlex each miss a distinct part of the literature and type the part they do cover |
|
30 |
+in distinct ways. Comparative studies of bibliographic data sources have documented large differences in |
|
31 |
+coverage between Web of Science, Scopus, Dimensions, Crossref and Microsoft Academic |
|
32 |
+\citep{visser2021comparison,martinmartin2021comparison}, and the journal-level coverage of the two commercial |
|
33 |
+indexes is known to under-represent conference proceedings, which carry a large share of computer-science |
|
34 |
+output \citep{mongeon2016coverage}. For the open successor of Microsoft Academic, OpenAlex, the first |
|
35 |
+independent assessments report strong coverage of works with DOIs together with weaker and uneven metadata on |
|
36 |
+affiliations, document types and references \citep{alperin2024openalex,culbert2025openalex, |
|
37 |
+scheidsteger2023openalex,delgadoquiros2024completeness}. These findings motivate the design adopted here: one |
|
38 |
+source supplies the backbone (OpenAlex), a second supplies the definition of what counts as computer science |
|
39 |
+(DBLP), a third supplies the preprint layer and its dates (arXiv), and a fourth checks the coverage of a |
|
40 |
+subfield with a dense, curated venue structure (the ACL Anthology). Crossref is used for verification only. |
|
41 |
+ |
|
42 |
+\subsection{OpenAlex} |
|
43 |
+ |
|
44 |
+OpenAlex \citep{priem2022openalex} is the backbone of the corpus. It supplies, for every work, the |
|
45 |
+identifiers (OpenAlex~W identifier, DOI, arXiv identifier where present), the publication date and type, the |
|
46 |
+title and an inverted-index abstract where available, the venue (source) and its type, the authorships with |
|
47 |
+institutions and countries, the topic assignment at three levels (field, subfield, topic) with a primary |
|
48 |
+topic, the list of referenced works (the citation graph), the open-access status and licence, and the |
|
49 |
+field-weighted citation impact together with yearly citation counts. OpenAlex is released under the CC0 |
|
50 |
+public-domain dedication, which permits redistribution of record-level derived data. |
|
51 |
+ |
|
52 |
+Two access routes exist and both were used, for different purposes. The public snapshot is a versioned bulk |
|
53 |
+release in gzipped JSON Lines, published in a public S3 bucket; the release used here is dated |
|
54 |
+2026-10-14 and comprises 1{,}898 part files for the \emph{works} entity, 675.3~GB compressed, with a manifest |
|
55 |
+listing the record count of each file. The snapshot was streamed from the primary compute node, each file's |
|
56 |
+content length checked against the manifest and a SHA-256 of the compressed bytes recorded in a SQLite ledger |
|
57 |
+before parsing; every one of the 1{,}898 files parsed without error and the sum of the per-file record counts |
|
58 |
+equals the manifest total of \LinkSlimTotal{} works. Two outputs were written during this single pass. The |
|
59 |
+first is the full JSON record of every work carrying \emph{any} topic in OpenAlex field~17 (Computer Science) |
|
60 |
+with a publication year between 2018 and 2026, stored as Zstandard-compressed JSON Lines and partitioned by |
|
61 |
+the snapshot's own date partitions (\LinkOaCsRecords{} records, about 20~GB). The second is a \emph{slim} |
|
62 |
+table of every work in the snapshot (identifier, DOI, year, type, primary topic, subfield, field and domain, |
|
63 |
+citation count and a few flags), kept in Parquet so that works cited by computer-science papers but published |
|
64 |
+in other fields can be resolved for the interdisciplinary analyses of Part~VIII (decision D2 of |
|
65 |
+\texttt{RESEARCH\_PLAN.md}). Records flagged by OpenAlex as XPAC expansion records are retained at this stage |
|
66 |
+with their flag so that the exclusion decision can be taken, and counted, later (Section~\ref{sec:data-eligibility}). |
|
67 |
+The smaller entity snapshots (topics, subfields, fields, domains, sources, institutions, publishers, funders, |
|
68 |
+concepts) were downloaded the same day with a per-file SHA-256 ledger; author entities were not downloaded |
|
69 |
+because the authorship data embedded in each work record suffice for the analyses planned. |
|
70 |
+ |
|
71 |
+The second route is the REST API. Without an API key the public endpoint operates under a shared daily budget |
|
72 |
+of USD~0.10, list-and-filter calls are priced at USD~0.0001 each, and cursor paging is unavailable, so that a |
|
73 |
+single filtered query cannot return more than 10{,}000 results through basic paging. Single-record lookups by |
|
74 |
+identifier are free. The API was therefore used for two narrowly defined tasks. First, an incremental harvest |
|
75 |
+of works with any computer-science topic and a publication date between 2026-10-01 and 2026-11-02, intended |
|
76 |
+to capture records added after the snapshot was cut; the harvest is sliced by publication day and, where a day |
|
77 |
+exceeds the paging limit, split into records with a computer-science primary field and records without one. |
|
78 |
+Raw JSON pages are stored verbatim under a dated directory with a ledger of counts and cost, and the job |
|
79 |
+resumes on the following day when the budget is exhausted. Second, free single-record lookups by DOI serve as |
|
80 |
+one of the verification routes for the bibliography of this manuscript (Section~\ref{sec:data-integrity}). |
|
81 |
+A free API key, which would raise the daily budget, requires the principal investigator to act on an e-mail |
|
82 |
+and was deliberately not obtained without instruction; the mandate forbids assuming credentials that have not |
|
83 |
+been tested. |
|
84 |
+ |
|
85 |
+\subsection{DBLP} |
|
86 |
+ |
|
87 |
+The DBLP computer science bibliography \citep{ley2002dblp,ley2009dblp} is a curated, venue-centred index that |
|
88 |
+has for three decades defined, in practice, the set of journals and conference series regarded as computer |
|
89 |
+science. It is used here in that capacity: a work indexed by DBLP is in computer science by construction, and |
|
90 |
+DBLP venue streams feed the taxonomy of Part~IV. The complete XML dump (\texttt{dblp.xml.gz}, dated 2026-11-02 |
|
91 |
+22:39~UTC, 1.12~GB) was downloaded together with its DTD and MD5 checksum, the checksum verified, and the file |
|
92 |
+parsed with a validating XML parser into one row per publication record (articles, conference papers, |
|
93 |
+proceedings volumes, books, book chapters, doctoral and master's theses, data records; the \texttt{www} |
|
94 |
+person records are skipped). The whole archive was kept so that per-year counts are available for the |
|
95 |
+historical baseline and for context. The DBLP dump is released under the Open Data Commons Attribution licence |
|
96 |
+(ODC-BY~1.0). DBLP contributes, in addition to the scope definition, author person identifiers, venue streams, |
|
97 |
+and DOI links for most records; the \texttt{ee} fields were also scanned for arXiv URLs, with a result reported |
|
98 |
+in Section~\ref{sec:data-linkage}. |
|
99 |
+ |
|
100 |
+\subsection{arXiv} |
|
101 |
+ |
|
102 |
+The arXiv e-print repository \citep{ginsparg2011arxiv} is the main preprint channel of computer science and, |
|
103 |
+for the period under study, the place where a large share of the most cited work first appeared. Its |
|
104 |
+metadata are harvested through the OAI-PMH interface (\texttt{set=cs}, \texttt{metadataPrefix=arXiv}) in |
|
105 |
+monthly datestamp windows from January 2018 to 2 November 2026. The harvester waits at least 3.5~s between |
|
106 |
+requests and honours \texttt{Retry-After} headers; every raw XML page is kept verbatim as the immutable |
|
107 |
+snapshot and parsed afterwards into a single Parquet table. Two properties of OAI-PMH matter for what follows. |
|
108 |
+The \texttt{from}/\texttt{until} parameters filter on the record's \emph{datestamp}, the time of its last |
|
109 |
+update, so that a monthly window contains every record updated in that month, not every record first |
|
110 |
+submitted then; duplicates across windows are resolved at parse time with the latest datestamp winning. The |
|
111 |
+\texttt{created} element gives the first submission date, which is the date used throughout this study for |
|
112 |
+preprints. The harvest returned \LinkArxivCsRecords{} distinct records, of which |
|
113 |
+\LinkArxivCreatedTwoZeroOneEightTwoZeroTwoSix{} were first submitted in 2018--2026; the remainder are older |
|
114 |
+e-prints updated during the window. The arXiv metadata are released for reuse under the repository's metadata |
|
115 |
+terms; e-prints themselves are governed by per-paper licences and are downloaded, for the high-priority set |
|
116 |
+only, within those licences and at the repository's rate limits. The use of arXiv as a research dataset, and |
|
117 |
+the caveats attached to its category labels and versioning, are discussed by \citet{clement2019arxiv}. |
|
118 |
+ |
|
119 |
+\subsection{ACL Anthology} |
|
120 |
+ |
|
121 |
+The ACL Anthology is the curated archive of the computational-linguistics community and has itself served as a |
|
122 |
+bibliometric corpus \citep{radev2013acl}. Its BibTeX export with abstracts (\texttt{anthology+abstracts.bib.gz}, |
|
123 |
+46.7~MB, SHA-256 recorded) was downloaded on 2026-11-02 and parsed into a table of 138{,}796 entries, of which |
|
124 |
+\LinkAclRecords{} are conference papers or journal articles and \LinkAclTwoZeroOneEightTwoZeroTwoSix{} fall in |
|
125 |
+2018--2026. The Anthology plays a diagnostic role: because its venue structure is complete and hand-maintained, |
|
126 |
+the share of its entries that the backbone can be matched to is a direct measure of OpenAlex coverage for a |
|
127 |
+subfield that publishes overwhelmingly in conference proceedings. It also supplies abstracts for those entries |
|
128 |
+in which OpenAlex has none. The export is licensed CC~BY~4.0. |
|
129 |
+ |
|
130 |
+\subsection{Crossref, Semantic Scholar and other sources} |
|
131 |
+ |
|
132 |
+Crossref \citep{hendricks2020crossref} is the registration agency behind most DOIs in the corpus and offers |
|
133 |
+open metadata through a REST API with a polite pool. It is not used to build the corpus, whose backbone |
|
134 |
+already carries Crossref-derived metadata through OpenAlex, but for three verification purposes: resolution of |
|
135 |
+every DOI cited in this manuscript, a cross-check of publisher-assigned document types on samples, and a |
|
136 |
+cross-check of citation counts (\texttt{is-referenced-by-count}) on a sample of highly cited works in |
|
137 |
+Part~IX. |
|
138 |
+ |
|
139 |
+The Semantic Scholar Academic Graph \citep{kinney2023s2} was listed in the mandate among the priority sources |
|
140 |
+because of two signals it alone provides, the influential-citation classification and citation intent. At the |
|
141 |
+time of the feasibility audit, anonymous requests to its API returned HTTP~429 with an instruction to apply for |
|
142 |
+a key, and the bulk-dataset endpoint requires a key outright. In keeping with the rule that inaccessible data |
|
143 |
+be recorded rather than circumvented, Semantic Scholar is recorded as unavailable (decision D3) and no analysis |
|
144 |
+in this manuscript uses influential-citation or citation-intent signals; where Part~VIII discusses the |
|
145 |
+strength of citation links, it does so with OpenAlex reference lists and the knowledge-graph extraction of |
|
146 |
+Part~IV, whose limits are stated there. The Microsoft Academic Graph \citep{wang2020mag}, from which OpenAlex |
|
147 |
+inherited much of its historical coverage, was discontinued at the end of 2021 and is not an independent source |
|
148 |
+for the period studied. Kaggle credentials for the arXiv snapshot distributed there were absent and were not |
|
149 |
+needed, OAI-PMH being sufficient. Benchmark repositories and code-hosting platforms enter only in the |
|
150 |
+reproducibility and benchmark analyses scoped in Part~IV and are not part of the bibliographic corpus. |
|
151 |
+ |
|
152 |
+Table~\ref{tab:data-sources} summarises the sources, the access route, the licence and the role of each. |
|
153 |
+ |
|
154 |
+\begin{table}[htbp] |
|
155 |
+\centering\small |
|
156 |
+\caption{Information sources of the WP44 corpus (all accessed 2026-11-02/03).} |
|
157 |
+\label{tab:data-sources} |
|
158 |
+\begin{tabularx}{\textwidth}{lXll} |
|
159 |
+\toprule |
|
160 |
+Source & Access and snapshot & Licence & Role \\ |
|
161 |
+\midrule |
|
162 |
+OpenAlex works snapshot & public S3 bucket, release 2026-10-14, 1{,}898 JSONL files, \LinkSlimTotal{} works & CC0 & backbone: identifiers, dates, types, topics, authorships, references, abstracts, OA status \\ |
|
163 |
+OpenAlex REST API & no key; USD~0.10 per day shared budget; increment 2026-10-01 to 2026-11-02; single lookups & CC0 & post-snapshot increment; reference verification \\ |
|
164 |
+DBLP & XML dump 2026-11-02 22:39~UTC, MD5 verified & ODC-BY~1.0 & computer-science scope; venue streams; author identifiers \\ |
|
165 |
+arXiv & OAI-PMH set \texttt{cs}, 2018-01 to 2026-11, raw pages kept & arXiv metadata terms & preprint layer; first-submission dates; categories \\ |
|
166 |
+ACL Anthology & BibTeX export with abstracts, 2026-11-02 & CC~BY~4.0 & coverage check for NLP venues; abstracts \\ |
|
167 |
+Crossref & REST API, polite pool & open metadata & verification of DOIs, types and citation counts \\ |
|
168 |
+Semantic Scholar & API key required; anonymous calls refused & --- & \emph{unavailable, recorded} \\ |
|
169 |
+\bottomrule |
|
170 |
+\end{tabularx} |
|
171 |
+\end{table} |
|
172 |
+ |
|
173 |
+\section{Identification: what each source contributes} |
|
174 |
+\label{sec:data-identification} |
|
175 |
+ |
|
176 |
+There is no keyword search in this study. A mapping of an entire discipline cannot be defined by a query |
|
177 |
+string without importing the vocabulary of whoever wrote it; it is defined instead by database scope filters |
|
178 |
+that are themselves documented and reproducible, which is the strategy recommended for mapping studies in |
|
179 |
+software engineering and adopted here for computer science as a whole |
|
180 |
+\citep{petersen2008mapping,petersen2015mapping}. The identification stage (S0 in the notation of the research |
|
181 |
+plan) therefore consists of four scope filters, one per source, applied to immutable snapshots whose dates and |
|
182 |
+hashes are recorded in \texttt{data/raw/README.md}. |
|
183 |
+ |
|
184 |
+\subsection{Scope filters} |
|
185 |
+ |
|
186 |
+The OpenAlex filter retains every work with at least one topic, primary or secondary, in field~17 and a |
|
187 |
+publication year in $[2018, 2026]$. The choice of \emph{any} topic rather than the primary topic is deliberate |
|
188 |
+and conservative at this stage: a work whose primary topic lies in, say, statistics or electrical engineering |
|
189 |
+but which carries a secondary computer-science topic is a candidate, and the decision whether it belongs to |
|
190 |
+the core or to the penumbra is deferred to the eligibility stage, where it is made explicit and counted |
|
191 |
+(Section~\ref{sec:data-core}). The filter yields |
|
192 |
+\PrismaIdentifiedOpenalexCsTopicTwoZeroOneEightTwoZeroTwoSixPassOne{} records in the first pass over the |
|
193 |
+snapshot. The DBLP filter retains the publication records of type article, inproceedings, incollection, book, |
|
194 |
+phdthesis and data with a year in $[2018, 2026]$: \PrismaIdentifiedDblpTwoZeroOneEightTwoZeroTwoSix{} records. |
|
195 |
+The arXiv filter retains the records of set \texttt{cs} whose first submission falls in the window: |
|
196 |
+\PrismaIdentifiedArxivCsTwoZeroOneEightTwoZeroTwoSix{} records. The ACL filter retains the conference papers |
|
197 |
+and journal articles of the Anthology with a year in the window: |
|
198 |
+\PrismaIdentifiedAclTwoZeroOneEightTwoZeroTwoSix{} records. The four counts overlap heavily, since most DBLP |
|
199 |
+and ACL records and a majority of arXiv records also exist in OpenAlex; the overlap is resolved by record |
|
200 |
+linkage, not by summation, and no total of identified records is reported as if the sources were disjoint. |
|
201 |
+ |
|
202 |
+\subsection{The OpenAlex topic classifier as a scope instrument} |
|
203 |
+ |
|
204 |
+Because the OpenAlex filter relies on an automated topic classifier, its properties bear on everything |
|
205 |
+downstream. OpenAlex assigns to each work up to three topics from a fixed list of 4{,}516, organised in 252 |
|
206 |
+subfields, 26 fields and four domains; the assignment is made by a model applied to the title, abstract and |
|
207 |
+venue, and the field label of a work is inherited from its topics rather than assigned directly. Two |
|
208 |
+consequences follow. A work can be labelled computer science because one of its topics belongs to field~17 |
|
209 |
+even when its content is only marginally computational, and conversely a work in a computer-science venue can |
|
210 |
+receive no computer-science topic when its abstract is missing or its vocabulary is domain-specific. The first |
|
211 |
+error inflates the candidate set with what will be called the penumbra; the second removes genuine |
|
212 |
+computer-science works from the first-pass candidate set. DBLP is used to correct the second error, which is |
|
213 |
+why the linkage stage has two passes (Section~\ref{sec:data-linkage}). The literature on OpenAlex has so far |
|
214 |
+examined its coverage and metadata completeness rather than the accuracy of its topic labels |
|
215 |
+\citep{alperin2024openalex,delgadoquiros2024completeness}; the present study treats the labels as a scope |
|
216 |
+instrument whose errors are bounded by the DBLP and arXiv memberships and quantified in |
|
217 |
+Section~\ref{sec:data-quality}, not as ground truth. |
|
218 |
+ |
|
219 |
+\subsection{Verification of the scale against the mandate} |
|
220 |
+ |
|
221 |
+The mandate set planning targets of more than one million candidate records and more than one hundred |
|
222 |
+thousand deeply classified records, subject to availability. The feasibility audit established, before any |
|
223 |
+ingestion, that the OpenAlex API alone reported more than six million works with a computer-science primary |
|
224 |
+field in 2018--2026 and that the DBLP dump held more than four million records in the same years; the targets |
|
225 |
+were therefore attainable without recourse to any restricted source. The audit also established what was |
|
226 |
+\emph{not} attainable: a Semantic Scholar key, an OpenAlex key, Kaggle credentials and the AWS command-line |
|
227 |
+tool were all absent, and the ingestion was designed around their absence (HTTPS streaming of the public |
|
228 |
+bucket, basic paging of the public API). The record of this audit is \texttt{reports/PHASE0\_FEASIBILITY.md}. |
|
229 |
+ |
|
230 |
+\section{Record linkage across sources} |
|
231 |
+\label{sec:data-linkage} |
|
232 |
+ |
|
233 |
+The four candidate sets describe overlapping populations with different identifiers. Record linkage (stage S1) |
|
234 |
+establishes, for each DBLP, arXiv and ACL record, the OpenAlex work it describes, so that one node per work |
|
235 |
+can be formed with the union of the metadata. The methods are deterministic and ordered by reliability; the |
|
236 |
+probabilistic framework of \citet{fellegi1969linkage} is not needed because the available keys (DOI, arXiv |
|
237 |
+identifier) are close to exact, and the residual title-based step is restricted to blocks where it is |
|
238 |
+unambiguous. The implementation follows the standard decomposition of data matching into key normalisation, |
|
239 |
+blocking, comparison and classification \citep{christen2012matching}; Part~IV gives the formal statement of the |
|
240 |
+keys and of the precision-estimation design, and this section reports what was done and what it produced. |
|
241 |
+ |
|
242 |
+\subsection{Keys and matching order} |
|
243 |
+ |
|
244 |
+All keys are normalised before comparison. DOIs are lower-cased. arXiv identifiers are lower-cased and |
|
245 |
+stripped of their version suffix (\texttt{v2}, \texttt{v3}, \ldots), so that all versions of an e-print map to |
|
246 |
+one identifier. Titles are reduced to a normalised string by lower-casing and deleting every character that is |
|
247 |
+not a letter or digit; the normalised title is used only when it has at least 25 characters, is unique within |
|
248 |
+its source, and is unique within OpenAlex, which is the blocking rule that keeps the title step from |
|
249 |
+producing spurious links between generic titles. |
|
250 |
+ |
|
251 |
+For DBLP, the order is: (i) DOI equality, (ii) arXiv identifier equality, restricted to records not yet linked |
|
252 |
+on either side, (iii) normalised title equality with a year difference of at most one, restricted to records |
|
253 |
+not yet linked on either side. The DOI step linked \LinkLinkDblpOaDoi{} records and the title step |
|
254 |
+\LinkLinkDblpOaTitleYear{}; the arXiv step linked none, because the extraction of arXiv URLs from the DBLP |
|
255 |
+\texttt{ee} fields returned no candidate (\LinkDblpWithArxiv{} records with an extracted identifier). The most |
|
256 |
+plausible reason is that DBLP now records the arXiv version of its CoRR entries as a DataCite DOI of the form |
|
257 |
+\texttt{10.48550/arXiv.*}, which the DOI step already handles; the step is kept in the pipeline because other |
|
258 |
+dumps may differ. In total \LinkDblpLinkedDistinct{} of the \LinkDblpTwoZeroOneEightTwoZeroTwoSix{} DBLP |
|
259 |
+records in the window were linked to an OpenAlex work after the first pass, leaving \LinkDblpUnlinked{} |
|
260 |
+unlinked. The composition of the unlinked set is informative: \LinkDblpUnlinkedByTypeArticle{} journal |
|
261 |
+articles, \LinkDblpUnlinkedByTypeInproceedings{} conference papers, \LinkDblpUnlinkedByTypePhdthesis{} |
|
262 |
+doctoral theses, \LinkDblpUnlinkedByTypeData{} data records, \LinkDblpUnlinkedByTypeIncollection{} chapters |
|
263 |
+and \LinkDblpUnlinkedByTypeBook{} books. Of these, \LinkDblpUnlinkedWithDoiInSlim{} carry a DOI that |
|
264 |
+\emph{does} exist in the slim table of all OpenAlex works, which means the work is in OpenAlex but was not |
|
265 |
+caught by the computer-science topic filter; this is the second error of the topic classifier described above |
|
266 |
+and the reason for the second pass. |
|
267 |
+ |
|
268 |
+For arXiv, the order is: (i) arXiv identifier equality against the identifier OpenAlex records for the work, |
|
269 |
+(ii) DOI equality for e-prints that carry a journal DOI, (iii) normalised title equality with a year |
|
270 |
+difference of at most two, the wider tolerance reflecting the typical lag between a preprint and its published |
|
271 |
+version \citep{lin2020preprints}. The steps linked \LinkLinkArxivOaArxivId{}, \LinkLinkArxivOaDoi{} and |
|
272 |
+\LinkLinkArxivOaTitleYear{} records respectively, for \LinkArxivLinkedDistinct{} distinct e-prints linked. |
|
273 |
+For the ACL Anthology, the order is: (i) DOI equality, (ii) equality between the Anthology identifier and the |
|
274 |
+identifier embedded in an \texttt{aclanthology.org} landing-page URL among the work's OpenAlex locations, |
|
275 |
+(iii) normalised title equality with a year difference of at most one. The steps linked |
|
276 |
+\LinkLinkAclOaDoi{} records by DOI and \LinkLinkAclOaTitleYear{} by title, with the URL step contributing the |
|
277 |
+remainder, for \LinkAclLinkedDistinctTwoZeroOneEightTwoZeroTwoSix{} distinct 2018--2026 entries linked out of |
|
278 |
+\LinkAclTwoZeroOneEightTwoZeroTwoSix{}; the residual is examined in Section~\ref{sec:data-quality} as a |
|
279 |
+measure of OpenAlex coverage of conference-heavy subfields. |
|
280 |
+ |
|
281 |
+\subsection{The second snapshot pass} |
|
282 |
+ |
|
283 |
+A DBLP record whose DOI resolves to an OpenAlex work outside the topic filter is, by the scope rule, a |
|
284 |
+computer-science work that the first pass did not load. The same situation arises for arXiv e-prints whose |
|
285 |
+journal DOI exists in OpenAlex without a computer-science topic. The linkage script therefore writes the list |
|
286 |
+of OpenAlex identifiers that are needed but not loaded: \LinkNeededOaIdsSecondPassDblpDoi{} identifiers from |
|
287 |
+DBLP DOIs and \LinkNeededOaIdsSecondPassArxivDoi{} from arXiv DOIs. A second pass over the works snapshot, |
|
288 |
+restricted to this identifier list, retrieves the full records of these works; they are normalised into the |
|
289 |
+same Parquet tables with a \texttt{\_p2} suffix, the DuckDB views are rebuilt over the union of both passes, |
|
290 |
+and linkage is re-run so that the DBLP-linked set gains the works that the topic classifier had missed. The |
|
291 |
+second pass is what makes the DBLP membership rule of Section~\ref{sec:data-core} operational: without it, |
|
292 |
+``DBLP-indexed'' would silently mean ``DBLP-indexed and labelled computer science by OpenAlex'', and the DBLP |
|
293 |
+correction would be void precisely where it matters. DBLP records with no OpenAlex counterpart after both |
|
294 |
+passes (\PrismaLinkedDblpOnlyNoOpenalexRecord{} records before the second pass) are kept in a separate table |
|
295 |
+with their year and type and are reported as such; they enter the volume counts of Part~IX only in the |
|
296 |
+sensitivity analysis that adds DBLP-only records, because they lack the abstracts, references and affiliations |
|
297 |
+on which every other indicator depends. Most of them are journal articles and conference papers with a DOI |
|
298 |
+that OpenAlex does not hold at all, together with doctoral theses, which DBLP indexes from university |
|
299 |
+repositories that OpenAlex covers unevenly. |
|
300 |
+ |
|
301 |
+\subsection{Precision of the linkage} |
|
302 |
+ |
|
303 |
+Exact-key links are correct whenever the key is correct in both sources; the known failure modes are DOIs |
|
304 |
+reassigned by publishers between versions, DOIs registered for a proceedings volume rather than a paper, and |
|
305 |
+e-prints whose OpenAlex record points to a different version. Title-based links can fail on near-identical |
|
306 |
+titles of distinct works (extended abstracts and full papers, workshop and conference versions). The protocol |
|
307 |
+pre-specifies the estimation of linkage precision on a sample of 500 DBLP--OpenAlex pairs stratified by method, |
|
308 |
+with automatic agreement checks (normalised-title similarity, year difference, first-author surname) and a |
|
309 |
+200-pair subsample reserved for the principal investigator (checkpoint H-1). The sampling script draws 250 DOI |
|
310 |
+links, 200 title links and 50 arXiv links with a fixed seed; since the arXiv step produced no links in this |
|
311 |
+dump, the realised sample has 450 pairs, and the precision estimate for the arXiv step is undefined rather |
|
312 |
+than reported as perfect. At the time of writing the sampling script exists but the sample has not been drawn and the |
|
313 |
+human checkpoint is unsigned; the automatic agreement rates and the human verdicts will be reported in Part~IX |
|
314 |
+and Appendix~B, and every conclusion that depends on the title-based links is labelled as pending human review |
|
315 |
+until H-1 is signed. |
|
316 |
+ |