Yahoo! Data for Citigroup is erroneous (again)
Author: Cone
Creation Date: 11/10/2013 6:21 PM
profile picture

Cone

#1
Careful out there. Yahoo! Finance seems to have lost the price history for C, and the last 4 days of updates do not reflect Citigroup trading.

Don't try to refresh the data, it's not there. Use a backup provider.
profile picture

Cone

#2
Another option is to correct the last 4 bars in the Yahoo! data from other sources. This is available in the attached result. Unzip and replace the C.WL file at C:\Users\[Windows Login]\AppData\Roaming\Fidelity Investments\WealthLabDev\1.0.0.0\Data\YahooStaticProvider\Daily\C\

For the next days (until the data at Y! are fixed), I'll try to remember to post the correction here and you can apply it yourself
profile picture

Cone

#3
It's not easy to get to the place to alert Yahoo! Finance of data problems, but I finally got a page with this info:

Reporting a data problem to Yahoo
Learn how to report data problems on Yahoo Finance to Yahoo and how to get help with data related questions, including:
. Incorrect data
. Delayed data updates
. Missing data

To report a data problem to Yahoo and get support from Yahoo staff and the community:
. Post a question in the Yahoo Finance product category of Yahoo Answers.


To report a data problem to Yahoo:
.Report a problem directly to Yahoo via Yahoo Finance Feedback.
-Note: Yahoo does not provide support via this method.
profile picture

Eugene

#4
Looks like that Yahoo! has heard you Robert. It's all right with C today for me.
profile picture

Cone

#5
Yup, the data are restored. :)
profile picture

ReneW

#6
The Citi problem does persist for me.

Once I have got 45 bars-- reload symbol -- 9340 bars and the last 5 bars wrong.

I repeat the step - I get 45 bars.
No solution so far.

Rene

profile picture

Eugene

#7
As I know that you were among those who experienced issues with Yahoo data loss last year, first thing required is to update the provider to its latest version 2014.01 where the problem is fixed (actually, since v2013.11). Then, using the Data Tool, remove all erroneous data. Finally, update the DataSet:

profile picture

Cone

#8
In this case, I'd go a step further than just using the Data Tool. Yahoo! seems to have really cleaned up the data with that URL change. I recommend that everyone completely refresh your Yahoo! data using the updated provider.
profile picture

ReneW

#9
Hi,


First: Where do I find the mentioned Data Tool ?
In my case its hidden somehow. (Sorry... )


To the Citigroup:

Its really vexing:

start WL

Single symbol reload C: - okay accidentally

Update data for selected providers (Yahoo) : C is destroyed, contains 46 bars... and no way to repair / single symbol reload does work, but delivers 46 bars only

I have a correct backup Citi file (up to Jan9) from a different computer.... I own more licenses... but basically its the same procedure with
each computer ... and only Citi seems to be affected.

After a WL shutdown, manually delete of C.WL , WL restart and single symbol reload, update dataset pricing
its ok (for the moment).


I am clueless here... if required, I could open a ticket.



Rene
profile picture

ReneW

#10
Follow Up:


1.) WL has correct Citi - Data: Citi Ok.jpg

2.) update dataset pricing (Yahoo) - 9341 bars with wrong data -> attachment Citi Error 9341.jpg

3.) reload symbol C - update dataset (Yahoo) - > 46 bars error -> attechment Citi Error 46.jpg

and no way out..... error remains C has only 46 bars

I could do thousand times symbol reload for C and update dataset pricing

4.) WL shutdown

5.) manually delete C.WL in data directory YahooStatic....\Daily\C

6.) WL restart - no data for C

7.) update dataset pricing C okay ... back to step 1

?

Sorry, Rene

Update: On a second machine, initially , the error did not occur.
But then , after updating the third dataset - Citi Error 9341 happened... again.
And then Citi Error 46....
The difference here is, that I wont get the correct data ... even after
restart the 46 bars error remains .... that means, backup data back.
If required, I could upload the defective 46-bar C.WL file, 2K size....

profile picture

Eugene

