Key terminology#

Registrants are at the heart of OpenSPP. They are the people or groups that are being registered to be included in social protection programs.

A registrant can be:

  • A group

  • An individual

Depending on the project's requirements, a registrant can simply contain a name or full biographic information, ID numbers, pictures, bank account numbers, phone numbers and more.

Important

Consider only collecting the data you really need when conducting a project.

Concepts#

Individual#

An individual is a registrant that represents a person. It will have all the fields of a registrant plus some additional ones.

Screenshot of the individual registrant list page showing a table with columns for name, registration ID, gender, age, and address

Screenshot of an individual registrant profile page displaying personal details form with fields for name, ID documents, contact information, and demographic data

Group#

A group is a registrant that represents a set of individuals. It will have all the fields of a registrant plus some additional ones.

Screenshot of the group registrant list page showing a table with columns for group name, registration ID, kind, and number of members

Screenshot of a group registrant profile page displaying group details form with fields for group name, type, member count, and administrative information

For example, groups could represent:

Groups do not need to contain individuals registrants. They can just contain their number of members.

For example:

  • Adults: 2

  • Children: 3

  • Elderly: 2

Group membership#

Individuals can be part of one or more groups. They can have specific roles in a group.

Screenshot of the group membership management interface showing a list of group members with their roles, relationship type, and enrollment dates

By default, the following roles exist:

  • Head (only one per group)

  • Principal recipient (only one per group)

  • Alternative recipient

An admin has the right to add other roles using the configuration menu.

Screenshot of the group membership type configuration page showing form fields to define membership roles and their properties

An individual can be the head of a group but have another or no role in another group.

Registrants relations#

When you need to store the relationship between registrants those relations can be useful.

Screenshot of the registrant relations interface showing a list of relationships between registrants with columns for relation type, source, and target registrant

You can define relationship type between different entities:

  • Group - Group

  • Individual - Individual

  • Individual - Group

Screenshot of the registrant relation type configuration page showing form fields to define relationship types between different entity combinations

For example:

  • Sibling (Individual - Individual)

  • Parent/Child (Individual - Individual)

  • Caretaker (Individual - Group)

  • Neighbour (Group - Group)

ID Documents#

Registrants can have one or more ID Documents.

Screenshot of the registrant ID documents interface showing a list of identity documents with columns for document type, ID number, and validity status

The system does not enforce uniqueness of ID Documents by default. If uniqueness is required, deduplication should be performed.

ID Document types can be configured by an administrator.

Event Data#

Event data is a way to store information about a registrant that is not part of the registrant's profile. It allows to store information without the need to modify the registrant's profile, providing following benefits:

  • Store multiple version of the data

  • Manage separate data lifecycle, sharing agreements, etc.

  • Better manage the source of different data

  • Store data that should not be visible to all users

This data can be a lot of things:

  • House visit

  • Raw import data

  • Information coming from another system through synchronization

  • Data that loses relevance over time

The data stored in Event Data can be used in OpenSPP as a normal field by using computed fields.