Applicants

Data Management This task should be performed in the Data Management panel.

Applicants

Applicants represent entities (typically organizations) that request analyses within the system. These entities can be structured hierarchically, where one applicant can be a parent of another applicant. This allows organizations to model their structure with subdivisions, departments, or sub-organizations, each handling its own data and analyses.

Important Considerations

• Applicants are essential to the system as they represent the entities requesting the data and analyses.
• Applicants and Sources: Each applicant must be linked to at least one Source to track and manage the data used for analyses. If an applicant requires multiple sources, you must create multiple Applicant-Source pairs to properly define the visibility and control of data.
• Default Source (G1): Every applicant operating on COHESIVE should have at least one Source with the code G1 to ensure full functionality within the system.

Creating an Applicant

1. Access the Applicant Section:

   • You can navigate to the Applicant section either by using the navigation menu:
     All Items → Classes → Applicants, or by using a direct link like:
     <http://your_instance:your_port/cmdbuild/ui/#classes/T_RICHIEDENTE/cards>

2. Add a New Applicant:

   • Click the Add Card button to open the form for creating a new applicant.

3. Fill in the Required Fields:

   • Code: Enter a unique code for the applicant (e.g., ONE_HEALTH).
   • Description: Provide a name or description, such as One Health Organization.
   • Father: If this applicant is a child of another applicant, select the parent applicant (optional).
   • Source: Select the Source associated with this applicant.

4. Save the Applicant:

   • After entering the information, click Save or Save and Close to create the new applicant.

Why Applicants are Important

Applicants are crucial in defining the organizational structure in the system. They allow for data partitioning, helping you manage the visibility and control of data. Each Applicant represents an entity requesting data, and by associating an applicant with a Source, you ensure that the right data is available for the right users, while still maintaining security and data segregation.

Exercise

Try to reproduce the example provided above by creating the applicants and associating them with the relevant sources. For more details, refer to the Visibility Model.

Tip: If an applicant has multiple sources, you need to add the same applicant multiple times—once for each source. It is recommended to give the applicant a distinct name for each source by adding a suffix. For example:

• PUBLIC_HEALTH_G1 (for the G1 source)
• PUBLIC_HEALTH_WS (for the web service source)