Implementation of Linking between SMS an TSM's in a new Configurations tab
As a user i want to configure the linking between SMS Meausred Quantities an TSM Datastreams in a new Configuration tab "data link". The SMS backend propagate new Endpoints for available TSM instances(normally one maybe initial by env-var) and for get and push request to new linking API (see related backend issue). The TSM instances have implmented the Endpoints(datasources, things, datastreams: https://codebase.helmholtz.cloud/hub-terra/tsmdl-time-series-management-decoupling-layer/tsmdl-api. The user should have something like a table based configuration tool in this tab.
| Device(seriesNumber)- Measured Quantity | datasource | thing | datastream |
|---|---|---|---|
| Device 1(0815)-Temp1 | UFZ-CRNS-DB | CRNS-01 | Channel 05 |
| Device 1(12234)-TempN | UFZ-CRNS-DB | CRNS-01 | Channel 04 |
| Device N - MQ M | ... | ... | ... |
The user should be assisted in this way. In case no manual linking is configured. The default Datasource, thing, datastream linking should be initial be filled by:
- either historical linking information based to this measured quantitie (earlier location event or other configuration)
- or after the user has choosen one entity of datasource - it should be propagated to all measured qunaitites by default- same to things. Just the datastream linking has to be choosen manually-without support (just if soome historical informations are available f.e MQ-tempsens is always mapped to column "temprature" https://confluence.digitalearth-hgf.de/pages/viewpage.action?pageId=48234876 https://codebase.helmholtz.cloud/nils.brinckmann/sms-logger-configs-and-sync-to-sta
Description and Key-Value pairs(N2H) based on TSMDL-API should be shown to user as hover text list key: value
Before start a meeting is needed to discuss the best ui/UX approach.
Relates to: backend#164 (closed) Have a look to the UI/UX ideas: