Enter QA environment with basic search/browse functionality

Configure Solr
Add IndexService library
Index and delete sample data with rake task
Generate catalog controller to customize blacklight
Show search results in catalog home view
Basic keyword search
Refine search with facets
Show basic metadata for single record

To test in your browser:  Follow the new README instructions to configure and start the dummy application, and index sample data to Solr.  You may need to visit [http://127.0.0.1:8983/solr/#/~cores/blacklight-core](http://127.0.0.1:8983/solr/#/~cores/blacklight-core) and click `Reload` for the sample data to index. Go to [http://localhost:3000/catalog](http://localhost:3000/catalog) (you will see the same page if you go to http://localhost:3000 because of the current route configuration).  You should see your sample record.  You should be able to search and refine your search with facets.  You should also be able to view some basic metadata for a single record if you click on the record id.  

There are also two unit test you can run with `bundle exec rake ci`.

Because we are likely moving away from Solr, I focused on getting Solr working without necessarily employing the most elegant solutions.  

In `schema.xml`, everything above line 476 `<fields>` is standard.  Everything below is ours, with the exception of `dynamic field definitions`, which is also standard.
What happens is that after you've indexed this into Solr, when you try to do a GET request on this data, Solr barfs at the special characters, ie. `@` and `:`, and you get a big error message.  If we stick with Solr, we could possibly figure out how to escape all the necessary special characters, but since we might be switching to ElasticSearch anyway, I just employed this quick and dirty method.  Also, I think it's worth considering the tradeoff between having really accurate/descriptive field names in the search index, and simplifying field names to make them more usable.  Does that answer your question?  I'm not sure what you mean by "safe".