This page shows how OpenSPP vocabulary codes map to PublicSchema canonical values. If you work with OpenSPP and spot an error, please report it.

19 vocabulaires covered: 15 correspondance de valeurs, 4 même norme.

Vocabulaires

Vocabulaire Nom dans le système Relation Couverture Lacunes
country Même norme Toutes les valeurs
currency Même norme Toutes les valeurs
education-level Education Level (ISCED 2011) Correspondance de valeurs 9/10 correspondances
event-severity HazardIncidentSeverity Correspondance de valeurs 5/5 correspondances 1 non couvert(s)
gender-type ISO 5218: Gender Correspondance de valeurs 3/4 correspondances
group-role Group Membership Type Correspondance de valeurs 1/1 correspondances 12 non couvert(s)
group-type Group Type Correspondance de valeurs 2/2 correspondances 2 non couvert(s)
identifier-type ID Type Correspondance de valeurs 4/4 correspondances 16 non couvert(s)
language Même norme Toutes les valeurs
marital-status MaritalStatus Correspondance de valeurs 6/6 correspondances
occupation Même norme Toutes les valeurs
payment-status Correspondance de valeurs 6/6 correspondances 4 non couvert(s)
relationship-type Correspondance de valeurs 10/10 correspondances 6 non couvert(s)
sex ISO 5218: Gender Correspondance de valeurs 4/4 correspondances
sp/benefit-modality Correspondance de valeurs 2/2 correspondances 4 non couvert(s)
sp/eligibility-status Correspondance de valeurs 1/1 correspondances 4 non couvert(s)
sp/enrollment-status Correspondance de valeurs 4/4 correspondances 2 non couvert(s)
sp/entitlement-status EntitlementState Correspondance de valeurs 8/8 correspondances 2 non couvert(s)
sp/grievance-status Correspondance de valeurs 6/6 correspondances 2 non couvert(s)

Lacunes documentées

Éléments de PublicSchema que OpenSPP ne modélise pas, avec la raison documentée.

Élément PublicSchema Raison
benefit-frequency OpenSPP does not have a vocabulary or selection enum for benefit delivery frequency. Cycle recurrence in OpenSPP is configured via date ranges and the Odoo recurrence infrastructure (RRULE), not a controlled vocabulary.
event-certainty No OpenSPP vocabulary or selection for data certainty or confidence level on recorded attributes.
conditionality-type OpenSPP does not expose a conditionality classification vocabulary. Whether a program is conditional or unconditional is implicit in program configuration, not a controlled vocabulary field.
delivery-channel OpenSPP does not have a delivery channel vocabulary. Payment delivery mechanism is determined by the FSP (Financial Service Provider) configuration, not a separate enumeration.
grievance-type OpenSPP GRM does not have a structured grievance category vocabulary in the extracted data. Ticket categorization is done through configurable category records (spp.grm.ticket.category), not a fixed selection enum, making a code-level mapping impossible without deployment-specific data.
hazard-type OpenSPP spp_hazard module defines hazard incidents but does not expose a hazard type classification vocabulary or selection in the extracted data. Hazard types would be configured per deployment.
referral-status OpenSPP does not have a referral module or referral lifecycle vocabulary in the extracted data. The spp_case_base module tracks intake source (including 'referral') but not outbound referral status.
targeting-approach OpenSPP does not have a controlled vocabulary for targeting methodology. Targeting is implemented through configurable filter rules and scoring models (spp_scoring), not a classification vocabulary.
script No OpenSPP vocabulary for writing scripts (ISO 15924). OpenSPP language vocabulary uses ISO 639 codes only.
region No OpenSPP vocabulary for UN M49 geographic regions. Country selection uses ISO 3166-1; regional groupings are not exposed as a controlled vocabulary.