run specs in random order
first-pass importing of openings...

... via background job

NOTES:
* uses bulk insert / updating via upsert.gem
* uses rest-client to request "internal web service" jobs.json
* uses resque.gem for backgrounding import-requests
* importer imports from most-recent-record-posted timestamp-to-present each run
* must export OPENINGS_URI=http://some.domain/jobs for specs to work
* a running json-server service is not required to run specs
* run rake db:seed db:seed:openings to populate DB

TODO:
* spec for db:seed:openings task
* consider cleaning up conversions during import
* consider adding additional edge-cases in specs
* implement keyword functionality
* everything front-end

NOTABLE GOTCHAS SOLVED:
* table_name_prefix via module not set in namespaced classes
* users.name must be unique for poster to poster_id conversion during import
* users.email factory was not unique
* must use :truncation strategy or upsert creates transaction errors
spec for db:seed:openings
Merge branch 'feature/seed_data' into next
fix an intermittent bug due function-overwriting
BUG: importing openings from unknown users-by-name...

... have no account in which to be associated, therefore,
have no user_id, therefore the opening is invalid.

Workaround: create a placeholder account 'Web Service' and
assign such openings to this account.
BUG: importing openings from unknown users-by-name...

... have no account in which to be associated, therefore,
have no user_id, therefore the opening is invalid.

Workaround: create a placeholder account 'Web Service' and
assign such openings to this account.
add serializer, controller and basic view layers

NOTES:
* responds to HTML, XML and JSON requests
* only VIPs and admins can create, update and destroy openings

TODO:
verify bits for serializers
Merge branch 'feature/opening_posting_bits' into next

Conflicts:
	spec/jobs/outsider/openings_importer_job_spec.rb
acts-as-taggable-on integration...

... first pass
BUG: Outsider::Openings#keywords functionality...

... changed with the integration of acts-as-taggable-on.gem

Workaround: keywords_as_string() yields a sorted CSV of keywords
Merge branch 'feature/keywords' into next
cleanup homepage and location
fail: re-enable visitors path
log requests in the background