OrganizationID

Overview

OrganizationID carries a single identifier value for an Organization participating in a research workflow (typically the publisher), together with an idType attribute that names the identification scheme. It enables publishers, vendors and consumers to refer to the same organization consistently across distribution platforms, regulatory systems and internal databases, and supports UUID-based identification for guaranteed global uniqueness (sources: user-guide-2.1 p.17, user-guide-2.2 p.17, data-dictionary-2.4 p.26).

Usage

OrganizationID appears as a child of Organization. The value is free-text string content holding the actual identifier; the scheme is declared via the required idType attribute (e.g. VendorCode, CUSIP, UUID, or the special L1 value for Level One) (sources: user-guide-2.2 p.17, data-dictionary-2.4 p.26). Cardinality has changed across versions: - In RIXML 2.0–2.2, at least one OrganizationID was required per Organization, with multiples permitted (sources: data-dictionary-interactions-2.0 p.16, user-guide-2.1 p.17, user-guide-2.2 p.17). - From RIXML 2.3 onward in the full schema, the element was relaxed to optional (zero or more) within Organization, so publishers can omit it for internal workflows or destinations that do not require organization identifiers (sources: release-notes-2.3 p.2, best-practices-guide p.16, user-guide-2.3 p.17, user-guide-2.3.1 p.17, data-dictionary-2.4 p.26, data-dictionary-2.5.1 p.26). - Under Level One compliance (2.2 through 2.5), exactly one OrganizationID is required, its idType must equal L1, and its content must be a UUID for the publisher (sources: level-one-2.2 p.12, level-one-2.3 p.7, level-one-2.3.1 p.7, level-one-2.4 p.25, level-one-2.5 p.7). Multiple OrganizationID instances are typical when the same organization is distributed through several vendor platforms, each expecting its own identifier scheme (sources: user-guide-2.1 p.17, user-guide-2.2 p.17, user-guide-2.3 p.17, data-dictionary-2.5.1 p.26). A v3 draft restructures this into an OrganizationIDList container holding one or more OrganizationID children, but the element semantics — string value plus required idType — are unchanged [data-dictionary-v3-draft p.37].

Rules

• MUSTEach OrganizationID MUST carry an idType attribute identifying the scheme of the identifier value.[RIXML User Guide v2.1 p.17] [RIXML User Guide v2.2 p.17] [RIXML Research Data Dictionary v2.4 p.26] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.37]↗
• MUSTIn RIXML 2.0–2.2, an Organization MUST contain at least one OrganizationID; multiple instances are permitted to support distribution through several vendors.[RIXML User Guide v2.1 p.17] [RIXML User Guide v2.2 p.17]
• MAYFrom RIXML 2.3 onward (full schema), OrganizationID is optional within Organization and MAY be omitted when not required by the consumer or when used internally.[RIXML Release Notes v2.3 p.2] [Best Practices for Publishing RIXML p.16] [RIXML User Guide v2.3 p.17] [RIXML User Guide v2.3.1 p.17] [RIXML Research Data Dictionary v2.4 p.26] [RIXML Research Data Dictionary v2.5.1 p.26]
• MUSTFor Level One compliance, Organization MUST contain exactly one OrganizationID whose idType is set to the special value L1.[RIXML Level One Addendum v2.2 p.12] [RIXML Level One Addendum v2.3 p.7] [RIXML Level One Addendum v2.3.1 p.7] [RIXML Level One Addendum v2.4 p.25] [RIXML Level One Addendum v2.5 p.7]
• MUSTFor Level One compliance, the value of OrganizationID MUST be a UUID identifying the publisher organization.[RIXML Level One Addendum v2.2 p.12] [RIXML Level One Addendum v2.3 p.7] [RIXML Level One Addendum v2.3.1 p.7] [RIXML Level One Addendum v2.5 p.7]
• MUSTIn Level One 2.5, the UUID used in OrganizationID MUST be distinct from the UUIDs used for researchID, productID and resourceID.[RIXML Level One Addendum v2.5 p.7]
• SHOULDOutside Level One, publishers SHOULD include a UUID as one of the OrganizationID values to guarantee global uniqueness across systems and time.[RIXML User Guide v2.1 p.17] [RIXML User Guide v2.2 p.17] [RIXML User Guide v2.3 p.17]

Relationships

• child-ofOrganization — OrganizationID is a child of Organization; cardinality is required (1..n) in 2.0–2.2 and optional (0..n) from 2.3 onward in the full schema, and exactly 1 under Level One.
• qualified-byOrganizationID.idType — The idType attribute qualifies OrganizationID by naming the identification scheme of the value (e.g. VendorCode, CUSIP, UUID, or L1).
• co-occurs-withOrganizationName — Under Level One 2.4, OrganizationID with idType='L1' is paired with an OrganizationName that carries nameType='Display' to identify the primary publisher.
• contained-inSource — Within research metadata, OrganizationID is reached via the Product → Source → Organization path and identifies the source/publisher organization for the product.