Import of "Infrastructure" data (to ComputingFacility)

[joncison]

Overarching issues

• confirm that all of these infrastructures are still active, and should become ComputingFacility

Existing fields (in "Infrastructure")

Nom de la plateforme

Mapping: ComputingFacility:name
Issues:

• Check that name is not used for database look-up, as the names can include accents (refactor accordingly using pk for look-up as needed)

Type d'infrastructure

Mapping: ComputingFacility:providedBy
Issues:

• Fill in missing values (for P3M, IMGT etc.)
• The current value is just "Hébergée" ir "Propriétaire" whereas the new model does not make this distinction: ComputingFacility:providedBy points to the BioinformaticsTeam that either "hosts" or "owns" the facility. Confirm that this is OK.
• to populate this require a BioinformaticsTeam object for each infrastructure, but this is not mentioned in the CSV file. Mandatory fields for BioinformaticsTeam are name, description, homepage, at least one member (a UserProfile), at least one maintainer (a UserProfile) , orgid, ifbMembership (an enum) and fundedBy (an Organisation). Decide what to do!

Capacité de stockage utile

Mapping: ComputingFacility:storageTb
Issues:

• fill in missing values (although ComputingFacility:storageTb is not mandatory)
• must parse weird number format / syntax (esp. for values > 1000) into an integer

Nombre de CPU

Mapping: ComputingFacility:cpuCores
Issues:

• fill in missing values (although ComputingFacility:cpuCores is not mandatory)
• weird number format / syntax (integer would be better)

Collections de données

Mapping: none
Issues:

• this a magic number, mostly not provided in the CSV. Instead the new model will support which ComputingFacility a Database is "providedBy" (implementation of Database is to-do). If sum of such databases is needed, this could be calculated.

Heure de CPU / An

Mapping: ComputingFacility:cpuHoursYearly
Issues:

• fill in missing values (although ComputingFacility:cpuHoursYearly is not mandatory)
• weird number format / syntax (integer would be better)

Outils bioinformatiques

Mapping: none
Issues:

• same as for "Collections de données" - the new model will support which ComputingFacility a Tool is "providedBy" (implementation of Tool is to-do). Sum of tools could be calculated.

Nombre d'utilisateurs

Mapping: ComputingFacility:usersYearly
Issues:

• the numbers vary wildly, so needs to be checked what is actually given here (new model is for yearly users)
• weird number format / syntax (integer would be better)

Conditions d'acces

Mapping: ComputingFacility:termsOfUse
Issues:

• Value in CSV is a string, but new model has this as a URL - what to do?

Descriptions des serveurs

Mapping: ComputingFacility:serverDescription
Issues:

• none, although the descriptions themselves are highly variable (standards/guidelines would help)

Titre appui a projet

Mapping: none
Issues:

• no field for "Project support title" in new model, rather, a Project can state what ComputingFacility it uses.
• The text is missing in most cases, and isn't super-useful where it is given

Description aide à projets

Mapping: ComputingFacility:description
Issues:

• not sure whether the text given here is really suitable as a general description of the ComputingFacility, but it seems the most appropriate. Must check (a new field may be necessary) - bear in mind ComputingFacility:description is mandatory.

Projets accompagnés

Mapping: none
Issues:

• no field for (number of) "Supported projects" in new model, rather, a Project can state what ComputingFacility it uses (so this number could be calculated).
• likely new model needed for ComputingFacilityMetric (in similar way as for TrainingEventMetric) after consultation

Conditions d'appui

Mapping: none
Issues:

• The text is missing in most cases, and isn't super-useful (to general users at least) where it is given

Projets hébergés

Mapping: none
Issues:

• no field for (number of) "Hosted projects" in new model, rather, a Project can state what ComputingFacility it uses (so this number could be calculated). NB: distinction between "hosted" and "supported" is not made in the new model. This is also suitable for inclusion in ComputingFacilityMetric.

Publications

Mapping: none
Issues:

• this is a magic number with no field in the new model - if really needed, an objective way to calculate number of publications relevant to a ComputingFacility is needed

Additional MANDATORY fields (in "ComputingFacility")

homepage

"URL where the computing facility can be accessed."
Issues:

• no field for this in CSV!

accessibilityType

"Accessibility of the computing facility to end-users."
Issues:

• no field for this in CSV! (values are "Internal", "National", "International")