#11
I found that the bug wasn't completely eliminated, so under a particular scenario it's possible to get 46 bars (in case you wonder why: this is because your DataSet's starting date was Nov 1, 2013). I'm looking into the problem.

Try the following:

1. Create a new DataSet with only C.
2. Close WL and delete the C.WL file.
3. Restart WL and update this newly created DataSet. It should work this time.

Therefore I recommend recreating all your old DataSets (i.e. created in versions before v2013.11) from scratch. They will be free from the "C bug". Sorry for the inconvenience.
profile picture

ReneW

#12
Eugene, thank you for the fast response!

I followed your suggestion, created the completely new dataset CTest, one symbol, C .
Shutdown, deleting, C.WL, restarting, update dataset pricing CTest:

Updating DataSet CTest ...
Preparing requests ...
Requests are ready to go.
Updating Security Names for 1 symbols...
Security Names updated.
[0] C 46 bars 01.10.2014 46 bars added
Update completed (1.60 sec)
----------------

Okay, reload symbol, update dataset pricing:


Updating DataSet CTest ...
Preparing requests ...
Requests are ready to go.
Updating Security Names for 1 symbols...
Security Names updated.
[0] C 9341 bars 01.10.2014 9341 bars added
Update completed (1.622 sec)
----------------


Testing again:

Updating DataSet CTest ...
Preparing requests ...
Requests are ready to go.
Updating Security Names for 1 symbols...
Security Names updated.
[0] C 9341 bars 01.10.2014 0 bars added
Update completed (0.920 sec)
----------------

Data ok.


I really hope that the data will last, to me the result of "update
pricing for C " looks a little randomly.
I have been fighting the whole week with this, and today I had the time to look into it.
Sometimes all was looking fine and then the Citi data was missing again.
By the way, my datasets dont start at November 2013.

Hopefully you will be able to track the bug(?) down for more reliability. We all know, that bugs just happen
and Citi could be a little difficult because of this reverse split some years ago and one
day I found that even on yahoo finance's website the quote stood at 25 dollars (yahoo chart).


Rene


profile picture

Eugene

#13
Rene,

I was able to nail down the bug. Fix is coming in v2014.02. Until then you know the workaround.
profile picture

Cone

#14
I've struggled with this one for the last couple days too. The new link used for downloading Y! data is returning a short erroneous set of data for Citi. The old link returns the old history, but without the split and dividends.

I'll send them a message about it, but Y! needs to corrects the issue.
profile picture

Cone

#15
This keeps going back and forth. Updates on Sunday and Monday pulled in good data, but today it's wrong again. If using Y! data, make sure to check it every day for the time being.
profile picture

ReneW

#16
Sometimes the correct data is delivered for C....

Is this now a bug within the Y! data provider , Yahoo itself or a
combination of both ?

I was wondering if a correction for the Y! provider could be issued
in the neartime, if possible.
Eugene's workaround does not work for me.... its a random issue with C.

By the way, NWSA data history is gone as well after the split months ago.


PS Update: Today is the first day in 2 weeks where Citi data was correctly
delivered at the first try - fingers crossed...
profile picture

Eugene

#17
Summary: Although there is (was) a minor bug in the provider (to be fixed in 2014.02 release), fixing it doesn't affect the end result. It has been determined that the corrupt data has been a problem at Yahoo, rooted in the data request link switch they made around 1/1/2014. Like Cone said above, the new download link is returning a short erroneous set of data for some symbols whereas the old link returns the old history w/o the fundamental items. Additionally, with CDNs and server farms that giant companies like Yahoo use one can hit a server with "good" data and the other moment with "bad" data.

Conclusion: You need to complain about C data to Yahoo directly. Meanwhile, please feel free to resort to one of the many existing data providers as a backup.
profile picture

Eugene

#18
The bug causing data corruption when updating has finally been fixed in the 2014.02 build just released. After the fix in 2013.11, a possibility of being affected still remained for old DataSets created in previous versions of the provider if user reloaded or manually wiped out a symbol from an old DataSet and tried to update it.

Note: this is NOT intended to be a fix for the "C" data problem! This is Yahoo's business.

Also, there's new feature: GetSessionOpen support.