Hard clustering

Representation

Keys _id, name, stepId, domainInformation, dataset, project, processingInfo, creationTS , latestUpdateTS are unchanged and follow the classic of representation only dataSpecification keys are changed and are described as above :

• dataSpecification :
  • keyword: Its value is “hardClustering” . Cf to mandatory keys
  • valueType: cf to mandatory keys
    • dataType: Its value is “categorical” . Cf to mandatory keys
    • structureType: Its value is “scalar” . Cf to mandatory keys
  • meaning: Its value is “Observation cluster membership” . Cf to mandatory keys.
  • view: Cf to mandatory keys.
  • dataLocationId: Cf to mandatory keys.
  • indices: List of HardClustering ClusterIds.

{
  "dataSpecification": {
    "keyword": "hardClustering",
    "valueType": {
      "dataType": "categorical",
      "structureType": "scalar"
    },
    "meaning": "Observation's Cluster belonging",
    "view": {
      "id": "637ce534dd85c10875c4fe26",
      "name": "view_11-22-2022_15:05:24"
    },
    "dataLocationId": "62b18d804ae71c6a0025237a",
    "indices": [
      1,
      2
    ]
  }
}

(hard_clustering_obs)=

Observation

The HardClustering observation schema is pretty simple and consist only on an integer value for key value which represent the ClusterId of the associated observation for a given HardClustering where complementary information are in the representation.

The observation value key is an integer which specify in which Cluster belong the observation for a given HardClustering.

 {
  "observationId": 0,
  "value": 1,
  "representationId": "62b18d804ae71c6a0025237a",
  "dataLocationId": "62b18d804ae71c6a00252379"
}