Entity Level Badges
What are Entity Level Badges?
Badges are a way of tagging users in the program based on their roles, gender, achievement, etc. Badges can be either (a) Assigned by the program or (b) Self-declared by the participants.
Badges allow programs under the entity to identify participants for building their learning pathways, tracking the activities performed and connecting with them for relevant opportunities. Badges also assist the participants to track their own capacity building journey as well.
Example: Master Trainer, Village Community Facilitator, Community Resource Personnel, Quality Inspector, Medical Officer, Gender (Male/Female), etc.
Entity level badges ensure there is standardization of badges with respect to the type and nomenclature of the badges, which can be inherited by the programs if required, as guided by the entity. It helps the entity in monitoring and analyzing the data for specific badges across the programs.
Entity level badges can be created by Entity Administrator(s) only.
Example: There could be a role of Health Worker (Female) across 3 different programs under the entity – National Health Mission. Creating a separate badge for the same role individually under all the 3 programs may result in variation with respect to nomenclature thus making it difficult to analyze the data for all the 3 programs together. Instead, this badge could be created at the entity level and all the 3 programs can inherit the same from the entity thus avoiding any discrepancy.
Badge Type
Badge type denotes a class of badges that have similar characteristics and behaviors. Examples of badge types include Role, Gender, Contract type, Achievement etc. The attributes of the Badge type indicate their functionality and behavior.
For a given Badge type, programs can define multiple Badges. A Badge is always mapped to one of the Badge Type and these badges inherit the attributes of the Badge type.
Badge Type Attributes:
Validity Applicable: Some badge types like Role badges could have validity period which is Time bound. And some badges like Gender will not have any validity so they would be Open-ended. This can be set depending on the Badge Type.
Self-Declared/Assigned: There are some badges that program might need participants to Self-Declare and the program trusts the badge data shared by the participants. On the other hand, Programs could choose to Assign some badges.
Badges are usually Assigned by the program, basis participant satisfactorily meeting certain desired requirements as defined by the program. Assigned badges are intrinsic to the program for their tracking & analysis and their details are not visible/accessible to the participants.
Single/Multiple values: This indicates whether the badge (when assigned /self-declared) can support multiple values. For example, an individual could play multiple roles in a program. Ex: A ‘Role’ badge type can be set to multiple values, whereas ‘Gender’ can be mapped to single value setting only.
Status (Draft/Published/Deactivated): Once created, a badge type is in a Draft status. Only once a badge type is published can a Badge (s) be mapped to it. If a Badge type is Deactivated, no badges can be assigned to the deactivated Badge Type.
Different badge types can have these three attributes in different permutations depending on the nature of badge type.
Entity can define as many Badges as appropriate for a specific Badge Type. A Badge is always mapped to one of the Badge Types. These badges inherit the attributes of the Badge type that a particular badge belongs to.
Entity Administrator would create the badge type(s) with required attributes and create the necessary badges under each Badge Type. Once this is done, the program administrators can choose to inherit the badge type(s) and badge(s) from the entity.
Add and Publish Badge Type
On the program page, click on Entity>Badges>Badge Type
Click on “+” to create a new Badge Type. Enter the Badge Type name, description and choose the required settings and click on “Add”. The Badge Type will be in “Draft” status.
Once a Badge Type is created and its attributes are finalized, then it needs to be Published. Only after a Badge Type is Published, the Badges can be mapped to the specific Badge Type. This can be done by clicking on the desired Badge Type and clicking on the Publish icon.
Remember: Badge type(s) can be deleted till it is in draft status. Once published, it can only be unpublished but cannot be deleted.
Add Badges
For a given Badge Type, multiple Badges can be defined.
On the program page, click on Entity>Badges>Badges
Click on “+” to create a new Badge. Select the required Badge Type under which the badge needs to be created, enter the Badge name and description and click on “Add Badge”. The Badge will be created.
Now, the badges created under the badge type can be inherited by the programs under the Entity.
Remember:
Once the badge(s) is inherited by any program(s), then the badge cannot be deleted, it can only be deactivated.
Badge details (name and description) can be edited even after the badge has been issued (self-declared or assigned) to participant(s).
Delete or Deactivate Badges
Delete Badges: Badges can be deleted till the selected badge is issued (self-declared or assigned) to a participant(s).
Deactivate Badge: If a badge is already created but you no longer want the badge to be assigned or self-declared, then the badge can be deactivated.
Existing badge declarations for the deactivated badge will still be valid and show up in all the relevant reports. However, future declarations of a deactivated badge will not be possible.
You can deactivate or delete by clicking on the required badge.
Remember: Once the badge is assigned or has been self-declared, then the option to delete will not be available. Such a badge can only be deactivated.
Last updated