Hi!

I notice the insider transaction data from InsiderCow include P/S date and reporting date. As the P/S date is the actual buying or selling date of insider transactions. The reporting date is the date insiders report transaction data to the SEC. The Fidelity insider transaction data only includes the actual transaction date (which is the same as P/S date from InsiderCow). The reporting date is not shown/included within the Fidelity insider transaction data.

Is there a way to get the reporting date from Fidelity Insider Transaction data? I think the reporting date is important as it is the date that people starts to know about the fact.

Thank you for the help in advance.

Hi Alex,

I think the availability of the extra fields such as officer, relationship, proceeds, and psdate, is unique to the InsiderCow and soon to be released OpenInsider providers. Meanwhile it's easy to check if there's anything "hidden" by looping over the available fields of IList<FundamentalItem> FundamentalDataItems. See this code example.

Hi! Eugene,

The Fidelity Insider Transaction data does not have the reporting date as I have loop through it by using the following code...

CODE:
Please log in to see this code.

I have checked out the OpenInsider provider and it looks promising. It has more detailed information about insider transaction than Fidelity's one and it is being updated faster than Fidelity's one as well. Few questions that I have in mind regarding about this new data provider like: 1. Any page viewing/data download limit. 2. Any fee involved. I have contacted this provider and hopefully, I will hear back from them and will share the answers on the forum once I hear back from them.

Regarding about data download limit, I have an idea:

1. Now the data will be download if there is a change, than the "whole" data (per symbol) will be downloaded to replace the old data.
2. Is it possible to design the download as accumulated type of download? Once having a base "data", if there is a data change (extra/new data), only the new/extra data will be downloaded.

This way, one can build up a base data by downloading some data each time (for example symbols starts from A to E, than from F to H...) to avoid the daily data download limit. Once the base data is there, any extra/new data will be downloaded (accumulative way) when needed. Thus to avoid the daily data download limit. I do not know the detailed programming logic behind the existing data download method and it might be difficult to change to the accumulated type of download. So I am just asking the possibility here...

Thank you, Eugene and enjoy the weekend.


Alex

QUOTE:
I have contacted this provider and hopefully, I will hear back from them and will share the answers on the forum once I hear back from them.

Please share your findings once you have their reply. I haven't encountered anything re: fee and/or limit on the website.

QUOTE:
1. Now the data will be download if there is a change, than the "whole" data (per symbol) will be downloaded to replace the old data.
2. Is it possible to design the download as accumulated type of download? Once having a base "data", if there is a data change (extra/new data), only the new/extra data will be downloaded.

1 - All MS123 fundamental providers always refresh accumulated fundamental (news, economic etc.) data on update.
2 - No as kludges like that are proven to introduce more problems. For example, such was the ability to specify starting date when creating Yahoo! DataSets. Even if we had such intention, we usually deal with web-based fundamental sources (as opposed to a 'formal' API) which do not necessarily have a way to specify starting date.

It's much easier to avoid the daily download limit if you simply build your base data by updating the data in "Update DataSet" mode: first one large DataSet, then another etc.

Good suggestion about using the "Update DataSet" mode... Thanks!

I have investigated more into how InsiderCow data being downloaded/updated.

Apparently, when download the InsiderCow dataset, WLP will download the whole dataset (no accumulation and no detection on change of data...) and will go ahead to replace whatever on local drive. Even when InsiderCow server stops the data download due to daily data download limit, WLP will still get the "empty" files to replace the local files.

Is it possible to change this download logic to both detect file change and to download only extra/new and changed data? This way, we can use "Update DataSet" mode to "bypass" daily download limit.

With current InsiderCow download method (whole dataset download regardless about anything), one can easily run over the daily download limit. I am just asking if it is easy to re-program to make this improvement. I certainly hope it is easy and can be done.

Meanwhile, I will be researching the IP randomization solution suggested by Eugene in order to solve this... : )

And, of course, I am looking forward to the release of OpenInsider Data Provider. As I have done some research and believe it to be a good well-rounded data provider for insider transactions...

QUOTE:
Apparently, when download the InsiderCow dataset, WLP will download the whole dataset (no accumulation and no detection on change of data...) and will go ahead to replace whatever on local drive.

Yes, this is by design.

QUOTE:
Is it possible to change this download logic to both detect file change and to download only extra/new and changed data?

No. Like I already said, it's not a normal API we're programming against. It's a web page. Hitting it for parsing means downloading it.

QUOTE:
Meanwhile, I will be researching the IP randomization solution suggested by Eugene in order to solve this... : )

Hopefully, OpenInsider doesn't have this limitation.

Thank you, Eugene...

I have contacted OpenInsider by using their website contact form twice and have not heard back from them. Meanwhile, I am waiting for the OpenInsider extension to become available in July and will surely try it out to see if there is any download limitation.

Alex,
The OpenInsider provider has just been released:

Check this out

Eugene,

Great and thanks!

I am going to write more code into my existing strategy to accommodate the OpenInsider's insider transaction data. And, of course, I will keep "ALL" my fingers crossed and hope for there is no data download limitation. ; )