Mercurial > gemma
comparison TODOs-historization_ng.md @ 4066:6bfe42f88638 historization_ng
Some thoughts on an extra SR constraint trigger to check for ref gauge..
| author | Sascha Wilde <wilde@intevation.de> |
|---|---|
| date | Wed, 24 Jul 2019 18:55:09 +0200 |
| parents | 39441cdc5021 |
| children |
comparison
equal
deleted
inserted
replaced
| 4055:98e2041c7ebf | 4066:6bfe42f88638 |
|---|---|
| 28 | 28 |
| 29 Cut end of validit _after_ accepting the new one. | 29 Cut end of validit _after_ accepting the new one. |
| 30 | 30 |
| 31 ## Sounding Results: | 31 ## Sounding Results: |
| 32 | 32 |
| 33 - Maybe add a constraint to check, that a ref gauge is available? | |
| 34 Maybe not neccessary as import isn't possible anyway, as the | |
| 35 reference gauge is needed for the import process... (So the | |
| 36 constraint would never catch anything, as no data could be produced | |
| 37 without ref gauge) Only upside: we would triger if there is an error | |
| 38 in the backend generating SR with invalid ref data. | |
| 33 - Check during upload that matching bottleneck and reference gauge | 39 - Check during upload that matching bottleneck and reference gauge |
| 34 data is available (and use ist correctly) | 40 data is available (and use ist correctly) |
| 35 - Use correct reference gauge for X-Cuts | 41 - Use correct reference gauge for X-Cuts |
| 36 - (Maybe later) use matching BN data for display | 42 - (Maybe later) use matching BN data for display |
| 37 | 43 |