RubyGems - blacklight - Versions diffs - 5.9.4 → 5.10.0 - Mend

blacklight 5.9.4 → 5.10.0

Files changed (137) hide show

checksums.yaml +4 -4
data/Gemfile +1 -1
data/VERSION +1 -1
data/app/assets/stylesheets/blacklight/_facets.scss +11 -10
data/app/helpers/blacklight/blacklight_helper_behavior.rb +14 -14
data/app/helpers/blacklight/configuration_helper_behavior.rb +16 -10
data/app/helpers/blacklight/facets_helper_behavior.rb +15 -14
data/app/helpers/blacklight/url_helper_behavior.rb +1 -1
data/app/models/bookmark.rb +1 -4
data/app/models/search.rb +3 -6
data/app/views/catalog/_facet_layout.html.erb +2 -2
data/app/views/catalog/_facet_limit.html.erb +5 -3
data/app/views/catalog/_facet_pivot.html.erb +4 -4
data/app/views/catalog/_home_text.html.erb +8 -48
data/app/views/catalog/_index_default.html.erb +3 -3
data/app/views/catalog/_show_default.html.erb +3 -3
data/app/views/catalog/_sms_form.html.erb +1 -1
data/app/views/catalog/facet.html.erb +1 -1
data/blacklight.gemspec +1 -1
data/config/jetty.yml +0 -3
data/config/locales/blacklight.de.yml +2 -0
data/config/locales/blacklight.en.yml +2 -0
data/config/locales/blacklight.es.yml +2 -0
data/config/locales/blacklight.fr.yml +2 -0
data/config/locales/blacklight.pt-BR.yml +2 -0
data/lib/blacklight.rb +70 -26
data/lib/blacklight/abstract_repository.rb +29 -0
data/lib/blacklight/base.rb +7 -7
data/lib/blacklight/bookmarks.rb +5 -5
data/lib/blacklight/catalog.rb +34 -19
data/lib/blacklight/catalog/search_context.rb +1 -1
data/lib/blacklight/configuration.rb +112 -46
data/lib/blacklight/configuration/facet_field.rb +9 -7
data/lib/blacklight/configuration/field.rb +27 -0
data/lib/blacklight/configuration/fields.rb +25 -20
data/lib/blacklight/configuration/search_field.rb +6 -8
data/lib/blacklight/configuration/solr_field.rb +3 -18
data/lib/blacklight/configuration/sort_field.rb +6 -7
data/lib/blacklight/document.rb +156 -0
data/lib/blacklight/document/dublin_core.rb +41 -0
data/lib/blacklight/document/email.rb +16 -0
data/lib/blacklight/document/export.rb +107 -0
data/lib/blacklight/document/extensions.rb +56 -0
data/lib/blacklight/document/schema_org.rb +7 -0
data/lib/blacklight/document/semantic_fields.rb +51 -0
data/lib/blacklight/document/sms.rb +14 -0
data/lib/blacklight/document_presenter.rb +3 -3
data/lib/blacklight/exceptions.rb +9 -2
data/lib/blacklight/facet.rb +21 -16
data/lib/blacklight/request_builders.rb +60 -284
data/lib/blacklight/routes.rb +1 -1
data/lib/blacklight/search_builder.rb +130 -0
data/lib/blacklight/search_helper.rb +316 -0
data/lib/blacklight/solr.rb +1 -0
data/lib/blacklight/solr/document.rb +4 -187
data/lib/blacklight/solr/document/dublin_core.rb +3 -37
data/lib/blacklight/solr/document/email.rb +4 -13
data/lib/blacklight/solr/document/export.rb +3 -103
data/lib/blacklight/solr/document/extensions.rb +4 -52
data/lib/blacklight/solr/document/more_like_this.rb +1 -1
data/lib/blacklight/solr/document/schema_org.rb +4 -4
data/lib/blacklight/solr/document/sms.rb +4 -11
data/lib/blacklight/solr/facet_paginator.rb +2 -2
data/lib/blacklight/solr/search_builder.rb +264 -0
data/lib/blacklight/solr_helper.rb +6 -261
data/lib/blacklight/solr_repository.rb +30 -24
data/lib/blacklight/solr_response.rb +3 -3
data/lib/blacklight/user.rb +1 -2
data/lib/blacklight/utils.rb +0 -23
data/lib/generators/blacklight/controller_generator.rb +38 -0
data/lib/generators/blacklight/document_generator.rb +20 -0
data/lib/generators/blacklight/install_generator.rb +38 -39
data/lib/generators/blacklight/models_generator.rb +2 -62
data/lib/generators/blacklight/templates/catalog_controller.rb +3 -4
data/lib/generators/blacklight/templates/config/{solr.yml → blacklight.yml} +3 -0
data/lib/generators/blacklight/templates/config/jetty.yml +0 -3
data/lib/generators/blacklight/templates/solr_document.rb +6 -6
data/lib/generators/blacklight/test_support_generator.rb +1 -6
data/lib/generators/blacklight/user_generator.rb +59 -0
data/lib/railties/blacklight.rake +16 -7
data/spec/controllers/catalog_controller_spec.rb +9 -15
data/spec/features/facets_spec.rb +8 -0
data/spec/helpers/configuration_helper_spec.rb +6 -13
data/spec/helpers/facets_helper_spec.rb +3 -2
data/spec/lib/blacklight/configuration_spec.rb +11 -38
data/spec/lib/blacklight/{solr/document → document}/dublin_core_spec.rb +4 -4
data/spec/lib/blacklight/{solr/document → document}/email_spec.rb +2 -2
data/spec/lib/blacklight/{solr/document → document}/sms_spec.rb +2 -2
data/spec/lib/blacklight/search_builder_spec.rb +145 -0
data/spec/lib/blacklight/search_helper_spec.rb +775 -0
data/spec/lib/blacklight/solr/document/more_like_this_spec.rb +1 -1
data/spec/lib/blacklight/solr/search_builder_spec.rb +561 -0
data/spec/lib/blacklight/solr_helper_spec.rb +5 -1291
data/spec/lib/blacklight/solr_repository_spec.rb +13 -13
data/spec/models/record_mailer_spec.rb +2 -2
data/spec/spec_helper.rb +1 -0
data/spec/test_app_templates/lib/generators/test_app_generator.rb +1 -1
data/spec/views/catalog/_constraints.html.erb_spec.rb +1 -1
data/spec/views/catalog/_paginate_compact.html.erb_spec.rb +2 -2
data/spec/views/catalog/index.atom.builder_spec.rb +1 -1
data/tasks/blacklight.rake +1 -1
data/template.demo.rb +1 -1
metadata +33 -45
data/doc/Adding-new-document-actions.md +0 -94
data/doc/Atom-Responses.md +0 -90
data/doc/Blacklight-Add-ons.md +0 -23
data/doc/Blacklight-configuration.md +0 -411
data/doc/Blacklight-on-Heroku.md +0 -100
data/doc/Blacklight-out-of-the-box.md +0 -47
data/doc/Bookmarks.md +0 -1
data/doc/Code4Lib-2014.md +0 -94
data/doc/Configuration---Facet-Fields.md +0 -130
data/doc/Configuration---Results-View.md +0 -224
data/doc/Configuration---Solr-fields.md +0 -106
data/doc/Configuring-and-Customizing-Blacklight.md +0 -257
data/doc/Configuring-rails-routes.md +0 -13
data/doc/Contributing-to-Blacklight.md +0 -43
data/doc/Examples.md +0 -120
data/doc/Extending-or-Modifying-Blacklight-Search-Behavior.md +0 -141
data/doc/Home.md +0 -100
data/doc/How-to-release-a-version.md +0 -45
data/doc/Indexing-your-data-into-solr.md +0 -36
data/doc/Internationalization.md +0 -32
data/doc/JSON-API.md +0 -83
data/doc/Pagination.md +0 -52
data/doc/Providing-your-own-view-templates.md +0 -69
data/doc/Quickstart.md +0 -153
data/doc/README_SOLR.md +0 -245
data/doc/Saved-Searches.md +0 -5
data/doc/Solr-Configuration.md +0 -154
data/doc/Sunspot-for-indexing.md +0 -46
data/doc/Support.md +0 -33
data/doc/Theming.md +0 -62
data/doc/Understanding-Rails-and-Blacklight.md +0 -75
data/doc/User-Authentication.md +0 -60
data/doc/_Sidebar.md +0 -9
data/doc/testing.md +0 -58

