Port aktivitetsbanken-crawler to Ruby

[mikaelsvensson]

Importing/syncronizing data from Aktivitetsbanken to the API is currently handled by the https://github.com/zegl/aktivitetsbanken-crawler application. It works as expected but it may be better to have this kind of functionality embedded into the API itself, or at least into the same project (source code project).

To do:

• Port the PHP code to Ruby code.
• Schedule the crawler to run, at least, once per week.

[mikaelsvensson]

Parsing HTML

• http://ruby.bastardsbook.com/chapters/html-parsing/
• http://railscasts.com/episodes/190-screen-scraping-with-nokogiri?view=asciicast
• https://railsgotchas.wordpress.com/2011/07/31/parsing-html-with-rails/

Scheduling:

• https://www.igvita.com/2007/03/29/scheduling-tasks-in-ruby-rails/
• http://backgroundrb.rubyforge.org/
• http://www.intridea.com/blog/2009/2/13/dead-simple-task-scheduling-in-rails
• http://stackoverflow.com/questions/7030975/dynamic-job-scheduling-in-rails

[mikaelsvensson]

The activity descriptions should be saved using Markdown. See http://daringfireball.net/projects/markdown/basics.

[zegl]

@mikaelsvensson I don't see why a port from PHP to Ruby would be necessary before the crawler could be a part of this project? The simplest solution would be to have the crawlers ownership migrated to the devscoutsweden-group and then include the repo with a sub-repository for easier deployment. Only one small thing needs to be fixed in the crawler ( zegl/aktivitetsbanken-crawler#5 ), and then everything should be ready to go.

[mikaelsvensson]

@zegl: Sorry, I should have explained myself better: By porting it to Ruby, thus limiting the number of programming languages involved in the overall solution, I think it will be easier to maintain the API as a whole. The same can be said for https://github.com/mikaelsvensson/scout-activities-analyzer, which should also be ported to Ruby using my own logic.

Also: Why am I writing in English!?