Bug #13300
closed
- Status changed from New to In Progress
The issue has been resolved.
In total, I've updated 119 GRSF stock records.
Since some of them have been approved, I've updated the corresponding ones in GRSF Public VRE.
The list of stocks that were updated is attached.
With many thanks, appreciated.
I checked the above example and it is fixed. I am going to submit the list of updates to RAM for a further check but I assume this issue is over.
My concern is to understand if this has been fixed manually for this specific occasion or if it has been a fix which will prevent similar errors in the next data harvest.
I noticed that in the KB we had two values (with different precision each one).
Since we haven't updated the GRSF KB for a long time, I guess that these values were added there by mistake.
I've checked and ensured that no duplicates are added during the construction or refreshing of the GRSF KB.
Also available in: Atom
PDF