A researcher’s whole publication record

Rather than measuring one tool, you can expand a researcher’s ORCID iD into one Project per work in their public record — every paper they’ve published, each as its own bare-paper Project. An ORCID iD identifies a person, never a piece of work, so it isn’t an Identity itself; it’s an input that expands into a set of them (see ADR-0006).

boast init --orcid 0000-0002-1825-0097 -o manifest.toml

(0000-0002-1825-0097 is ORCID’s own public sandbox/demo account — Josiah Carberry, a fictional professor ORCID maintains specifically for testing against the real API — used here instead of a real researcher’s iD.)

This performs a real network fetch against the ORCID public API (unlike the rest of init, which only writes a file from what you already gave it) and writes one [[project]] entry per work that has a DOI or PMID. Works with neither are skipped — boast has no Provider that can measure them — and a summary of how many were found, kept, and skipped is printed to stderr:

 WARN orcid:0000-0002-1825-0097: 6 works in record; 6 have a DOI/PMID and will be written to manifest.toml, 0 were skipped (no DOI or PMID — not measurable).
 WARN running `boast about` over 6 works ≈ 36 requests across 6 Providers
Manifest written to manifest.toml

manifest.toml (header comment plus the first two of six [[project]] entries):

# Generated by `boast init --orcid 0000-0002-1825-0097` on 2026-08-03 — 6 works.
# 6 written below; 0 skipped (no DOI/PMID).
# Re-run with --include-unidentified to list the skipped works for completion.
# Each remaining work costs ~6 API requests when you run `boast about`.
[[project]]
identities = ["doi:10.5555/12345680"]

[[project]]
identities = ["doi:10.5555/666655554444"]
...

--orcid accepts a bare iD, an orcid:-prefixed one, or a full orcid.org URL, and is repeatable if you want one Manifest covering several researchers:

boast init --orcid 0000-0002-1825-0097 --orcid 0000-0001-2345-6789 -o manifest.toml

It’s exclusive with every other identity source (positionals, --repo, --package, --from-file) — an ORCID expansion has no defensible answer to “which of these works does that repo belong to?”, so mixing them is rejected rather than guessed at.

Works without a DOI or PMID

Most ORCID records carry works boast can’t measure (books, datasets, talks — anything without a DOI or PMID). By default these are silently dropped. Pass --include-unidentified to list them instead, as commented-out [[project]] blocks you can fill in by hand if one of them does have an identifier ORCID just didn’t capture:

boast init --orcid 0000-0002-1825-0097 --include-unidentified -o manifest.toml

The Carberry demo record above happens to have zero unidentified works, so there’s no real run to show for it here — but on a record that has some, each appears (title, year, and work type, straight from the ORCID record) as a commented-out block instead of being silently dropped:

# ─── 1 work with no DOI or PMID in your ORCID record ───
# These can't be measured as-is. If you know the DOI, uncomment the block and
# fill it in — and consider adding it to your ORCID record so it's there next time.
#
# "Some Conference Talk" (2019, lecture-speech)
# [[project]]
# identities = ["doi:"]

Running it

Once you have the Manifest:

boast about manifest.toml

writes one Snapshot per Project. Because that’s usually a lot of Projects for one researcher, the CI automation guide — built for a single Project Manifest — doesn’t directly cover this case; see its “Scope” section for the reason and the workaround.