Import of "Training" data (to TrainingEvent and TrainingEventMetrics)

[joncison]

Overarching issues

• will these data be imported from e.g. TeSS by some mechanism tbd? If so, not sure of value of importing them from the CSV.

Existing fields (in "Training")

Nom de la formation

Mapping: (Training)Event:name
Issues: none

Chemin

Lien vers la formation?

Mapping: (Training)Event:homepage,
Issues:

• missing in most cases - (Training)Event:homepage is mandatory!
• need to check what these links point to

Type de formation

Niveau de formation (formations universitaires uniquements)

Mapping: TrainingEvent:audienceTypes
Issues:

• textual values need mapping to the TrainingEvent:audienceTypes enum

Cours résumé

Description

Mapping: (Training)Event:description
Issues:

• many courses are missing this, but (Training)Event:description is mandatory!
• sometimes URLs are given - which might be better in (Training)Event:homepage

Mots clés

Thème (formations professionnelles uniquement)

Mapping: (Training)Event:keywords, (Training)Event:topics
Issues:

• for each keyword, a corresponding Keyword object should be created, but only for keywords that have not been mapped to EDAM (see mapping file. Where a keyword does map to an EDAM term, (Training)Event:topics should be populated instead.

Date de la session

Date de la session

Mapping: (Training)Event:dates, TrainingEventMetrics:dateStart, TrainingEventMetrics:dateEnd
Issues:

• why are there two columns with the same name in the CSV?
• decision is needed about past events, with respect to populating TrainingEventMetrics objects

jouy en josas

Mapping: (Training)Event:venue, (Training)Event:city, (Training)Event:country ??
Issues:

• values are a mixture of institutes and places! So the mappings above are just alternatives.

Organisateurs

Mapping: (Training)Event:organisedBy
Issues:

• very spare data
• to populate this require new Organisation object(s) ; mandatory fields are name, description and homepage.

Sponsors

Mapping: (Training)Event:sponsoredBy
Issues:

• to populate this require new EventSponsor object(s) ; mandatory fields are name & homepage.

Nombre de participants académiques

Mapping: (Training)Event:maxParticipants, TrainingEventMetrics:numParticipants
Issues:

• note the distinction of TrainingEvent and TrainingEventMetrics

Nombre de participants académiques

Nombre de jours

Taux de satisfaction des apprenants

Mapping: none
Issues:

• these could be added to TrainingEventMetrics, but see Refine TrainingEventMetrics model with inputs from FR training folk #113

Participation

Mapping: (Training)Event:costs
Issues:

• values need to be mapped to the costs controlled vocabulary

Opérateur de la formation

Mapping: (Training)Event:hostedBy
Issues:

• (Training)Event:hostedBy is "Organisation which is hosting the event." Need to check the mapping is right, esp. with respect to "Organisateurs" above

Nombre de sessions

Reccurance

Mapping: none
Issues:

• this will be handled / could be calculated by the relation between TrainingEvent and TrainingEventMetric (the number of metrics equates to the number of past sessions), alternatively through TrainingEvent:dates (for future sessions).

Temps de formation

Mapping: TrainingEvent:hoursPresentations, TrainingEvent:hoursHandsOn, TrainingEvent:hoursTotal
Issues:

• note the distinctions in the new model - so these data aren't available

Additional MANDATORY fields (in "Event")

(Training)Event:accessibility

"Whether the event is public or private. "
Issues:

• presumably all are public?

(Training)Event:contactName

"Name of person to contact about the event."
Issues:

• could be made optional as a stop-gap measure

(Training)Event:contactEmail

"Email of person to contact about the event."
Issues:

• could be made optional as a stop-gap measure

[bryan-brancotte]

imported