In this section we will discuss how the licensing systems of LEVERADE work. This is one of the most important parts of our platform and it is essential to completely understand the hierarchy so that it can be applied correctly.
Basic concepts
We will begin with the specific functions of the LEVERADE licensing system
configuration by giving a brief explanation of some of the basic concepts of this task.
First, we’ll separate them into: Profile, License and Participant.
Profile: unique information about the person in a team. Data that will generally not change from one year to the next. For example: Name, Date of Birth, Gender.
License: information that allows someone to participate in a competition and which can change from one year to the next, or even in one season. For example type (of player or referee), club, discipline, category etc.
Participant: the license registration for the competition. It is not normally necessary to add extra information but if it is, this can be something like the player number.
Configure licenses
Now that we’ve understood the structure that personal data follows in LEVERADE, we can start to develop the tools to configure the license registration process in the federation: Fields, Positions, Numbering Rules and Forms.
Fields: is the information that the team must gather from all its players, referees, managers and members of the technical team.
LEVERADE offers default fields but the team can easily create as many as they want.
Things to bear in mind when creating fields:
-Type: the type of data that we want to gather and in which format we want to gather it. The types of fields that can currently be created in LEVERADE are: Text, Telefone, Numeric, List (to select an option from various options that can be set up), Date, Web address, email and Check box (for the team to accept an obligatory or optional condition)
-Position: the order in which we want to show the fields in the form.
-Internal Code: can only contain lowercase letters (a-z), numbers (0-9), underscores (_), must start with a letter and not end with an underscore. This is what our API will read when it connects LEVERADE to an external program.
-Name: the name we wish to assign to a field and which helps the user to understand which data is required.
-Description: A button that opens up a dialogue box telling the user what must be filled out in this field or, for example, the Data Protection Terms & Conditions that need to be accepted when registering the license.
-Unique: When a field is unique, there can be no equal data to it in the team’s entire database. For example, the ID document must be unique since two people can’t have the same number.
-Applicable: Wherein the user’s data must be filled in, if it is data required for the profile, license or participant.
Positions: Directly linked to the licenses and allow for the creation of license subtypes under the same form, allowing for a more effective and precise organisation of our licenses. For example, a technical team license can include as many innumerable subtypes: doctor, delegate, trainer, physio, etc. Creating them is very simple, we just have to select the type of license and give it a name and an internal code.
Numbering Rules: Unique alphanumerical identifiers that we can include in our licenses. The system allows for the creation of its own numbering rules and their inclusion in the license forms. In this way, every time a license is generated it receives a unique identifier. Creating this is also very simple: we include the name, the alphanumeric pattern that we want to be included in the licenses, and the last number used (in case it comes from another numbering system and they have already assigned these numbers to users).
Forms configuration
Finally, let’s look at the configuration and definition of the forms. We’ve left these until the end because to configure the forms properly we first need to set the fields, the positions if needed and the numbering rules, if the team uses them.
-Forms: all the fields that the team set up for the users to fill in their personal information in order to create their profile, register their license or sign up for a competition.
It’s important to understand the difference between the profile, the license and the participant when configuring the forms because in both the license forms and the participant forms the fields applicable to the profile will be enabled in “Available fields”, as we’ll see later when we set the license and participant forms.
First we’re going to configure the profile form since generally it will only be necessary to have one form to register all the profiles of the team.
To begin, we need to give the form a name, decide if we want the information to be automatically validated (by unchecking “active”, we ensure that no one can fill in the form) and in which dates we want it to be active:
Next, we must add the “Available fields” that we want the users to fill in when registering their profile in the team. For this, we click on the field, mark whether it is obligatory or not and then click “Add”:
If the field is a list and we want to select some of the options and not all of them, we can do this by clicking on each option and pressing the “ctrl” key at the same time.
Once all the fields have been added, we click “Save”:
Next, we’ll create the license form, which is different from the profile form in several ways. Firstly, because we can set a price for the different license forms, based on our list of prices and also because we must select “Advanced form required”.
-Advanced form required: this is the form that someone from an advanced level had to process previously. Meaning, if we are setting a license form, the advanced form will be a profile form, and if we are setting a participant form, the advanced form will be a license form.
There can be one advanced form or several, for example, a participant form for the “First Division” competition can have “Youth” and “Absolute” license forms as advanced forms.
Furthermore, when you select a required advanced form, it will gather the information previously filled in by the person, meaning they don’t have to fill in the same information twice and LEVERADE will automatically be updated.
Next, we need to add the “Available fields” that we want users to fill in when processing their license. An important thing to note is that we can check that the fields that correspond to the profile appear as available.
These profile fields, in the license form, don’t work the same way as the fields that the user must fill in in their license form (Since they already filled them in in their advanced profile form), if including them doesn’t act as a restriction. For example, if we add the field “Sex” and choose the option “Male”, only people that have filled in “Male” in their profile form can also process this license.
Finally, we’ll look at creating the participant form, which is the additional information that a user must fill in to sign up to a competition. Like in the previous forms, we need to assign them a name, a price if necessary, select the required advanced form(s) and mark if they are active or not and on which dates, if necessary.
Normally it is not necessary to fill in any fields and the most common course of action is to set restrictions, such as that license expiration date coincides with the end date for the selected season:
