Hi! We've renamed ScraperWiki.
The product is now QuickCode and the company is The Sensible Code Company.

Archive by Author

Libraries that are ready and waiting

One of the nice things about ScraperWiki is that it gives you access to all sorts of useful data manipulation libraries, all from your web browser. Everything from PDF extractors, to statistical analysis. We’ve now documented what is available – in Python, in Ruby and in PHP. Here’s a screenshot of a few for a […]

Who changed my scraper? History upgrade

We’ve upgraded the history window, to make it easier to see who’s changed your scraper, what they changed, and when it broke. This is particularly useful if you’ve just received an email alert. You can get to it from the “History” tab at the top right of each scraper or view’s page. Here’s an example from the Work4MP […]

Job advert: Product / UX lover

ScraperWiki is a Silicon Valley style startup, but based in the UK. We’re changing the world of open data, and how programming is done together on the Internet. We’re looking for a web product designer who is… Able to make design decisions to launch features by themselves. Capable of writing CSS and HTML, and some […]

Ruby screen scraping tutorials

Mark Chapman has been busy translating our Python web scraping tutorials into Ruby. They now cover three tutorials on how to write basic screen scrapers, plus extra ones on using .ASPX pages, Excel files and CSV files. We’ve also installed some extra Ruby modules – spreadsheet and FastCSV – to make them possible. These Ruby scraping […]

Job advert: Web designer/programmer

Care about oil spills, newspapers or lost cats? ScraperWiki is a Silicon Valley style startup, but in the North West of England, in Liverpool. We’re changing the world of open data, and how programming is done together on the Internet. We’re looking for a web designer/programmer who is… Capable of writing standards compliant CSS and […]

Get the source to ScraperWiki

We’ve always intended that ScraperWiki itself should be open source – philosophically it doesn’t make sense for a collaborative code wiki for working with public datasets not to be. More practically, letting anyone see our developer tools means you can also access our bug tracker, so you know what we’re working on and what issues […]

We're hiring!