Hello, thanks for your time. After reading FAQ and the first blog post, realize I rushed ahead and posted lol. My bad. Will start there before using user forums!
I’m very new to knime but already digging in deep and I hope this is a simple question. I dig the forum, found answer to my core question immediately.
Couple questions, knime workflow to scrape LinkedIn Job data attached below, and some brainstorming.
Today, I was lucky to have a KNIME data scientist chat w/ me about KNIME on LinkedIn & I had a question about batch scripting.
She sent me to the community, glad she did, answered my question by typing a title! Nice work
So here goes, nodes needing to be reset in the UI, to “restart” a create date time, VS leaving it cached (although I’m a big fan of every tool auto caching)…
Saving the file with things reset cleared all this up, silly user error lol.
answers that too.
Thinking too far ahead… So, I can use KNIME to make a batch script creator, each knime file has evidence of the need to reset, and that could be automated from the file code, which could automatically funnel to building the batch schedule too…(assuming based on limited experience) which would enable me to automate build schedules based on conditions. so rad…
I’m wondering if anyone is doing any - Voice to text - and calling the script/macro?
Sorry I feel like im all over the place, not enough coffee, sleep, and having too much fun playing in knime.
Started last week and still can’t find the end of the tunnel. Wish i started using knime sooner. Been getting all my college mates excited about it because we all had to deal with SAP BOBJ data services collectively and we all understand the life of living within advanced etl products.
Thanks for the input, comments, links to your blogs - im eager to learn…
And I’m excited to start writing about the product, this is the first time I feel a company is trying to un-democratize solutions & I’m a big fan.
CANADA_Analytics_v1.001.knwf (141.5 KB)
Attached my first workflow, it’s is a simple api/web scrape that hits LinkedIn job data with some pretty decent success. You can swap out the data/keyword and fire away. Robots.txt and LinkedIn says it’s OK as long as you’re not selling the data or hosting it privately for profit. ENJOY