data/doc/Providing-your-own-view-templates.md DELETED Viewed

@@ -1,69 +0,0 @@
-# Customizing the User Interface
-## Layouts
-Blacklight provides a layout called "blacklight" that provides the basic scaffolding to make Blacklight operate correctly. If you replace it with your own layout, you may wish to preserve some key features of the provided layout:
-Call `content_for(:head)` somewhere in your HTML <head>:
-```erb
- <%= content_for(:head) %>
-```
-Render flash messages in the layout - none of the Blacklight-provided templates and partials are configured to do this for you.
-Provide an AJAX modal:
-```erb
-  <div id="ajax-modal" class="modal fade" tabindex="-1" role="dialog" aria-labelledby="modal menu" aria-hidden="true">
-    <div class="modal-dialog">
-      <div class="modal-content">
-      </div>
-    </div>
-  </div>
-```
-## Overriding Views (templates and partials)
-As a Rails Engine, you can easily override views in your app. You can see what views and partials are provided by looking in `[[./app/views|https://github.com/projectblacklight/blacklight/tree/master/app/views]]` inside the Blacklight source.
-Once you find the view you'd like to change, you should create a file with the same name and relative path in your own application (e.g. if you wanted to override [[./app/views/catalog/_show_partials/_default.html.erb|https://github.com/projectblacklight/blacklight/blob/master/app/views/catalog/_show_partials/_default.html.erb]] you would create ./app/views/catalog/_show_partials/_default.html.erb in your local application. Frequently, you will start by copying the existing Blacklight view and modifying it from there.
-It is generally recommended that you override as little as possible, in order to maximize your forward compatibility. Look to override either a small, focused partial template, or a helper method of partial template called from a larger template, so your application's version can call out to those same helpers or partial templates within blacklight core code.
-## Overriding the CatalogController
-Overriding the Blacklight `CatalogController` implementation is easy, and the skeleton of the `CatalogController` is generated into your application for you when you install Blacklight.
-See the [[Extending or Modifying Blacklight Search Behavior]] for tips and approaches to customizing the catalog.
-## Custom View Helpers
-(This is accurate for Blacklight 3.1.1 and subsequent. Before that, things were messier).
-One of the most common things you might need to do is create a view helper -- especially to override some Blacklight behavior implemented in it's own view helpers. The first step is looking at Blacklight source to determine what view helper method you want to override.
-Blacklight comes packaged with several view helper modules. There is a BlacklightHelper in (blacklight source) app/helpers/blacklight_helper.rb , and several others that correspond to specific controller. (Note, depending on version of Rails and configuration, all helpers may get loaded for every request, even ones that are named to correspond only to a particular other controller).
-If you simply created a local helper with the same name as a helper in Blacklight, that will end up preventing the Blacklight helper from being loaded at all though, which is not what you want to do to override.
-We've structured each Blacklight view helper module into two parts to make it easy to selectively over-ride methods. For instance, here's Blacklight's app/helpers/blacklight_helper.rb:
-```ruby
-module BlacklightHelper
-  include Blacklight::BlacklightHelperBehavior
-end
-```
-Now, the actual methods will be found in app/helpers/blacklight/blacklight_helper_behavior.rb instead.
-If you want to over-ride a helper method, copy the wrapper blacklight_helper into your local app, with the 'include' line, and now you can individually over-ride methods from BlacklightHelperBehavior, and the other methods you don't over-ride will still have their default implementation.
-YOUR `app/helpers/blacklight_helper.rb`
-```ruby
-module BlacklightHelper
-  include Blacklight::BlacklightHelperBehavior
-  def application_name
-    "Bestest University Search"
-  end
-end
-```

