What is the recommended approach for doing aggregation data analysis on connections collections ranging from about ten up to a few thousand? Since on one hand the API terms of use specify that we cannot save any data other than the member ID, and on the other hand we are throttled from pulling too much data at a time, is there a way to do any sort of aggregation data analysis?
Thanks!
- Log in to post comments
Greetings Matthew:
Thanks so much for asking - unfortunately you have deduced that we do not support this use case. Both the throttle and the TOS statement is intended not to let you know that we do not want you doing this. I can understand why it is interesting to do this but we do not support it.
Thanks
Steve