-
Notifications
You must be signed in to change notification settings - Fork 3
On import update modified values #309
Comments
I have committed the change for allowing the update of modified values. Point (1) in the list of changes above. |
I'm adding more detailed requirements about (2) - deleting dataseries values, per a discussion with @cjhendrix:
Caveat: One solution could be to:
@cjhendrix @seustachi we should discuss how we proceed about this issue |
Thanks for documenting this, Alex. I'll add it to the CPS planning doc. As for the caveat, I have a couple of questions:
|
It doesn't sound like an enormous effort. The model should be change to have this new status in the unique key as well. |
Then I suggest we build it to avoid gaps in data availability, either as Alex suggested or some other approach. |
I don't think it's a huge effort, I'd estimate like 1 day. On the plus side, the solution suggested above, would solve another problem that we have: during import (which takes some time in our case) someone accessing the API might get incomplete data, and the result could also get cached.
|
Sounds like the plan is clear then. Lets implement a solution like the one you have described that avoid any gaps in data availability. |
@alexandru-m-g @cjhendrix is this done ? or to roll to next sprint ? |
There are still some tasks that were not done in this ticket:
|
Right now we are only importing new indicator values, we are not updating values which were modified since the last import.
CHANGES:
This is related to #278
The text was updated successfully, but these errors were encountered: