solr_schema.xml

<?xml version="1.0" encoding="UTF-8" ?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements.  See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License.  You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->

<!--  
This is the Solr schema file. This file should be named "schema.xml" and
should be in the conf directory under the solr home
(i.e. ./solr/conf/schema.xml by default) 
or located where the classloader for the Solr webapp can find it.

This example schema is the recommended starting point for users.
It should be kept correct and concise, usable out-of-the-box.

For more information, on how to customize this file, please see
http://wiki.apache.org/solr/SchemaXml
-->

<schema name="example" version="1.1">
  <!-- attribute "name" is the name of this schema and is only used for display purposes.
  Applications should change this to reflect the nature of the search collection.
  version="1.1" is Solr's version number for the schema syntax and semantics.  It should
  not normally be changed by applications.
  1.0: multiValued attribute did not exist, all fields are multiValued by nature
  1.1: multiValued attribute introduced, false by default -->

  <types>
	<!-- field type definitions. The "name" attribute is
	just a label to be used by field definitions.  The "class"
	attribute and any other attributes determine the real
	behavior of the fieldType.
	Class names starting with "solr" refer to java classes in the
	org.apache.solr.analysis package.
	-->

	<!-- The StrField type is not analyzed, but indexed/stored verbatim.  
	- StrField and TextField support an optional compressThreshold which
	limits compression (if enabled in the derived fields) to values which
	exceed a certain size (in characters).
	-->
	<fieldType name="string" class="solr.StrField" sortMissingLast="true" omitNorms="true"/>

	<!-- boolean type: "true" or "false" -->
	<fieldType name="boolean" class="solr.BoolField" sortMissingLast="true" omitNorms="true"/>

	<!-- The optional sortMissingLast and sortMissingFirst attributes are
	currently supported on types that are sorted internally as strings.
	- If sortMissingLast="true", then a sort on this field will cause documents
	without the field to come after documents with the field,
	regardless of the requested sort order (asc or desc).
	- If sortMissingFirst="true", then a sort on this field will cause documents
	without the field to come before documents with the field,
	regardless of the requested sort order.
	- If sortMissingLast="false" and sortMissingFirst="false" (the default),
	then default lucene sorting will be used which places docs without the
	field first in an ascending sort and last in a descending sort.
	-->    


	<!-- numeric field types that store and index the text
	value verbatim (and hence don't support range queries, since the
	lexicographic ordering isn't equal to the numeric ordering) -->
	<fieldType name="integer" class="solr.IntField" omitNorms="true"/>
	<fieldType name="long" class="solr.LongField" omitNorms="true"/>
	<fieldType name="float" class="solr.FloatField" omitNorms="true"/>
	<fieldType name="double" class="solr.DoubleField" omitNorms="true"/>


	<!-- Numeric field types that manipulate the value into
	a string value that isn't human-readable in its internal form,
	but with a lexicographic ordering the same as the numeric ordering,
	so that range queries work correctly. -->
	<fieldType name="sint" class="solr.SortableIntField" sortMissingLast="true" omitNorms="true"/>
	<fieldType name="slong" class="solr.SortableLongField" sortMissingLast="true" omitNorms="true"/>
	<fieldType name="sfloat" class="solr.SortableFloatField" sortMissingLast="true" omitNorms="true"/>
	<fieldType name="sdouble" class="solr.SortableDoubleField" sortMissingLast="true" omitNorms="true"/>


	<!-- The format for this date field is of the form 1995-12-31T23:59:59Z, and
	is a more restricted form of the canonical representation of dateTime
	http://www.w3.org/TR/xmlschema-2/#dateTime    
	The trailing "Z" designates UTC time and is mandatory.
	Optional fractional seconds are allowed: 1995-12-31T23:59:59.999Z
	All other components are mandatory.

	Expressions can also be used to denote calculations that should be
	performed relative to "NOW" to determine the value, ie...

	NOW/HOUR
	... Round to the start of the current hour
	NOW-1DAY
	... Exactly 1 day prior to now
	NOW/DAY+6MONTHS+3DAYS
	... 6 months and 3 days in the future from the start of
	the current day

	Consult the DateField javadocs for more information.
	-->
	<fieldType name="date" class="solr.DateField" sortMissingLast="true" omitNorms="true"/>


	<!-- The "RandomSortField" is not used to store or search any
	data.  You can declare fields of this type it in your schema
	to generate psuedo-random orderings of your docs for sorting 
	purposes.  The ordering is generated based on the field name 
	and the version of the index, As long as the index version
	remains unchanged, and the same field name is reused,
	the ordering of the docs will be consistent.  
	If you want differend psuedo-random orderings of documents,
	for the same version of the index, use a dynamicField and
	change the name
	-->
	<fieldType name="random" class="solr.RandomSortField" indexed="true" />

	<!-- solr.TextField allows the specification of custom text analyzers
	specified as a tokenizer and a list of token filters. Different
	analyzers may be specified for indexing and querying.

	The optional positionIncrementGap puts space between multiple fields of
	this type on the same document, with the purpose of preventing false phrase
	matching across fields.

	For more info on customizing your analyzer chain, please see
	http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters
	-->

	<!-- One can also specify an existing Analyzer class that has a
	default constructor via the class attribute on the analyzer element
	<fieldType name="text_greek" class="solr.TextField">
	  <analyzer class="org.apache.lucene.analysis.el.GreekAnalyzer"/>
	</fieldType>
	-->

	<!-- A text field that only splits on whitespace for exact matching of words -->
	<fieldType name="text_ws" class="solr.TextField" positionIncrementGap="100">
	  <analyzer>
		<tokenizer class="solr.WhitespaceTokenizerFactory"/>
	  </analyzer>
	</fieldType>

	<!-- A text field that uses WordDelimiterFilter to enable splitting and matching of
	words on case-change, alpha numeric boundaries, and non-alphanumeric chars,
	so that a query of "wifi" or "wi fi" could match a document containing "Wi-Fi".
	Synonyms and stopwords are customized by external files, and stemming is enabled.
	Duplicate tokens at the same position (which may result from Stemmed Synonyms or
	WordDelim parts) are removed.
	-->
	<fieldType name="text" class="solr.TextField" positionIncrementGap="100">
	  <analyzer type="index">
		<tokenizer class="solr.StandardTokenizerFactory"/>
		<!--commenting this out should allow better (less magic) matching
		<filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
		-->
		<filter class="solr.LowerCaseFilterFactory"/>
	  </analyzer>
	  <analyzer type="query">
		<tokenizer class="solr.StandardTokenizerFactory"/>
		<!--commenting this out should allow better (less magic) matching
		<filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="0" catenateNumbers="0" catenateAll="0" splitOnCaseChange="1"/>
		-->
		<filter class="solr.LowerCaseFilterFactory"/>
	  </analyzer>
	</fieldType>

	<!-- since fields of this type are by default not stored or indexed, any data added to 
	them will be ignored outright 
	--> 
	<fieldtype name="ignored" stored="false" indexed="false" class="solr.StrField" /> 

  </types>


  <fields>
	<!-- Valid attributes for fields:
	name: mandatory - the name for the field
	type: mandatory - the name of a previously defined type from the <types> section
	  indexed: true if this field should be indexed (searchable or sortable)
	  stored: true if this field should be retrievable
	  compressed: [false] if this field should be stored using gzip compression
	  (this will only apply if the field type is compressable; among
	  the standard field types, only TextField and StrField are)
	  multiValued: true if this field may contain multiple values per document
	  omitNorms: (expert) set to true to omit the norms associated with
	  this field (this disables length normalization and index-time
	  boosting for the field, and saves some memory).  Only full-text
	  fields or fields that need an index-time boost need norms.
	  termVectors: [false] set to true to store the term vector for a given field.
	  When using MoreLikeThis, fields used for similarity should be stored for 
	  best performance.
	  -->

	  <!-- DASe -->

	  <!-- 
	  underscore so these will NOT collide w/ attribute ascii ids will NOT be used in 
	  search query so under score OK
	  -->
	  <field name="_id" type="string" indexed="true" stored="true" required="true"/>
	  <field name="_search_text" type="text" indexed="true" stored="false" multiValued="false"/>
	  <field name="_item_id" type="text" indexed="true" stored="false" multiValued="false"/>
	  <field name="_serial_number" type="text" indexed="true" stored="false" multiValued="false"/>
	  <field name="_media_count" type="text" indexed="true" stored="false" multiValued="false"/>

	  <!-- 
	  note that the following field names CANNOT be used as att_ascii_id or Att Name 
	  not underscore since they may be used in search query
	  -->

	  <field name="item_type" type="string" indexed="true" stored="false" required="false"/>
	  <field name="item_type_name" type="text" indexed="true" stored="false" required="false"/>
	  <field name="admin" type="text" indexed="true" stored="false" multiValued="false"/>

	  <!-- for facetting -->
	  <field name="collection" type="string" indexed="true" required="true"/>
	  <field name="c" type="string" indexed="true" stored="true" required="false"/>

	  <!-- for sorting -->
	  <field name="_updated" type="string" indexed="true" stored="true" multiValued="false"/>
	  <field name="_created" type="string" indexed="true" stored="true" multiValued="false"/>
	  <!-- end DASe -->

	  <!-- Here, default is used to create a "timestamp" field indicating
	  When each document was indexed.
	  -->
	  <field name="timestamp" type="date" indexed="true" stored="true" default="NOW" multiValued="false"/>

	  <!-- allows attribute_ascii_id preceded by '@' perform exact search (beware special chars)-->
	  <dynamicField name="@*" type="string" stored="false" indexed="true" multiValued="true"/>

	  <dynamicField name="*" type="text" stored="false" indexed="true" multiValued="true"/>

	</fields>

	<!-- Field to use to determine and enforce document uniqueness. 
	Unless this field is marked with required="false", it will be a required field
	-->
	<uniqueKey>_id</uniqueKey>

	<!-- field for the QueryParser to use when an explicit fieldname is absent -->
	<defaultSearchField>_search_text</defaultSearchField>

	<!-- SolrQueryParser configuration: defaultOperator="AND|OR" -->
	<solrQueryParser defaultOperator="AND"/>

	<!-- copyField commands copy one field to another at the time a document
	is added to the index.  It's used either to index the same field differently,
	or to add multiple fields to the same field for easier/faster searching.  -->

	<!--
	<copyField source="name" dest="text"/>
	<copyField source="name" dest="nameSort"/>
	<copyField source="name" dest="alphaNameSort"/>
	<copyField source="name" dest="spell"/>
	-->

	<!-- Similarity is the scoring routine for each document vs. a query.
	A custom similarity may be specified here, but the default is fine
	for most applications.  -->
	<!-- <similarity class="org.apache.lucene.search.DefaultSimilarity"/> -->
	<!-- ... OR ...
	Specify a SimilarityFactory class name implementation
	allowing parameters to be used.
	-->
	<!--
	<similarity class="com.example.solr.CustomSimilarityFactory">
	  <str name="paramkey">param value</str>
	</similarity>
	-->


  </schema>