CASRAI Declaration Reviewer

NIKOLAI proposal: a CASRAI Declaration Reviewer is the CASRAI-side reviewer (individual or team) who checks a submitted Mapping Declaration against the existing crosswalk row it targets before that row is permitted to change status from shadow mapping to declared. No review process has processed a live declaration yet — this role is being defined ahead of the Mapping Declaration feature's first use, not documented from an existing case. This wording is a NIKOLAI editorial synthesis, not a quotation from any single source.

This is CASRAI's own proposed definition, not a definition any named organisation has agreed to. See what NIKOLAI is and is not.

Source of record

Where this definition comes from

ANSI/NISO Z39.104-2022 (CRediT, Contributor Roles Taxonomy), §1, Scope
“CRediT establishes a standardized set of roles to describe each author's individual contributions to the work, promoting transparency of contributions.”
https://www.niso.org/publications/z39104-2022-credit

Divergence

Where sources materially disagree

CRediT's 14 roles deliberately exclude peer review — CRediT credits contributors to the work, not reviewers of it. This role therefore has no CRediT role counterpart; it echoes the general contributor-role pattern that ANSI/NISO Z39.104-2022 formalises (a named party, a defined function, recorded against one specific output) while filling a gatekeeping function CRediT's own scope excludes.

Gap

Fully operationally wired, and the clearest contrast among the six N10 roles: casrai_nikolai_decl_rest_approve()/_reject() are gated to a real CASRAI editor (current_user_can('manage_options')) and durably record _reviewed_by (the editor's WP user id) and _reviewed_at on every decision. This is the one and only code path anywhere in this codebase that can set a crosswalk row's declared_by to non-null -- a real, exercised mechanism, not a placeholder.