data/doc/Quickstart.md DELETED Viewed

@@ -1,153 +0,0 @@
-Blacklight is a Ruby on Rails Engine plugin, meaning it provides a small application that runs inside an existing Ruby on Rails project.
-This Quickstart will walk you through installing Blacklight and Solr, and indexing a sample set of records. If you want information about configuring Blacklight to use an existing Solr index with your data in it, see the [Developing Your Application](https://github.com/projectblacklight/blacklight/wiki#wiki-blacklight-configuration) section of the wiki.
-## Dependencies
-To get started with Blacklight, first [install Ruby](https://gorails.com/setup/#ruby) and [install Rails](https://gorails.com/setup/#rails), if you don't have it installed already. You'll need Ruby 1.9 or higher, and Rails 3.2 or higher.
-To run Solr, you'll also need Java installed.
-### Got Ruby?
-You should have Ruby 1.9 or greater installed.
-```console
-$ ruby --version
-  ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-darwin13.0]
-```
-### Got Rails?
-Blacklight works with Rails 3.2 and Rails 4.x, although we strongly encourage you to use Rails 4.
-```console
-$ rails --version
-  Rails 4.0.3
-```
-### Got Java?
-```console
-$ java -version
-java version "1.6.0_0"
-IcedTea6 1.3.1 (6b12-0ubuntu6.1) Runtime Environment (build 1.6.0_0-b12)
-OpenJDK Client VM (build 1.6.0_0-b12, mixed mode, sharing)
-```
-The output will vary, but you need to make sure you have version 1.6 or higher. If you don't have the required version, or if the java command is not found, download and install the latest version from Oracle at http://www.oracle.com/technetwork/java/javase/downloads/index.html. Make sure to install the JDK.
-## Creating a new application the easy way
-```console
-$ mkdir projects
-$ cd projects
-$ rails new search_app -m https://raw.github.com/projectblacklight/blacklight/master/template.demo.rb
-      create
-      create  README.rdoc
-      create  Rakefile
-      create  config.ru
-      create  .gitignore
-      create  Gemfile
-      create  app
-      create  app/assets/javascripts/application.js
-      create  app/assets/stylesheets/application.css
-      create  app/controllers/application_controller.rb
-      create  app/helpers/application_helper.rb
-      create  app/views/layouts/application.html.erb
-      create  app/assets/images/.keep
-      create  app/mailers/.keep
-      create  app/models/.keep
-      create  app/controllers/concerns/.keep
-.
-.
-.
-Your bundle is complete! Use `bundle show [gemname]` to see where a bundled
-gem is installed.
-$ cd search_app
-```
-### What Does the Easy Way Generator Do?
-When you run the Rails generator for a new application, you can pass in the name of a file of template commands to be run after the base generator runs. The template file above runs through steps 2-5 of the 'Hard Way' below.
-## Creating a new application the hard way
-1. Create a new, blank Rails application
-   ```console
-   $ rails new my_new_blacklightapp
-   $ cd my_new_blacklightapp
-    ...
-   ```
-2. Append these lines to your application's `Gemfile`
-    ```ruby
-    gem 'blacklight', ">= 5.3.0"
-    gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
-    ```
-    Especially if you are running on Linux, you may have to add `gem 'therubyracer'` to your gemfile, to get a Javascript runtime needed by the asset pipeline.
-    then, update the bundle
-    ```bash
-    $ bundle install
-    ```
-3. Install blacklight using Devise for user authentication:
-    ```bash
-    $ rails generate blacklight:install --devise --marc --jettywrapper
-    ```
-    Including `--devise` will also generate devise-based Users into your application. If you would prefer to integrate with an alternative user authentication provider, see the [[User Authentication]] documentation.
-   Including `--marc` will also generate `blacklight-marc` into your application, which adds library-specific functionality out-of-the-box.
-4. Run your database migrations to create Blacklight's database tables:
-    ```console
-    $ rake db:migrate
-    ```
-5. For the initial install of Blacklight you may need to download Jetty by running before starting it:
-    ```console
-    $ rake jetty:clean
-    ```
-## Easy or Hard: After creating your new application
-1.  Make sure your Solr server is running. If you installed the Blacklight using the `--jettywrapper` option, you can start the Jetty/Solr server using:
-    ```console
-    $ rake jetty:start
-    ```
-   You should be able to navigate to Solr at http://localhost:8983/solr/#/blacklight-core/query
-2. Index some data. You can index test the MARC records provided with Blacklight by running:
-    ```console
-    $ rake solr:marc:index_test_data
-    ```
-   Depending on the version of Solr you're using, you may see a warning that can be safely ignored:
-   ```console
-   Warning: Specifying binary request handling from a Solr Server that doesn't support it. Enable it in the solrconfig file for that server.
-   ```
-3. Start up your application
-    ```console
-    $ rails server
-    ```
-Visit the catalog at [[http://localhost:3000/catalog]].
-![Blacklight Home Page](https://f.cloud.github.com/assets/111218/2059077/5f10e090-8b95-11e3-9cac-72d8e0e5968e.png)
-You should see the Blacklight interface with 30 MARC records for testing. Additional MARC records are available from the [[blacklight-data|https://github.com/projectblacklight/blacklight-data]] repository. These can be ingested into Solr using SolrMarc,
-```console
-$ rake solr:marc:index MARC_FILE=(path to file)
-```
-See [[Configuring and Customizing Blacklight]] for information about how to customize the Blacklight user interface, search experience, and more.

data/doc/README_SOLR.md DELETED Viewed

@@ -1,245 +0,0 @@
-#Solr in Blacklight
-##Setting up Solr
-Blacklight uses Solr as its "search engine".
-More information about Solr is available at the Solr web site ( http://lucene.apache.org/solr/)
-There are three sections to this document:
-* Getting Solr
-* Configuring Solr
-  * schema.xml
-  * solrconfig.xml
-* SolrMARC
-### Getting Solr
-Blacklight distributes a pre-configured version of Solr (with the Jetty
-container) as [[blacklight-jetty|https://github.com/projectblacklight/blacklight-jetty/tags]].
-You can also use an existing Solr index (with some minor modifications).
-If you want to start from a new version of Solr, follow the directions from the [[Solr tutorial|http://lucene.apache.org/solr/tutorial.html]]
-You should now have a usable copy of Solr.
-### Configuring Solr
-####Solr Schema.xml
-Between the `schema.xml` and `solrconfig.xml` you can change and tune the search behavior following directions from the [[Solr wiki|http://wiki.apache.org/solr/]]. Solr comes with example schema and solrconfig files, which you can use as a starting point for configuring your local Solr application.
-Blacklight expects a uniqueKey field within your Solr index,
-traditionally called `id`. The name of the unique key field can be
-configured in your application's `SolrDocument`.
-##### Blacklight community "best practices"
-Solr uses a schema.xml file to define document fields (among other things). These fields store data for searching and for result display. You can find the example/solr/conf/schema.xml file in the Solr distribution you just downloaded and uncompressed.
-Documentation about the Solr schema.xml file is available at (http://wiki.apache.org/solr/SchemaXml).
-  The default schema.xml file comes with some preset fields made to work with
-  the example data. If you don't already have a schema.xml setup, we
-  recommend using a simplified "fields" section like this:
-```xml
-	<fields>
-		<field name="id" type="string" indexed="true" stored="true" required="true" />
-		<field name="text" type="text" indexed="true" stored="false" multiValued="true"/>
-		<field name="timestamp" type="date" indexed="true" stored="true" default="NOW" multiValued="false"/>
-		<field name="spell" type="textSpell" indexed="true" stored="true" multiValued="true"/>
-		<dynamicField name="*_i"  type="sint"    indexed="true"  stored="true"/>
-		<dynamicField name="*_s"  type="string"  indexed="true"  stored="true" multiValued="true"/>
-		<dynamicField name="*_l"  type="slong"   indexed="true"  stored="true"/>
-		<dynamicField name="*_t"  type="text"    indexed="true"  stored="true" multiValued="true"/>
-		<dynamicField name="*_b"  type="boolean" indexed="true"  stored="true"/>
-		<dynamicField name="*_f"  type="sfloat"  indexed="true"  stored="true"/>
-		<dynamicField name="*_d"  type="sdouble" indexed="true"  stored="true"/>
-		<dynamicField name="*_dt" type="date"    indexed="true"  stored="true"/>
-		<dynamicField name="random*" type="random" />
-		<dynamicField name="*_facet" type="string" indexed="true" stored="true" multiValued="true" />
-		<dynamicField name="*_display" type="string" indexed="false" stored="true" />
-	</fields>
-```
-  Additionally, replace all of the tags after the "fields" section, and before
-  the `</schema>` tag with this:
-```xml
-	<uniqueKey>id</uniqueKey>
-	<defaultSearchField>text</defaultSearchField>
-	<solrQueryParser defaultOperator="OR"/>
-	<copyField source="*_facet" dest="text"/>
-```
-  Now you have a basic schema.xml file ready. Other fields can be specified, including a primary document title (`title_display`) and format (`format`), but these are easily configured in your application's `CatalogController`.
-  Fields that are "indexed" are searchable.
-  Fields that are "stored" are can be viewed/displayed from the Solr search
-  results.
-  The fields with asterisks ('*') in their names are "dynamic" fields. These
-  allow you to create arbitrary tags at index time.
-  The *_facet field can be used for creating your facets. When you index,
-  simply define a field with _facet on the end:
-    category_facet
-  The *_display field can be used for storing text that doesn't need to be
-  indexed. An example would be the raw MARC for a record's detail view:
-    raw_marc_display
-  For text that will be queried (and possibly displayed), use the *_t type
-  field for tokenized text (text broken into pieces/words) or the *_s type
-  for queries that should exactly match the field contents:
-    description_t
-    url_s
-  The Blacklight application is generic enough to work with any Solr schema, but to
-  manipulate the search results and single record displays, you'll need to know the
-  stored fields in your indexed documents.
-  For more information, refer to the Solr documentation:
-    http://wiki.apache.org/solr/SchemaXml
-#####solrconfig.xml
-Solr uses the solrconfig.xml file to define searching configurations, set cache options, etc.
-You can find the examples/solr/conf/solrconfig.xml in the distribution directory you just uncompressed.
-Documentation about the solrconfig.xml file is available at (http://wiki.apache.org/solr/SolrConfigXml).
-Blacklight expects two request handlers to be defined -- one to handle
-general search requests and one to handle single-document lookup. The
-names of these request handlers are configurable, but are called
-"search" and "document" respectively, out of the box.
-#####Solr Search Request Handlers
-  When Blacklight does a collection search, it sends a request to a Solr
-  request handler named "search". The most important settings in this handler
-  definition are the "fl" param (field list) and the facet params.
-  The "fl" param specifies which fields are returned in a Solr response.
-  The facet related params set up the faceting mechanism.
-  Find out more about the basic params:
-     http://wiki.apache.org/solr/DisMaxRequestHandler
-  Find out more about the faceting params:
-    http://wiki.apache.org/solr/SimpleFacetParameters
-######How the "fl" param works in Blacklight's request handlers
-  Blacklight comes with a set of "default" views for rendering each document
-  in a search results page. This view simply loops through all of the fields
-  returned in each document in the Solr response. The "fl" (field list) param
-  tells Solr which fields to include in the documents in the response ...
-  and these are the fields rendered in the Blacklight default views.
-  Thus, the fields you want rendered must be specified in "fl".  Note that
-  only "stored" fields will be available;  if you want a field to be rendered
-  in the result, it must be "stored" per the field definition in schema.xml.
-  The "fl" parameter definition in the "search" handler looks like this:
-  ```xml
-    <str name="fl">id,score,author_display,(....lots of other fields)</str>
-  ```
-  You may also use an asterisk plus "score":
-  ```xml
-    <str name="fl">*,score</str>
-  ```
-######How the facet params work in Blacklight's request handlers
-  In the search results view, Blacklight will look into the Solr response for
-  facets. If you specify any facet.field params in your "search" handler,
-  they will automatically get displayed in the facets list:
-  ```xml
-    <str name="facet.field">format</str>
-    <str name="facet.field">language_facet</str>
-  ```
-#####Blacklight's "search" request handler: for search results
-  When Blacklight displays a list of search results, it uses a Solr request
-  handler named "search." Thus, the field list (fl param) for the "search"
-  request handler should be tailored to what will be displayed in a search
-  results page.  Generally, this will not include fields containing a large
-  quantity of text.  The facet param should contain the facets to be
-  displayed with the search results.
-  ```xml
-	<requestHandler name="search" class="solr.SearchHandler" >
-		<lst name="defaults">
-			<str name="defType">dismax</str>
-			<str name="echoParams">explicit</str>
-			<!-- list fields to be returned in the "fl" param -->
-			<str name="fl">*,score</str>
-			<str name="facet">on</str>
-			<str name="facet.mincount">1</str>
-			<str name="facet.limit">10</str>
-			<!-- list fields to be displayed as facets here. -->
-		    <str name="facet.field">format</str>
-		    <str name="facet.field">language_facet</str>
-			<str name="q.alt">*:*</str>
-		</lst>
-	</requestHandler>
-   ```
-#####Blacklight's "document" request handler:  for a single record
-  When Blacklight displays a single record it uses a Solr request handler
-  named "document".  The "document" handler doesn't necessarily need to be
-  different than the "search" handler, but it can be used to control which
-  fields are available to display a single document. In the example below,
-  there is no faceting set (facets are not displayed with a single record)
-  and the "rows" param is set to 1 (since there will only be a single record).
-  Also, the field list ("fl" param) could include fields containing large
-  text values if they are desired for record display. Is is acceptable to
-  include large amounts of data, because this handler should only be used
-  to query for one document:
-	<requestHandler name="document" class="solr.SearchHandler">
-		<lst name="defaults">
-			<str name="echoParams">explicit</str>
-			<str name="fl">*</str>
-			<str name="rows">1</str>
-			<str name="q">{!raw f=id v=$id}</str>
-			<!-- use id=blah instead of q=id:blah -->
-		</lst>
-	</requestHandler>
-  A Solr query for a single record might look like this:
-   http://(yourSolrBaseUrl)/solr/select?id=my_doc_id&qt=document
-####Blacklight Solr Schema and Solrconfig File Templates
-Blacklight provides schema.xml and solrconfig.xml files as starting points:
-  https://github.com/projectblacklight/blacklight-jetty/blob/master/solr/blacklight-core/conf/schema.xml
-  https://github.com/projectblacklight/blacklight-jetty/blob/master/solr/blacklight-core/conf/solrconfig.xml
-#SolrMARC:  from Marc data to Solr documents
-The SolrMARC project is designed to create a Solr index from raw MARC data.
-It can be configured easily and used with the basic parsing and indexing
-supplied.  It is also readily customized for a site's unique requirements.
-The project software and documentation is available at [[http://code.google.com/p/solrmarc]]
-Blacklight comes with an embedded SolrMarc, with some default config that matches the default Blacklight setup, and provides some rake tasks to easily index docs with SolrMarc according to your app's environment.  There is no need to manually install/configure SolrMarc yourself.  From your application's home directory simply run:
-```bash
-  rake solr:marc:index:info
-```
-to see options.  Run `rake solr:marc:index` to actually do indexing. Like all rake tasks, by default this will use your 'development' environment; add "RAILS_ENV=production" to instead index to the solr you've labelled production in your config/solr.yml file.
-The solrmarc config files are in your app's config/SolrMarc directory, you can edit them there for local config.
-If you'd like to use a different or more recent version of SolrMarc.jar, you can put it in your app at ./solr_marc/SolrMarc.jar, and the built-in rake tasks will use your local SolrMarc.jar instead of the one bundled with Blacklight.