This document presents the results obtained by synchronisation and clarifies some mapping elements.

These tasks are handled in production through the Moodle CRON. Manual triggering is meant for demonstration and qualification, when a check is needed, or when a sync is needed without waiting for the crons to run.

When triggered manually, they should therefore be run in the order of this documentation.

This action rebuilds the Moodle cache with up-to-date NetYpareo data.

Result:

      Running on :
      Name : Test Ymag
      Base URL : https://demo.ymag.fr/netypareo/
           Updating cache status for instance 0 
             Reading 37 records...

This synchronisation meets three usage needs:

• In the case of a multi-tenant NetYpareo (several institutions).
• In the case of a NetYpareo to a multi-tenant Moodle.
• In the case of a multi-tenant NetYpareo to a multi-tenant Moodle.

Cohorts are therefore created (with the names of the institutions addressed in this example). These cohorts are not populated with users. They will be populated by the other synchronisations.

Result with two different NetYpareo instances:

the first is a NetYpareo test database, the second a CFA (apprenticeship training centre).

      Running on :
      Name : Test Ymag
      Base URL : https://demo.ymag.fr/netypareo/
           Syncing cohorts...
             Site cohort updated: SITE1 [SITE_S1]
             Site cohort updated: SITE2 [SITE_S2]

      Running on :
      Name : CFA Montpellier
      Base URL : http://ypareo.cfaen34.fr/netypareo-test/
            Syncing cohorts...
             Site cohort updated: CFPPH [1_SITE_CFPPH]
             Site cohort updated: Jean-François CHAMPOLLION [1_SITE_CHAMPO]
             Site cohort updated: Jean MERMOZ [1_SITE_MERMOZ]

As a reminder, this sync is based either on the user name (NetYpareo IDnumber or username) or, as chosen, on the identification number (UserID) through the component's central settings.

Here in this example: To be specified

From the following API functions:

• get_utilisateur_apprenant: Site code at zero: therefore whatever the site
  • Filtering possible on status
  • only exists if a NetYpareo account is activated
• get_utilisateur_formateur
• get_utilisateur_tuteur: no site code (we don't know which institution cohort they belong to, we will rely on the learner/tutor matching if it exists)

Result:

User student updated: [apprenant10007] [6106273]
User student updated: [apprenant10105] [6116669]  
             Explanations: [Username] [IDnumber: user ID in NetYpareo]

Result:

       Running on :
       Name : Test Ymag
       Base URL : https://demo.ymag.fr/netypareo/
        Syncing tutors...
             User tutor updated: [entreprise42] [7557909]
             User tutor updated: [interlocuteur10] [300626]
             User tutor updated: [interlocuteur100] [306977]
             User tutor updated: [interlocuteur10000] [6526799]

• In Moodle: The notion of cohort is a gathering of users with the same role. Any cohort can then be automatically synchronised with any course in Moodle by adding one (or several) cohort enrolment method instance(s) to the various courses.
• In NetYpareo: This notion of cohort does not exist in NetYpareo. There are however two notions of groups in NetYpareo, found through two API functions:
  • Get_group_FC: Corresponds to one-off training actions (from date to date)
  • Get_group: Corresponds to qualifying training actions associated with a training programme and defined subjects.

These groups are therefore pulled into different cohorts in Moodle, from the two menu buttons present in the interface.

Result:

Image to be placed

R&D not completed, preparatory code done, but waiting for an operator request

• Valéry Frémaux (valery@activeprolearn.com) Design and development
• Florence Labord (florence@activeprolearn.com) Documentation and qualification

Back to the component index - Back to plugins index - Back to catalogue