What is the crowd's opinion of SelectorGadget?

From 3.5 billion comments

Very little. You should be able to learn the basics in a couple of afternoons.

​

Also, be sure to check out the selector gadget--it's super helpful/fast https://selectorgadget.com/

Two thoughts:

1. have you considered using JSON parsing using the REST sensor? Backend services tend to be more reliable than front end for parsing; granted it can all go belly up with any code change.
   1. e.g. Refreshing the PSN endpoint quickly shows that: https://status.playstation.com/data/statuses/region/SCEE.json returns a nice neat package for you to parse in a reliable format.
2. Not sure how you are identifying selectors, but I use SelectorGadget. It's a bookmarklet that you can click to include or excude items and it will present the selectors required.

That's called data mining, data extraction or web scraping.

You can get tons of free lancers for the job.

I can't say how hard or easy without seeing the website first.

9 out of 10 times you can easily do that with xpath locators and some cleanup, but this site seems to be dynamically generating the content, so it might be more complicated then I anticipate.

If you want to try it yourself, check https://selectorgadget.com/ and try going from there.

I like using selectorgadget to narrow down css selectors. Just click on what you want to select, it highlights things that seem related, and click again on anything you don’t want to remove it and identify the unique css for the remaining highlighted elements.

Several people have mentioned rest which is my R web scraping library of choice as well. To add to the conversation I want to also suggest using selector gadget. Selector gadget allows you to pull the tags off of html objects interactively which makes the task of web scraping far easier. Also, you may find rcurl useful for making http requests.

Good luck! Feel free to reach out with any questions. I have done quite a bit of web scraping and even taught a couple classes on the subject.