# Design, Development and Use of a Digital Badges System in Higher Education
## 4 Badges Module
### Views  
Within the section Group badges, previously mentioned, a number of possibilities will be given for the development and the viewing of the plugin, for which a varied set of features exist.  
Figure 3: Configuration of badge by contest.  
Figure 2: Configuration of automatic badge.  
* Creation and edition of badges. These views are used so that the user can create or modify badges, setting their desired parameters as summarized in previous paragraphs. Accordingly, it is possible to produce many types of badges, from the simplest ones with only a few parameters and requirements, up to the more complex end, just adapting to the user's preferences.
* Leaders table. This is an ordered list of users according to the badges they possess (total number of badges and their icons). Moreover, looking at a better user experience, an extra functionality for ordering the list by user name, and by number of badges per user as well, has been included (Figure 4). The list is configurable, with the administrator defining how many students are shown in a screen page.
* View of all badges. A list with all the badges in a group along with a short description of their most important properties (icon, labels, visibility, and type), the creator's identity and the creation date (Figure 5).
* Full view of the badge. A view that shows the set of properties of the badge in detail. In addition, it includes the options to enable/disable the badge, to commit/revoke a badge to a student in case it is a manual badge, and a list of the holders of the badge (Figure 6). Had the badge been a public badge, in this view we will be given the option of creating or deleting a certificate for all the users who have the badge. The reception of such certificate is a proof that the certificate is not tied to a group in the social network, but it is instead a unique and own distinction for the student which will continue in his/her profile even after the group in which it was awarded or the person who created it ceases to exist in the platform.  
Figure 4: Leaders table.  
Figure 5: List of badges of a group.  
View of badges per user. For each user, there exists a view in his/her profile listing the badges won, public and private. The path to this view is through the option \"My badges\" presented in the user profile, or through the button for quick access to the personal badges displayed in the view of badges for all the group members. Here, one can see the icon, group, and description of the badge, provided the latter exists (Figure 7). In the group badges, it should be highlighted that, if the user accessing the view is not a member of that group, she/he will not be included in the table of private badges neither. Finally, next to the table of public badges, a student is given the option to generate a badge that can be linked to his/her account in Mozilla Open Badges (see Appendix A).  
Figure 6: View of badge by contest.  
Figure 7: List of badges of an user.  
In case a badge has to be removed, the option is available either in the private view of the badge or in the view of all the group badges. It is important to recall the removing a badge implies the removal of the Gamepoints assigned to the badge when this is manual.  
Since different types of users exist in the social network, each one with individual characteristics for accessing and viewing the contents, their view of the social network will be obviously different. Thus, users with all the permissions (administators, instructors, others) will be able to see and edit any type of content, spanning from the values of the fields for the badge to the addition of new badges, the modification of the existing, etc. Normal users (typically the students) will only be able to visit the views wherein the change of badges is not possible, or to badges with private visibility. So, their ability to do changes in the global state of the social network is restricted.