OpenAlex works without an account for casual use like this, and
doesn’t need a personal email or API key for a workshop-scale
query.
Deciding whether a patron’s request is an author, an organization
with its own entry, or a department with no entry of its own is a
reference-interview skill, not only an API choice.
API responses often include list-columns.
tidyr::unnest(..., names_sep = "_") flattens them while
avoiding name collisions with the outer table.
Unnesting a list-column multiplies rows, one per nested value, so
totals should come from the original one-row-per-work table, not the
unnested one.
OpenAlex’s current subject field is topics, not the
older, unmaintained concepts field.
A verified ORCID confirms you have the right person, but not that
OpenAlex’s own record for them is clean. Check actual works before
trusting a count.
The same ggplot2 and reporting skills from earlier
episodes transfer directly to new, API-sourced data, and any report
should say plainly what it can’t tell you.