If you are searching for how to translate a RAiD, how to translate a Research Activity Identifier, how to preserve research-project identity across languages, or how to translate project metadata without breaking persistent links, the central rule is that the identifier is not prose. Translate the project title, description, participant roles and explanatory metadata; preserve the RAiD exactly as the registry supplies it.
This matters in research administration, grant reporting, universities, funders, repositories, research infrastructure, project portfolios, persistent-identifier systems, open-science platforms and scholarly metadata. A multilingual record can read perfectly and still become wrong if a RAiD is altered, if a grant is confused with the research activity it supports, if a project title is translated into a new pseudo-identity, or if people, organizations, inputs and outputs are detached from the activity they belong to.
This guide explains how to translate around the Research Activity Identifier governed by ISO 23527:2022. RAiD is a persistent identifier and global registry for research projects and activities, operated by the Australian Research Data Commons as Registration Authority. The goal is to let project language change while the project itself remains traceable across systems, time, institutions and research outputs.
1. RAiD identifies a research activity
RAiD is designed to identify a research project or activity as a persistent entity rather than merely storing a title string. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
2. ISO 23527:2022 governs the identifier
RAiD is governed by ISO 23527:2022, so production guidance should use the current standard context instead of treating it as a local project code. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
3. ARDC is the Registration Authority
The Australian Research Data Commons operates RAiD in its role as Registration Authority and maintains the service with registration agencies. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
4. A RAiD is persistent
Project titles, personnel and organizations can change over time, while the RAiD remains the persistent point that holds the activity together. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
5. The project title is not the identifier
A translated title can be natural for a target audience without changing the RAiD that identifies the activity. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
6. A project is not the same as a grant
A grant is funding received; RAiD identifies the research activity itself, which may involve one or several grants. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
7. Funding IDs belong in related metadata
Grant identifiers should remain separate and be linked to the RAiD rather than substituted for it. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
8. People can join and leave a project
Research personnel can change through the lifecycle, so translated records should keep people as time-aware relationships to one stable activity. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
9. Organizations can change during the lifecycle
A project can move institution or gain partners while the research activity remains the same persistent object. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
10. Inputs and outputs can be linked to the activity
RAiD metadata can bring together datasets, instruments, grants, publications and other persistent identifiers associated with the project. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
11. RAiD is a PID container
The identifier helps connect other persistent identifiers around a project rather than replacing ORCID, ROR, DOI or funder IDs. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
12. RAiD is not ORCID
ORCID identifies researchers; RAiD identifies projects or activities. The same person can participate in many RAiDs. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
13. RAiD is not ROR
ROR identifies research organizations, while RAiD identifies the project that those organizations participate in. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
14. RAiD is not DOI
DOIs identify registered objects such as papers, datasets or other outputs, while RAiD identifies the activity that can produce or use them. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
15. RAiD can resolve to a metadata landing page
A RAiD can be resolved through the registry to a standardized metadata record, making the identifier useful across languages and systems. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
16. The resolvable URL should be protected
If the identifier is represented as a URL, translation should not change domain, path or identifier characters. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
17. Embargoed RAiDs can exist
Some RAiD metadata can be temporarily embargoed, so a failure to see public detail immediately does not imply the identifier is invalid. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
18. Sensitive information should not be stored casually
The registry is not intended as a place for permanently sensitive or confidential information, which matters when translating project descriptions. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
19. Project names can have multilingual labels
A research activity may need a translated public title while retaining one RAiD for reconciliation. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
20. Translated descriptions should not create new activities
Creating a French or Japanese description does not by itself justify minting a second RAiD. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
21. Project scope can evolve
Research plans can change between proposal and delivery; RAiD is designed to preserve continuity as project metadata evolves. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
22. Planned and delivered activity can differ
Translation should preserve whether a statement describes planned work, current work or completed outputs instead of flattening them into one tense. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
23. Temporal metadata matters
Start dates, end dates and changing relationships help explain project history and should remain attached to the same RAiD. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
24. Participant roles are not interchangeable
Principal investigator, contributor, data manager and partner roles can have distinct meanings in research administration. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
25. Organizations and departments need separate modelling
A department name can be translated in prose while the organization relationship is anchored through its own identifier. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
26. Funder and host organization are different roles
The organization paying for research is not necessarily the institution hosting or performing it. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
27. Facilities can be related resources
Major instruments, facilities and infrastructure can be linked to the activity without becoming the RAiD itself. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
28. Datasets can have their own DOIs
A dataset produced by a project can carry a DOI while remaining related to the same RAiD. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
29. Publications can be outputs rather than identifiers for the project
One project can produce many publications, so a paper DOI should not replace the activity identifier. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
30. Software can be a project output
Code, packages and software releases can be linked to the research activity while retaining their own identifiers. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
31. Samples can be linked through IGSN IDs
Physical samples can carry IGSN identifiers and still be connected to the project that collected or analyzed them. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
32. Milestones are not new project identities
A major milestone or work package can be described separately without automatically becoming a new RAiD. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
33. Subprojects require explicit governance
If a programme contains distinct activities, the decision to create related RAiDs should follow project governance rather than translation convenience. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
34. Research programmes and individual projects differ
A programme-level activity can span several projects; translation should preserve hierarchy instead of collapsing levels. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
35. Lifecycle relationships should be time aware
A person or organization can be associated only during part of the activity, so temporal qualifiers should survive translation. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
36. Acronyms are discovery labels, not identity
Project acronyms can collide across disciplines and countries. Keep the RAiD as the stable disambiguator. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
37. Project titles can be reused
Different research activities can share similar or identical names, making identifier-based matching safer than title matching. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
38. Machine translation should not process the RAiD
The identifier has no linguistic content and should be masked or locked before automated translation. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
39. Translation memory can carry the wrong project ID
Repeated administrative phrases can insert a stale RAiD from another project unless identifiers are treated as variables. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
40. CSV exports can create row-shift errors
A valid RAiD can be attached to the wrong project after sorting, making relational QA essential. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
41. JSON APIs should separate RAiD and display text
Changing locale should alter project titles and descriptions, not the identifier field. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
42. OCR is rarely the right source for RAiD identity
Screenshots and PDFs can corrupt persistent identifiers; retrieve the canonical value from the registry or source system. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
43. Right-to-left interfaces need identifier isolation
Arabic and Hebrew project pages should keep the RAiD or URL in canonical order while surrounding prose follows target direction. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
44. Project status language needs precision
Active, completed, withdrawn, paused and planned can describe different project states that should not be blurred in translation. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
45. Administrative closure is not the same as scientific completion
A project can close financially while outputs or data curation continue; translated status text should preserve that distinction. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
46. Search intent: translate a RAiD
Users typically need to know whether the identifier changes with language and how to translate the project metadata around it. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
47. Search intent: identify a research project PID
A code in a research system may be RAiD, grant ID, DOI or internal project ID, so namespace recognition should come before translation. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
48. Search intent: translate a project title linked to RAiD
The visible title can be translated for discovery while the persistent identifier remains stable. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
49. Search intent: translate project participants
Names, roles and affiliations can be localized or transliterated under their own policies while their PID relationships remain connected to the RAiD. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
50. Worked example: one project with two grants
A project receives funding from two sources. The grant identifiers remain separate metadata while the RAiD identifies the shared research activity. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
51. Worked example: researcher changes university
A contributor moves institution midway through the project. The activity keeps one RAiD while affiliations change over time. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
52. Worked example: multilingual public project page
English, French and Japanese pages show different titles and descriptions but resolve to the same RAiD-backed project record. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
53. Worked example: dataset and publication outputs
The same activity produces a dataset DOI and several publication DOIs, all linked back to one RAiD. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
54. Worked example: programme and subproject
A large programme contains several distinct projects. Translation preserves the hierarchy instead of treating every work package as the same activity. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
55. Bulk research-system migrations need project-level reconciliation
Migration QA should compare participant, organization and output relationships by RAiD before and after localization. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
56. Reference route: RAiD registry
The official RAiD site explains resolution, metadata and the identifier’s role as a global research-project PID. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
57. Reference route: DataCite RAiD guidance
DataCite documentation explains RAiD as a PID for projects and activities and notes ISO 23527:2022 governance. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
58. Connection to ROR
ROR identifies organizations participating in research; RAiD identifies the activity connecting those organizations, people and outputs. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
59. Connection to ORCID
ORCID identifies researchers; RAiD connects those researchers to the project context in which activity occurs. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
60. Connection to IGSN
IGSN identifies material samples; RAiD can provide project context for collection, creation or analysis of those samples. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
61. Connection to the protected language ecosystem
Vocabulary Learning and How English Works support precise role, status and project-language translation while RAiD preserves project identity. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
62. Connection to the master translation architecture
The master translation system owns general terminology and QA governance; this specialist page should remain focused on research-activity identity. In a multilingual workflow, keep the RAiD as protected persistent-identifier data and translate only the human-facing project metadata around it. Quality assurance should confirm not only that the identifier is unchanged, but also that people, organizations, dates, grants, inputs and outputs remain attached to the same research activity. When project identity is uncertain, resolve the RAiD through the official registry instead of inferring identity from a translated title, acronym or grant number.
63. Release checklist
Before release, preserve the RAiD exactly; distinguish the project from its grants, people, organizations and outputs; keep temporal relationships intact; separate project title from persistent identity; protect identifier fields from machine translation, OCR and stale translation-memory matches; and verify every person, ROR, ORCID, DOI, IGSN and funding relationship still belongs to the same research activity. Then review the project title, roles, statuses and descriptions for clear target-language meaning.
64. Final rule: translate the research activity, preserve the project identity
Research projects evolve: people move, organizations change, plans become outputs and funding can come from several sources. RAiD exists so that change does not destroy project identity. Translate the metadata readers need, preserve the persistent identifier systems need, and keep the project’s relationships traceable across the full research lifecycle. See RAiD and DataCite RAiD guidance.