Stewarding definitions and data quality
You keep the meaning of the data stable: indicator and variable definitions, codebooks, semantic mappings and the quality of what was collected. You review and approve; you do not run analyses or export data.
What you are responsible for
Approving codebooks, reviewing semantic mappings, reading study governance and consent status, and the quality decision on flagged responses. You are not responsible for creating analyses, recording consent, collection, publication, integrations or administration, and the platform refuses each of those to this role.
Where you start
Signing in takes you to Semantic Governance: the catalog, indicators, mappings, collisions and coverage. Your navigation also carries Operations Queue, Data Quality and Data Governance; every entry is a page whose server routes accept this role.
Definitions, codebooks and mappings
- Reading the catalog, indicators, codebooks and mappings uses analysis.read.
- Approving a codebook and reviewing a semantic mapping use analysis.review, which this role holds.
- Proposing a new mapping or reference definition uses analysis.create, which this role does not hold. Somebody else proposes; you review.
Study governance
Data Governance shows jurisdiction policy packs, a study’s resolved policy and its ethics amendments, read-only for this role. Changing a study’s governance profile needs organization.update, submitting an amendment needs analysis.create and deciding one needs evidence.review; this role holds none of the three.
Quality and the task queue
Data Quality lets you approve or reject flagged responses. Operations Queue shows tasks whose gate needs quality review or analysis reading, and the data-quality issues you can review and resolve.
When something goes wrong
| What you see | What to do |
|---|---|
| A save is refused with a permission code | The action needs a permission outside this role, usually analysis.create or organization.update. The refusal names it. |
| A mapping review is refused | The refusal names the reason: the mapping was already reviewed, its target indicator is not yet approved, or an AI suggestion is being approved without a review note. |
| The catalog is empty | No datasets or indicators have been declared for your organization yet. |
Limits worth knowing before you plan around them
What this role cannot do, and what the platform does not offer
- This role cannot export data (no data.export) and cannot create or approve an analysis.
- It can read consent status but cannot record consent.
- It has no collection, publication, integration or administration authority.
- It cannot decide an ethics amendment; that needs evidence.review.