CASRAI Dictionary

Tag: researcher profile

  • ORCID for researchers: connecting your identifier to your contributions

    Most researchers now have an ORCID iD, often created in a hurry because a journal or funder asked for one. Far fewer have a record that actually does the work an identifier is meant to do. An ORCID iD that sits empty, or that you copy facts into by hand, delivers almost none of its value. The point of the identifier is connection — to your publications, your grants, your affiliations, and the wider identifier ecosystem — and that is what this guide is about. The foundational explainer lives at persistent identifiers for authors, and this article is the practical companion.

    What an ORCID iD actually solves

    An ORCID iD is a persistent, unique identifier for an individual researcher — a sixteen-digit number, expressed as an HTTPS URI, that stays with you across name changes, institution moves, and career stages. The problem it solves is name disambiguation: in a literature full of common surnames, initial variations, and transliterations, a string name cannot reliably tell two researchers apart, and cannot reliably tie one researcher’s scattered outputs together. The iD does both. It distinguishes you from every other researcher who shares your name, and it gathers your contributions under one unambiguous, machine-readable identity.

    This is why funders and publishers increasingly require it. An ORCID iD on a submission or grant application means the work, the award, and the person can be linked without guesswork — the difference between a name a human must interpret and an identifier a system can resolve.

    Step 1: register and complete the core of your record

    Registration is free and takes minutes at orcid.org. The valuable part is what comes next: populating the record so it represents you. Add your employment and education affiliations, ideally selected from ORCID’s organisation lookup so they carry an organisation identifier rather than a free-typed string. Where the lookup is backed by ROR — the Research Organization Registry — your affiliation is anchored to a persistent organisation identifier, which is what lets systems reliably connect you to your institution. (For the organisation side of the ecosystem, see what is ROR.) Add alternative name forms and a short biography so that the record disambiguates you even where systems still rely on names.

    Step 2: let trusted organisations write to your record

    This is the step that turns a static profile into a living one, and it is the step most researchers skip. ORCID has a permissions model: you can grant a trusted organisation — a publisher, a funder, a repository, your institution’s research-information system — permission to read from and write to your record. Once granted, these systems can add works, grants, and affiliations for you, automatically and with provenance attached.

    • Authorise Crossref and DataCite auto-update so that when you publish an article or deposit a dataset with your iD, the output appears on your record without manual entry.
    • Grant your funders permission so that awards are written to your record from the authoritative source.
    • Connect your institution’s system so affiliations and outputs stay synchronised.

    The principle is enter-once, reuse-everywhere. A contribution asserted with your iD by a trusted source is more credible than one you typed yourself, because the assertion carries the provenance of the organisation that made it. The record stops being a CV you maintain and becomes a verified, auto-updating account of your work.

    The single highest-value action most researchers can take with ORCID is to turn on auto-update permissions for Crossref and DataCite. After that, publishing with your iD maintains your record for you.

    Step 3: use your iD everywhere it is asked for — and where it is not

    An identifier only disambiguates if it is attached at the moment of contribution. Enter your ORCID iD on every manuscript submission, every grant application, every dataset deposit, and every peer-review record. Each time you do, you create a verified link between the work and your identity that flows into the connected systems. Conversely, an output published without your iD is one your record cannot automatically claim, and one that name-based systems may attach to the wrong person.

    Step 4: connect ORCID to the rest of the identifier graph

    ORCID is one node in a connected ecosystem, and its value compounds when it is linked to the others. Your iD identifies you; ROR identifies your organisations; a DOI identifies your outputs; a grant identifier identifies your funding; and a project identifier such as RAID identifies the activity that ties them together. When your outputs carry your ORCID iD and your institution’s ROR ID, and your awards carry grant identifiers linked to your iD, the graph assembles itself: a query can move from you to your works to your funders to your institution without a single hand-typed reconciliation.

    This graph is also where contribution metadata lives. When a publisher records a CRediT statement and writes the relevant roles to your ORCID record alongside the publication, your iD begins to carry not just what you have published but what you did on each output — the richer, contribution-aware picture that responsible assessment depends on.

    A note on what ORCID will and will not do

    ORCID disambiguates and connects; it does not, by itself, validate the quality of a contribution or decide authorship. An auto-updated record is only as good as the assertions trusted sources write to it, and you remain responsible for reviewing your record and correcting errors. Keep the public-visibility settings deliberate, review incoming auto-updates periodically, and treat the record as something you curate, not something that runs entirely without you.

    Where shared vocabulary fits

    The identifier ecosystem works only when systems agree on what each identifier means and how they connect — what a “trusted organisation” permission grants, how an affiliation is asserted, how an output links to a person. A shared, federated vocabulary that defines these relationships and points back to ORCID and ROR for the authoritative infrastructure is what lets the graph hold together across systems. Supplying that definitional layer is the role the CASRAI dictionary is designed to play; the relevant terms sit in the persistent-identifiers domain.

    Related reading

  • Keeping your ORCID record current: a maintenance guide for researchers

    Registering for an ORCID iD takes about two minutes. Keeping the record behind it accurate is where most researchers fall down, and an out-of-date ORCID record quietly undermines the very thing the identifier is meant to do. The good news is that, with a few settings configured once, ORCID will keep much of your record current for you — the work is far more about permissions than about manual data entry. This guide explains how. For the background on what the identifier is and why it matters, the persistent-identifiers guidance for authors and the explainer on what an ORCID iD is are the place to start; this article assumes you already have one and want to keep it healthy.

    The two kinds of data on an ORCID record

    The single most useful thing to understand about ORCID is that not all the information on a record is equal. ORCID distinguishes between data that you have typed in yourself and data that a trusted organisation has asserted about you.

    • Self-asserted data is anything you add by hand — an affiliation you typed, a paper you entered manually. It is useful, but a reader cannot tell whether it is verified.
    • Validated assertions are added by a trusted organisation through ORCID’s API — your university confirming an employment, a publisher confirming you authored a paper, a funder confirming you hold a grant. These carry the source of the assertion, so anyone reading the record can see that the affiliation came from the institution itself, not just from your own claim.

    A record full of validated assertions is dramatically more trustworthy — and more useful to funders and hiring committees — than one you have populated entirely by hand. The goal of good ORCID maintenance is therefore to let trusted organisations do as much of the asserting as possible.

    Turn on auto-update

    The highest-value setting is auto-update. When you connect your ORCID iD to Crossref and DataCite — a one-time authorisation — new works that are deposited with your ORCID iD attached are added to your record automatically. In practice this means that when you publish a paper and the publisher includes your ORCID iD in the Crossref deposit, the paper appears on your ORCID record without you doing anything, and it appears as a validated assertion sourced from the registration agency.

    The condition is simple but easy to miss: the publisher has to actually collect and deposit your ORCID iD. That is why you should always supply your ORCID iD during submission, and ideally sign in with it rather than typing it, so that the iD is authenticated. An authenticated iD attached at submission is what makes the whole auto-update chain work. Connect once, supply your iD every time, and your publication list largely maintains itself.

    Manage your trusted organisations and trusted individuals

    Auto-update is one instance of a broader mechanism: trusted parties. ORCID lets you grant two kinds of trust:

    • Trusted organisations — institutions, funders, publishers, and systems you authorise to read from or write to your record through the API. Your university’s research-information system, for example, can be a trusted organisation that adds your validated employment affiliation and pushes your institutional outputs onto your record.
    • Trusted individuals — a person, such as a research administrator or an assistant, whom you authorise to manage your record on your behalf. This is useful for senior researchers who would rather delegate the upkeep.

    Both are managed under the Trusted parties section of your account settings, and both are fully revocable. Granting access does not hand over your password; it grants a scoped, auditable permission that you can withdraw at any time. Reviewing this list once or twice a year — confirming the organisations you expect are there, and revoking any you no longer deal with — is the core maintenance habit.

    Set your visibility deliberately

    Every item on an ORCID record has a visibility setting: everyone, trusted parties only, or only me. The default for new items can be configured in your account. For the record to be useful to the systems that consume it — funders checking your outputs, journals verifying your identity, your CRIS pulling your profile — the key items generally need to be public. A common and self-defeating mistake is to register an iD, set everything to private, and then wonder why the identifier seems to do nothing. As a rule, make your name, affiliations, and outputs public, and reserve restricted visibility for things you genuinely want kept back.

    A short maintenance routine

    1. Connect to Crossref and DataCite auto-update once. This is the single highest-leverage action; it keeps your works current automatically.
    2. Always supply your authenticated ORCID iD at submission — for papers, datasets, software, and grant applications — so that each output and award can be asserted onto your record.
    3. Authorise your institution as a trusted organisation so that your employment and institutional outputs arrive as validated assertions.
    4. Review your trusted parties annually and revoke any you no longer use.
    5. Add the things no one else will assert — education, professional memberships, peer-review and editorial service, older works that predate ORCID — by hand, since these often have no organisation to assert them for you.
    6. Check your visibility settings so that the items you want discoverable are actually public.

    Why a current record pays off

    Beyond convenience, an accurate ORCID record increasingly does real work on your behalf. Funders draw on it for applications and reporting; narrative-CV and biosketch tools pull from it; institutional systems reconcile your outputs against it. A record rich in validated assertions lets you make precise, checkable claims about your contribution history — including, where publishers deposit them, your CRediT roles per paper, so that “I led the analysis on these studies” becomes a verifiable statement rather than an assertion on a CV. The effort is front-loaded into a handful of one-time settings; the payoff compounds across every later application and assessment.

    Where shared vocabulary fits

    “Auto-update”, “trusted party”, “validated assertion”, “source”, and “self-asserted” are ORCID-specific terms that are easy to muddle, and confusion about them is exactly why so many records go stale. A shared, federated vocabulary that defines these terms precisely is what lets guidance from one institution be understood at another. Supplying that definitional layer is part of the role the CASRAI dictionary is designed to play.

    Related reading

  • What a CRIS does: the research-information backbone explained

    Most universities run a system that quietly underpins a great deal of their research administration, and most researchers could not name it. It is the Current Research Information System (CRIS) — the institutional backbone that ties together who the researchers are, what projects they run, who funds them, and what they produce. This article gives a plain-language account of what a CRIS does, why it matters, and why it depends so heavily on shared vocabulary. It draws on the research-information systems domain.

    CRIS and RIM: the system and the function

    Two terms travel together and are easily confused. A CRIS is the software system. Research Information Management (RIM) is the broader discipline and practice of managing research information — the function that the CRIS supports. RIM is what a research office does; the CRIS is the tool it uses to do it. Both terms appear because the same activity is described from two angles: the operational system and the professional practice. Familiar CRIS products include Pure, Symplectic Elements, Converis, Worktribe, and the open-source VIVO and DSpace-CRIS.

    What a CRIS actually holds

    A CRIS is, at heart, a set of connected records about a handful of entity types and the relationships between them. The core entities are people, organisational units, projects, funding, and outputs. The value is in the connections: this researcher, in this department, leads this project, funded by this award, which produced these publications and datasets. Each entity is a record; the CRIS is the graph that joins them.

    The researcher profile is the entity most people encounter. It aggregates a person’s affiliations, outputs, projects, and activities into a single record — the thing that often surfaces as a public staff page. Behind it sits an organisational hierarchy: the structured representation of departments, schools, institutes, and centres, so that the system can roll outputs and funding up to any level of the institution. The quality of that hierarchy determines whether “how much did the School of Engineering publish last year?” is a one-click query or a week of manual work.

    The core job: getting data in

    A CRIS is only as useful as the data in it, and the central operational challenge is keeping that data current without burying researchers in data entry. Two mechanisms do most of the work. A publication harvest automatically imports publication metadata from external sources — Crossref, Scopus, Web of Science, PubMed, ORCID — so that a researcher’s output list populates itself rather than being typed in. A funder ingest imports funding and award metadata, so that grants appear against the right people and projects.

    Neither mechanism is reliable without identifiers. A publication harvest that matches on author name alone will mis-assign work by every researcher who shares a surname; matching on ORCID iD resolves the person unambiguously. A funder ingest that matches on institution name will fragment one university across a dozen spelling variants; matching on ROR ID collapses them to one. This is why the maturation of the persistent-identifier ecosystem has done more for CRIS data quality than any feature in the software itself.

    Disambiguation, enrichment, validation

    Three less-visible activities determine whether a CRIS is trusted. Disambiguation is the process of resolving ambiguous identifications — two authors with the same name, two spellings of one organisation — to canonical entities. Enriched metadata is metadata improved with information from external sources: adding Crossref Funder Registry IDs to funding records, adding ROR IDs to affiliations, adding DOIs to outputs that arrived without them. A validation rule is a check applied during ingest to enforce data quality — rejecting a publication record with no identifier, flagging an award whose dates fall outside its project. Together these turn a heap of imported records into a research-information asset an institution can report from with confidence.

    What the CRIS is for

    The reason institutions invest in a CRIS is that the same research-information facts are needed, repeatedly, for many different purposes. Annual reporting, research assessment exercises, open-access compliance monitoring, public staff and project pages, internal resource allocation, and responses to funder audits all draw on the same underlying entities. Without a CRIS, each of these is a separate data-gathering exercise; with one, they are views over a single maintained graph. The CRIS is the institution’s single source of truth for research information, and its value is exactly proportional to how trustworthy that single source is.

    This is also why a CRIS connects outward. It is not an island: it harvests from Crossref and ORCID, it can push validated publications to a repository, it feeds open-access compliance dashboards, and increasingly it exchanges project information using shared models. A modern CRIS is a node in an institutional and sectoral information fabric, not a closed database.

    Why shared vocabulary is the precondition

    Here is the catch that connects the CRIS to CASRAI’s mission. Every CRIS implementation that invents its own field names — its own way of recording an ethics status, an output type, a project phase, a funding category — creates a system that cannot exchange data cleanly with any other. The harvests work because Crossref, ORCID, and ROR provide shared identifiers and shared metadata. The internal records often do not interoperate, because each institution structured them locally. A controlled, shared vocabulary for the entities and attributes a CRIS holds is what would let research information move between institutions as cleanly as it now moves in from the identifier providers. Supplying that definitional layer is the convening role the CASRAI dictionary exists to play.

    What to do now

    For institutions running a CRIS: invest in identifiers first — ORCID and ROR adoption do more for data quality than any feature. Treat disambiguation, enrichment, and validation as ongoing operations, not one-off projects. For those procuring or integrating systems: use vendor-neutral, shared vocabulary to specify what you need, so the conversation is about your requirements rather than one product’s field names.

    Related reading