Where you set it
Open your study’s Record stage. In the Findability panel you’ll find two fields:
Your affiliation’s identifier — its ROR id — is set once on your profile, not per study. See Researcher profiles; it then rides along on every record you author.
Both Findability fields save the moment you change them — there’s no separate save step.
Funders
Start typing a funder’s name and pick it from the list. Each match comes straight from the Crossref Funder Registry and carries the funder’s DOI — the canonical identifier for that body. Your record then links to it, and the metadata we emit tags the funder with its@id so a machine reads the same identifier a person does.
No match in the registry? Keep typing and choose Use ”…” to add the funder as plain text. It appears on your record by name; it simply won’t carry a registry id.
Where these identifiers show up
Once set, your PIDs appear in two places, kept in step by construction:On the record, for people
The public study record shows the language and links each funder to its Funder Registry page. Your affiliation on the byline links to its ROR page.
In the metadata, for machines
The record embeds schema.org JSON-LD carrying
inLanguage, each funder with its @id, and the author’s affiliation with its ROR @id — what Google Dataset Search and other indexers read.Resource type
The record also derives a DataCite resource type from its state —Dataset when you’ve published a data table, StudyRegistration for a preregistered study, otherwise Text. It’s emitted in the metadata so indexers classify the record correctly. My Research Lab does not mint a separate DataCite DOI — your OSF registration DOI stays the one canonical identifier for the study.