Good morning, community! Are you ready for a new Just KNIME It! challenge?
This time we are going to dive into the world of TV shows (Rick & Morty, more specifically) and sharpen our JSON and API skills along the way.
Here is the challenge. Let’s use this thread to post our solutions to it, which should be uploaded to your public KNIME Hub spaces with tag JKISeason4-4 .
Need help with tags? To add tag JKISeason4-4 to your workflow, go to the description panel in KNIME Analytics Platform, click the pencil to edit it, and you will see the option for adding tags right there. Let us know if you have any problems!
I think one of the strongest point of KNIME is how easy it is to get data directly from the internet — whether it’s scraping a website or calling an API, it’s all visual and super flexible. And this challenge was a great example of that!
Built a recursive loop to crawl all pages. Learned loads about REST calls, JSON Path, and loop logic along the way. Huge thanks to the KNIME community for the support/tips that kept me on track.
Would love any feedback or suggestions to make the workflow even smoother!
This week’s challenge had me diving into the Rick and Morty universe… which, I have to admit, I’ve never actually watched before!
So, just to make sure I wasn’t cataloging a bunch of total strangers, I added images of each character to my solution — visual data enrichment, KNIME-style!
Now I finally know what a Pickle Rick looks like… and yes, it was worth it.
Happy KNIME’ing and see you in the next multiverse loop!
Overall, the 2 first objectives are in the first 2 parts of the workflows. An extra part is included in the third green box.
Beginner-friendly objective 1: get the number of pages that will be returned by the API. I then used a Bootstrap sampling to generate 1 row per page, followed by a GET Request getting all the information for each page.
Intermediate-friendly objective 1: this part include the recursive loop allowing to follow each page link to next page. It ends when the next page field is empty.
I have added an extra part to include a data app, allowing the user to do some filtering. Also, the workflow is ready to include episodes information - data available but not shown in the Data App.
The Data App, allowing some filtering on the data available, includes also the more detailed information about the characters and the image of this character.
Wow, adding character images? That’s pure genius!
I completely missed that dimension of the API — what a brilliant way to bring the dataset to life.
Definitely stealing that idea for my next interdimensional analysis
Love how KNIME lets us go from JSON to fully visual insights in just a few nodes!
Hats off, sir — that was sharp!
Glad you liked the character image idea, sometimes data just needs a little personality to shine!
To be honest, I added the images because… I had no idea what cartoon we were analyzing!
So I figured, if I can’t understand the story, at least I can make the dataset look cool!
Wow, that was a challenge!! Mostly because I have never used the recursive loop nodes before, and it looks like it may be a big part of my workflows going forward.
Also big shoutout to @berti093! I don’t have much experience with APIs or loops, but your workflow was very easy to follow. My submission is pretty much the same, but I was able to bring in images for the characters as well (this made it take a lot longer to go through the loop).