Processing data

Processing data is defined by user and will be data that will be processed by workflows.

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 “processingData” . Cf to mandatory keys.

  • valueType : It is the type of processing data values and then depends on them. Cf to mandatory keys.

  • meaning: Its value is “Processing data” . Cf to mandatory keys.

  • view: Cf to mandatory keys.

  • dataLocationId: Cf to mandatory keys.

Currently, only numerical vector can be saved during raw data loading which gives us un single template at this moment.

JSON template for numerical vector processing data representation.

{
  "dataSpecification": {
    "keyword": "processingData",
    "valueType": {
      "dataType": "numerical",
      "structureType": "scalar"
    },
    "meaning": "Processing data",
    "view": {
      "id": "637ce534dd85c10875c4fe26",
      "name": "view_11-22-2022_15:05:24"
    },
    "dataLocationId": "62b18d804ae71c6a0025237a"
  }
}

Observation

The key value has always the same String value “DataLocation”, it means to look on associated dataLocationId key which points towards Domain data parquet files.

{
  "observationId": 1,
  "value": "DataLocation",
  "representationId": "62b18d804ae71c6a00252379",
  "dataLocationId": "62b18d804ae71c6a00252371"
}