From an ORCID record to a LaTeX publication list

A worked example on ORCID’s test record

latexci.com · API read on 2026-10-18

Abstract

ORCID keeps the list of your works, and its public API returns it as JSON. That list is a good start for the publications section of an academic CV, but it is not a finished bibliography: the summaries carry no co-authors, the venue is often empty, and the same work can arrive from several sources. We read the record of Josiah Carberry (0000-0002-1825-0097), the fictitious researcher used in ORCID’s own documentation, and turned it into a LaTeX list two ways: plain LaTeX grouped by year, and biblatex fed with the BibTeX stored in ORCID.

1What the public API returns

Two read calls are enough (Figure 1). The first returns every work as a summary, grouped when several sources describe the same work. The second, given up to 100 put-codes, returns the full works. Both answered our requests without any token.

HTTP

GET https://pub.orcid.org/v3.0/0000-0002-1825-0097/works
Accept: application/json

GET https://pub.orcid.org/v3.0/0000-0002-1825-0097/works/9543020,4562455,4562454
Accept: application/json

Figure 1. The list of works, then the full works for three put-codes.

For this record the first call returned 6 groups holding 7 summaries: 1 work came from two sources. Table 1 lists the first summary of each group, the one a simple import keeps.

Year	Title	journal-title	Source
2012	A Methodology for the Emulation of Architecture	empty	Crossref Metadata Search
2012	The Memory Bus Considered Harmful	empty	Josiah Carberry
2011	The Impact of Interactive Epistemologies on Cryptography	empty	Josiah Carberry
2008	Developing Thin Clients Using Amphibious Epistemologies	empty	Josiah Carberry
2008	Toward a Unified Theory of High-Energy Metaphysics: Silly String Theory	empty	Josiah Carberry
1987	Bulk and surface plasmons in artificially structured materials	IEEE Transactions on Plasma Science	Scopus - Elsevier

Table 1. The works of 0000-0002-1825-0097, as summaries. 6 of 6 have a DOI; 5 have no journal title.

One summary (fields a CV needs)

{
  "put-code": 9543020,
  "title": {
    "title": {
      "value": "A Methodology for the Emulation of Architecture"
    },
    "subtitle": {
      "value": "Journal of Psychoceramics"
    },
    "translated-title": null
  },
  "type": "journal-article",
  "publication-date": {
    "year": {
      "value": "2012"
    }
  },
  "journal-title": null,
  "external-ids": {
    "external-id": [
      {
        "external-id-type": "issn",
        "external-id-value": "0264-3561"
      },
      {
        "external-id-type": "doi",
        "external-id-value": "10.5555/12345680"
      }
    ]
  }
}

Fields only in the full work

short-description, citation, contributors, language-code, country

Figure 2. A work summary, cut to the useful fields, and the fields that only the full work has. Authors are in contributors.

2Limits to know before you import

No co-authors in summaries. The summary has no contributors field at all. The full works do, but on this record 1 of 6 listed any contributor. Expect to type author lists yourself.
Venue often missing. 5 of 6 summaries had an empty journal-title, although the journal appears in the full work’s BibTeX. In the summary of Figure 2 the journal name sits in title.subtitle instead: “Journal of Psychoceramics”.
One work, several sources. A group can hold the same work from a publisher, a database and the researcher. Keep one per group, or you list the paper twice.
Stored BibTeX is a snapshot. 6 of 6 full works carried a citation in BibTeX. For DOI 10.5555/12345679, ORCID’s copy says 2008; the DOI resolver, asked for BibTeX the same day, said 2012 with the title “Developing Thin Clients Using Amphibious Epistemologies - edited title” (Figure 3).
Citation keys clash. The stored entries reuse keys: Carberry_2008, Carberry_2012 appear twice. Re-key before you feed them to BibTeX or biber.

Stored in ORCID

@article{Carberry_2008,
  title={Developing Thin Clients Using Amphibious Epistemologies},
  volume={5},
  url={http://dx.doi.org/10.5555/12345679},
  DOI={10.5555/12345679},
  number={11},
  journal={Journal of Psychoceramics},
  publisher={CrossRef test user},
  author={Carberry, Josiah},
  year={2008},
  month={Feb},
  pages={1-3}}

From doi.org, Accept: application/x-bibtex

@article{Carberry_2012,
  title={Developing Thin Clients Using Amphibious Epistemologies - edited title},
  volume={1},
  ISSN={0264-3561},
  url={http://dx.doi.org/10.5555/12345679},
  DOI={10.5555/12345679},
  number={1},
  journal={Journal of Psychoceramics},
  publisher={Test accounts},
  author={Carberry, Josiah},
  year={2012},
  month=Jan }

Figure 3. The same DOI, two answers. The DOI metadata was edited after ORCID stored its copy.

When you need current metadata, resolve the DOIs again: the DOI to BibTeX tool does it for a list of DOIs.

3Plain LaTeX, grouped by year

The simplest list needs no bibliography software. Sort the summaries newest first, open one enumerate per year and link each DOI (Figure 4). It uses only what the summaries hold, so the authors are missing until you add them.

Publication list grouped by year, compiled from the ORCID summaries — **Figure 4.** The list generated from the summaries of Table 1, compiled. The preamble adds `enumitem`, `xurl` and `hyperref`.

To group by type instead, use the type field: ORCID calls journal papers journal-article, conference papers conference-paper and preprints preprint. On this record every work is journal-article, so a grouping by type gives a single group, which is why Figure 4 groups by year.

4The biblatex route

If you already manage references with biblatex, take the BibTeX that ORCID stores with each full work, give each entry a unique key (here orcid plus the put-code) and print the list with sorting=ydnt, newest first (Figure 5). Splitting by type is one \printbibliography[type=...] per section.

biblatex publication list built from the BibTeX stored in ORCID — **Figure 5.** biblatex with biber on the stored BibTeX, compiled. The 1987 entry spells the name differently from the five others.

Figure 5 also shows the cost of importing without review: five entries name the author “Carberry, Josiah”, the sixth “Carberry, J.S.”. To biblatex these are two different people, which breaks anything that matches names, such as setting your own name in bold. Normalise your name across entries before you print.

5With the latexci CV builder

The CV builder does the first route for you. Type your ORCID iD and press the import button: only the iD is sent, through a latexci endpoint, to pub.orcid.org. For up to 100 works it keeps the first summary of each group and fills the title, journal, year, DOI and type (journal article, conference paper or preprint), newest first, and skips titles already in your list. Co-authors are left for you to add, for the reason in Section 2; the builder then sets your own name in bold in every author list.

Import from ORCID in the builder Academic CV template

Applying outside academia too? Read whether a LaTeX resume is ATS-friendly, or, in French, Modèle de CV LaTeX gratuit.