(QM) Add new integer profile instance for QM data retention

spec/MicroWaveDeviceInventory+config.json

@@ -384,6 +384,22 @@
             }
           }
         },
+        {
+          "uuid": "mwdi-1-3-0-integer-p-007",
+          "profile-name": "integer-profile-1-0:PROFILE_NAME_TYPE_INTEGER_PROFILE",
+          "integer-profile-1-0:integer-profile-pac": {
+            "integer-profile-capability": {
+              "integer-name": "qualityMeasurementRetentionPeriod",
+              "purpose": "Time period for which qualityMeasurement records are kept, before they are deleted.",
+              "unit": "days",
+              "minimum": 1,
+              "maximum": 30
+            },
+            "integer-profile-configuration": {
+              "integer-value": 7
+            }
+          }
+        },
         {
           "uuid": "mwdi-1-3-0-string-p-000",
           "profile-name": "string-profile-1-0:PROFILE_NAME_TYPE_STRING_PROFILE",

spec/MicroWaveDeviceInventory+profileInstances.yaml

@@ -211,6 +211,17 @@ profile-instances:
     configuration:
       integer-value: 1
 
+  - profile-name: 'IntegerProfile'
+    uuid: 'mwdi-1-3-0-integer-p-007'
+    capability:
+      integer-name: 'qualityMeasurementRetentionPeriod'
+      purpose: 'Time period for which qualityMeasurement records are kept, before they are deleted.'
+      unit: 'days'
+      minimum: 1
+      maximum: 30
+    configuration:
+      integer-value: 7
+
   - profile-name: 'StringProfile'
     uuid: 'mwdi-1-3-0-string-p-000'
     capability:

spec/additionalDescription/CyclicCacheQualityMeasurementProcess.md

@@ -38,6 +38,7 @@ By selecting the device, whose cached ControlConstruct was updated the longest t
 Once a candidate devices has been identified, first its ControlConstruct is retrieved from the MWDI's cache. In the next step, the ControlConstruct is fetched from live (via MWDI live service).
 
 Both ControlConstructs are then compared to determine the differences. After the comparison and scoring has been finished, results are written to ElasticSearch.  
+Data is kept according to the retention period specified in integerProfile *qualityMeasurementRetentionPeriod*.
 
 There are no specific presciptions for how the comparison shall be implemented apart from the comparison logic to be applied. An appropriate approach shall be selected by the implementer.  
 *First analysis results showed that* deepdiff *could be a suitable candidate for comparing the ControlConstructs (large JSON structures), as it is claimed to be easy to use and to be handling deep comparisons really well (it can detect value changes, missing or new objects, type mismatches etc., and its output potentially can be easily connected with the intended scoring model).*