<?xml version="1.0" encoding="UTF-8"?>
<!--
	#
	# DSpace Configuration
	#
	# Revision: $Revision: 1.81 $
	#
	# Date:     $Date: 2006/11/27 16:16:49 $
	#
-->
<configuration>
	<!-- Basic information -->
	<dspace>
		<!-- DSpace installation directory -->
		<dir>/dspace</dir>

		<!-- DSpace base URL.  Include port number etc., but NOT trailing slash -->
		<url>http://dspace.myu.edu:8080/dspace</url>

		<!-- DSpace host name - should match base URL.  Do not include port number -->
		<hostname>dspace.myu.edu</hostname>

		<!-- Name of the site -->
		<name>DSpace at My University</name>
	</dspace>

	<config>
		<!--
			##### Destinations for configuration files for other tools #####
			Comment out any lines corresponding to files you don't need, so they
			don't get copied
			Example Apache HTTPD configuration
			config.template.apache13.conf = ${dspace.dir}/config/httpd.conf
		-->
		<template>
			<log4j><properties>
				${dspace.dir}/config/log4j.properties
			</properties></log4j>
			<log4j-handle-plugin><properties>
				${dspace.dir}/config/log4j-handle-plugin.properties
			</properties></log4j-handle-plugin>
			<oaicat><properties>
				${dspace.dir}/config/oaicat.properties
			</properties></oaicat>
		</template>
	</config>

	<!--
		Database settings
	-->
	<db>
		<!--
			Alternate Orcale Example
			<name>oracle</name>
			<url>jdbc:oracle://localhost:5432/dspace</url>
			<driver>com.oracle.?????</driver>
		-->

		<name>postgres</name>
		<url>jdbc:postgresql://localhost:5432/dspace</url>
		<!-- JDBC Driver -->
		<driver>org.postgresql.Driver</driver>
		<!-- Database username and password -->
		<username>dspace</username>
		<password>dspace</password>
		<!-- 
			Maximum number of DB connections in pool
		-->
		<maxconnections>30</maxconnections>
		<!-- 
			Maximum time to wait before giving up if all connections in pool are busy (milliseconds)
		-->
		<maxwait>5000</maxwait>
		<!--
			Maximum number of idle connections in pool (-1 = unlimited)
		-->
		<maxidle>-1</maxidle>

		<!--
			Determine if prepared statement should be cached. (default is true)
		-->
		<statementpool>true</statementpool>
	</db>

	<!--
		Email settings 
	-->

	<mail>
		<server>
			<!-- 
				# SMTP mail server (mail.server) 
				(maybe should be mail.server.host) 
			-->
			smtp.myu.edu
			<!-- 
				SMTP mail server authentication username and password (if required)
				(mail.server.username)
				(mail.server.password)
			-->
			<username>myusername</username>
			<password>mypassword</password>
		</server>
		<!--
			# From address for mail
			(mail.from.address)
		-->
		<from>
			<address>dspace-noreply@myu.edu</address>
		</from>
		<!--
			# General site administration (Webmaster) e-mail (mail.admin)
		-->
		<admin>dspace-help@myu.edu</admin>
	</mail>
	<!--
		# Currently limited to one recipient! (feedback.recipient)
	-->
	<feedback>
		<recipient>dspace-help@myu.edu</recipient>
	</feedback>
	<!--
		# Uncomment for Recipient for server errors and alerts 
		(alert.recipient) = email-address-here
		<alert><recipient>email-address-hear</recipient></alert>
	-->

	<!--
		##### File Storage ######
	-->
	<assetstore>
		<!--
			(assetstore.dir) Asset (bitstream) store number 0 (zero)
			
			# Specify the number of the store to use for new bitstreams with this property
			# The default is 0 (zero) which corresponds to the 'assetstore.dir' above
			# assetstore.incoming = 1
		-->
		<dir id="0" incoming="true">${dspace.dir}/assetstore</dir>
		<!--
			# Specify extra asset stores like this, counting from 1 upwards:
			# assetstore.dir.1 = /second/assetstore
			# assetstore.dir.2 = /third/assetstore
		-->
		<dir id="1">/second/assetstore</dir>
		<dir id="2">/third/assetstore</dir>
	</assetstore>

	<!--
		##### SRB File Storage #####
		
		# The same 'assetstore.incoming' property is used to support the use of SRB 
		# (Storage Resource Broker - see http://www.sdsc.edu/srb/) as an _optional_ 
		# replacement of or supplement to conventional file storage. DSpace will work
		# with or without SRB and full backward compatibility is maintained.
		#
		# The 'assetstore.incoming' property is an integer that references where _new_
		# bitstreams will be stored.  The default (say the starting reference) is zero.
		# The value will be used to identify the storage where all new bitstreams will
		# be stored until this number is changed.  This number is stored in the 
		# Bitstream table (store_number column) in the DSpace database, so older 
		# bitstreams that may have been stored when 'asset.incoming' had a different 
		# value can be found.
		#
		# In the simple case in which DSpace uses local (or mounted) storage the
		# number can refer to different directories (or partitions).  This gives DSpace
		# some level of scalability.  The number links to another set of properties
		# 'assetstore.dir', 'assetstore.dir.1' (remember zero is default), 
		# 'assetstore.dir.2', etc., where the values are directories.
		#
		# To support the use of SRB DSpace uses this same scheme but broadened to 
		# support:
		# - using SRB instead of the local filesystem
		# - using the local filesystem (native DSpace)
		# - using a mix of SRB and local filesystem
		#
		# In this broadened use the 'asset.incoming' integer will refer one of the 
		# following storage locations
		# - a local filesystem directory (native DSpace)
		# - a set of SRB account parameters (host, port, zone, domain, username, 
		#	password, home directory, and resource)
		#
		# Should the be any conflict, like '2' refering to a local directory and 
		# to a set of SRB parameters, the program will select the local directory.
		#
		# If SRB is chosen from the first install of DSpace, it is suggested that
		# 'assetstore.dir' (no integer appended) be retained to reference a local
		# directory (as above under File Storage) because build.xml uses this value 
		# to do a mkdir. In this case, 'assetstore.incoming' can be set to 1 (i.e.
		# uncomment the line in File Storage above) and the 'assetstore.dir' will not 
		# be used.
		#
		# Here is an example set of SRB parameters:
		# Assetstore 1 - SRB
		#srb.host.1 = mysrbmcathost.myu.edu
		#srb.port.1 = 5544
		#srb.mcatzone.1 = mysrbzone
		#srb.mdasdomainname.1 = mysrbdomain
		#srb.defaultstorageresource.1 = mydefaultsrbresource
		#srb.username.1 = mysrbuser
		#srb.password.1 = mysrbpassword
		#srb.homedirectory.1 = /mysrbzone/home/mysrbuser.mysrbdomain
		#srb.parentdir.1 = mysrbdspaceassetstore
		#
		# Assetstore n, n+1, ...
		# Follow same pattern as for assetstores above (local or SRB)
		
		<srb>
		<host>mysrbmcathost.myu.edu</host>
		<port>5544</port>
		<mcatzone>mysrbzone</mcatzone>
		<mdasdomainname>mysrbdomain</mdasdomainname>
		<defaultstorageresource>mydefaultsrbresource</defaultstorageresource>
		<username>mysrbuser</username>
		<password>mysrbpassword</password>
		<homedirectory>/mysrbzone/home/mysrbuser.mysrbdomain</homedirectory>
		<parentdir>mysrbdspaceassetstore</parentdir>
		</srb>
	-->

	<!--
		# Directory for history serializations
		history.dir = ${dspace.dir}/history
	-->
	<history>
		<dir>${dspace.dir}/history</dir>
	</history>

	<!--
		# Where to put the logs
		log.dir = ${dspace.dir}/log
	-->
	<log>
		<dir>${dspace.dir}/log</dir>
	</log>


	<upload>
		<!--
			# Where to temporarily store uploaded files
			upload.temp.dir = ${dspace.dir}/upload
		-->
		<temp>
			<dir>${dspace.dir}/upload</dir>
		</temp>
		<!--
			# Maximum size of uploaded files in bytes, negative setting will result in no limit being set
			# 512Mb
		-->
		<max>536870912</max>
	</upload>

	<!--
		##### Search settings #####
	-->
	<search>
		<!--
			# Where to put search index files
			search.dir = ${dspace.dir}/search
		-->
		<dir>${dspace.dir}/search</dir>

		<!--
			# Higher values of search.max-clauses will enable prefix searches to work on
			# large repositories
			# search.max-clauses = 2048
			<max-clauses>2048</max-clauses>
		-->

		<!--
			# Which Lucene Analyzer implementation to use.  If this is omitted or
			# commented out, the standard DSpace analyzer (designed for English)
			# is used by default.
			# search.analyzer = org.dspace.search.DSAnalyzer
			
			# Chinese analyzer
			# search.analyzer = org.apache.lucene.analysis.cn.ChineseAnalyzer
			<analyzer>org.apache.lucene.analysis.cn.ChineseAnalyzer</analyzer>
		-->

		<!--
			# Boolean search operator to use, current supported values are OR and AND
			# If this config item is missing or commented out, OR is used
			# AND requires all search terms to be present
			# OR requires one or more search terms to be present
			search.operator = OR
		-->
		<operator>OR</operator>

		<!--
			##### Fulltext Indexing settings #####
			# Maximum number of terms indexed for a single field in Lucene.
			# Default is 10,000 words - often not enough for full-text indexing.
			# If you change this, you'll need to re-index for the change
			# to take effect on previously added items.
			# -1 = unlimited (Integer.MAX_VALUE)
			search.maxfieldlength = 10000
		-->
		<maxfieldlength>10000</maxfieldlength>


		<!--
			##### Fields to Index for Search #####
			# DC metadata elements.qualifiers to be indexed for search
			# format: - search.index.[number] = [search field]:element.qualifier
			#         - * used as wildcard
			###      changing these will change your search results,     ###
			###  but will NOT automatically change your search displays  ###
			search.index.1 = author:dc.contributor.*
			search.index.2 = author:dc.creator.*
			search.index.3 = title:dc.title.*
			search.index.4 = keyword:dc.subject.*
			search.index.5 = abstract:dc.description.abstract
			search.index.6 = author:dc.description.statementofresponsibility
			search.index.7 = series:dc.relation.ispartofseries
			search.index.8 = abstract:dc.description.tableofcontents
			search.index.9 = mime:dc.format.mimetype
			search.index.10 = sponsor:dc.description.sponsorship
			search.index.11 = identifier:dc.identifier.*
			search.index.12 = language:dc.language.iso	
			
			Marks Comments: These enumerations are not neccessary in some places
			here for example, it is just to allow multiple keys
			close to the same id, we can do better with Commons Config
		-->
		<index>
			<field name="author">dc.contributor.*</field>
			<field name="author">dc.creator.*</field>
			<field name="author">
				dc.description.statementofresponsibility
			</field>
			<field name="title">dc.title.*</field>
			<field name="keyword">dc.subject.*</field>
			<field name="abstract">dc.description.abstract</field>
			<field name="abstract">
				dc.description.tableofcontents
			</field>
			<field name="series">dc.relation.ispartofseries</field>
			<field name="mime">dc.format.mimetype</field>
			<field name="sponsor">dc.description.sponsorship</field>
			<field name="identifier">dc.identifier.*</field>
			<field name="language">dc.language.iso</field>
		</index>
	</search>


	<!--
		###### Statistical Report Configuration Settings ######
	-->
	<report>
		<!--
			# should the stats be publicly available?  should be set to false if you only
			# want administrators to access the stats, or you do not intend to generate
			# any report.public = false
		-->
		<public>false</public>

		<!--
			# directory where live reports are stored
			report.dir = ${dspace.dir}/reports/
		-->
		<dir>${dspace.dir}/reports/</dir>
	</report>

	<!--
		##### Handle settings ######
	-->
	<handle>

		<!--
			# CNRI Handle prefix
			handle.prefix = 123456789
		-->
		<prefix>123456789</prefix>

		<!--
			# Directory for installing Handle server files
			handle.dir = ${dspace.dir}/handle-server
		-->
		<dir>${dspace.dir}/handle-server</dir>

	</handle>

	<!-- 
		#### Stackable Authentication Methods #####
		# Stack of authentication methods
		#  (See org.dspace.eperson.AuthenticationManager)
		plugin.sequence.org.dspace.eperson.AuthenticationMethod = \
		org.dspace.eperson.PasswordAuthentication
	-->
	<plugin type="sequence"
		interface="org.dspace.eperson.AuthenticationMethod">
		<class>org.dspace.eperson.PasswordAuthentication</class>
	</plugin>

	<!-- 
		#### Example of configuring X.509 authentication
		#### (to use it, add org.dspace.eperson.X509Authentication to auth stack above)
		
		<plugin type="sequence" interface="org.dspace.eperson.AuthenticationMethod">
		<class>org.dspace.eperson.PasswordAuthentication</class>
		</plugin>
		
		<authentication>
		<x509>
		## method 1, using keystore
		#authentication.x509.keystore.path = /tomcat/conf/keystore
		#authentication.x509.keystore.password = changeit
		<keystore>
		<path>/tomcat/conf/keystore</path>
		<password>changeit</password>
		</keystore>
		## method 2, using CA certificate
		#authentication.x509.ca.cert = ${dspace.dir}/config/MyClientCA.pem
		<ca><cert>${dspace.dir}/config/MyClientCA.pem</cert></ca>
		## Create e-persons for unknown names in valid certificates?
		#authentication.x509.autoregister = true
		<autoregister>true</autoregister>
		</x509>
		</authentication>
	-->

	<!-- 
		##### Web UI Settings ######
	-->
	<webui>
		<!-- 
			## webui.ldap.autoregister ##
			#
			# This will turn LDAP autoregistration on or off.  With this
			# on, a new EPerson object will be created for any user who
			# successfully authenticates against the LDAP server when they
			# first login.  With this setting off, the user
			# must first register to get an EPerson object by
			# entering their ldap username and password and filling out
			# the forms.
			webui.ldap.autoregister = true
		-->
		<ldap>
			<autoregister>true</autoregister>
		</ldap>


		<submit>
			<!--  
				# Should the submit UI block submissions marked as theses?
				webui.submit.blocktheses = false
			-->
			<blocktheses>false</blocktheses>
			<!--
				#### Creative Commons settings ######
				# are Creative Commons licenses used in submission?
				webui.submit.enable-cc = false
				<enable-cc>false</enable-cc>
			-->
		</submit>

		<!--
			# whether to display thumbnails on browse and search results pages (1.2+)
			webui.browse.thumbnail.show = false
		-->
		<browse>
			<!-- 
				# Set the bindings for the DC browse fields.  These determine which metadata
				# elements are used for browse by date, author, title and subject.  In addition, 
				# these settings will be used to determine the behaviour of the fields on the
				# listing page: dates will be formatted as required, and titles will be links
				# to item metadata pages.  At least the date and title fields ought to be
				# specified in the webui.itemlist.columns parameters.
				#
				# The form is <schema_prefix>.<element>[.<qualifier>|.*], ...
				#
				# NOTE: if you make changes to this configuration to an existing DSpace
				# installation you must re-index the system using: 
				#
				# % [dspace]/bin/index-all
				#
				# webui.browse.index.date = dc.date.issued
				# webui.browse.index.author = dc.contributor.*
				# webui.browse.index.title = dc.title
				# webui.browse.index.subject = dc.subject.*
				<index>
				<date>dc.date.issued</date>
				<author>dc.contributor.*</author>
				<title>dc.title</title>
				<subject>dc.subject.*</subject>
				</index>	
			-->

			<thumbnail>
				<show>false</show>
				<!--
					# max dimensions of the browse/search thumbs. Must be <= thumbnail.maxwidth
					# and thumbnail.maxheight. Only need to be set if required to be smaller than
					# dimension of thumbnails generated by mediafilter (1.2+)
					#webui.browse.thumbnail.maxheight = 80
					#webui.browse.thumbnail.maxwidth = 80
					<maxheight>80</maxheight>
					<maxwidth>80</maxwidth>
				-->
				<!--
					# where should clicking on a thumbnail from browse/search take the user
					# Only values currently supported are "item" and "bitstream"
					#webui.browse.thumbnail.linkbehaviour = item
					<linkbehavior>item</linkbehavior>
				-->
			</thumbnail>
		</browse>


		<!-- 
			# whether to display the thumb against each bitstream (1.2+)
			webui.item.thumbnail.show = true
		-->
		<item>
			<thumbnail>
				<show>true</show>
			</thumbnail>
		</item>


		<preview>
			<!-- 
				#### Settings for Item Preview ####
				webui.preview.enabled = false
			-->
			<enabled>true</enabled>

			<!--
				# max dimensions of the preview image
				webui.preview.maxwidth = 600
				webui.preview.maxheight = 600
			-->
			<maxwidth>600</maxwidth>
			<maxheight>600</maxheight>

			<!-- 
				# the brand text
				webui.preview.brand = My Institution Name
			-->
			<brand>
				My Institution Name
				<!-- 
					# an abbreviated form of the above text, this will be used
					# when the preview image cannot fit the normal text
					webui.preview.brand.abbrev = MyOrg
				-->
				<abbrev>MyOrg</abbrev>
				<!--
					# the height of the brand
					webui.preview.brand.height = 20
				-->
				<height>20</height>
				<!--
					# font settings for the brand text
					webui.preview.brand.font = SansSerif
					webui.preview.brand.fontpoint = 12
				-->
				<font>SansSerif</font>
				<fontpont>12</fontpont>
			</brand>

			<!-- #webui.preview.dc = rights -->
			<dc>rights</dc>
		</preview>

		<!-- 
			# whether to display collection and community strengths
			webui.strengths.show = false
		-->
		<strengths>
			<show>false</show>
		</strengths>

		<!-- 
			# whether to display the contents of the licence bundle (often just the deposit
			# licence in standard DSpace installation
			webui.licence_bundle.show = false
		-->
		<licence_bundle>
			<show>false</show>
		</licence_bundle>

		<!--  
			# Customise the DC metadata fields to show in the default simple item view.
			# 
			# The form is <schema_prefix>.<element>[.<qualifier>|.*][(date)|(link)], ...
			#
			# For example:
			#    dc.title               = Dublin Core element 'title' (unqualified)
			#    dc.title.alternative   = DC element 'title', qualifier 'alternative'
			#    dc.title.*             = All fields with Dublin Core element 'title' 
			#                             (any or no qualifier)
			#    dc.identifier.uri(link) = DC identifier.uri, render as a link
			#    dc.date.issued(date)   = DC date.issued, render as a date
			#
			# If an item has no value for a particular field, it won't be displayed.
			# The name of the field for display will be drawn from the current UI
			# dictionary, using the key:
			#
			# "metadata.<field>"
			#
			# e.g.   "metadata.dc.title"
			#        "metadata.dc.contributor.*" 
			#        "metadata.dc.date.issued"
			#
			#webui.itemdisplay.default = dc.title, dc.title.alternative, dc.contributor.*, \
			#                            dc.subject, dc.date.issued(date), dc.publisher, \
			#                            dc.identifier.citation, dc.relation.ispartofseries, \
			#                            dc.description.abstract, dc.description, \
			#                            dc.identifier.govdoc, dc.identifier.uri(link), \
			#                            dc.identifier.isbn, dc.identifier.issn, \
			#                            dc.identifier.ismn, dc.identifier
			
			<itemdisplay>
			<default>dc.title</default>
			<default>dc.title.alternative</default>
			<default>dc.contributor.*</default>
			<default>dc.subject</default>
			<default>dc.date.issued(date)</default>
			<default>dc.publisher</default>
			<default>dc.identifier.citation</default>
			<default>dc.relation.ispartofseries</default>
			<default>dc.description.abstract</default>
			<default>dc.description</default>
			<default>dc.identifier.govdoc</default>
			<default>dc.identifier.uri(link)</default>
			<default>dc.identifier.isbn</default>
			<default>dc.identifier.issn</default>
			<default>dc.identifier.ismn</default>
			<default>dc.identifier</default>
			</itemdisplay>
		-->

		<!-- 
			# Specify which collections use which views by Handle.
			#
			# webui.itemdisplay.<style>.collections = <collection handle>, ...
			#
			# FIXME: This should be more database-driven
			#
			# webui.itemdisplay.thesis.collections = 123456789/24, 123456789/35
			<itemdisplay>
			<thesis>
			<collections>123456789/24</collections>
			<collections>123456789/35</collections>
			</thesis>
			</itemdisplay>
		-->

		<!--
			# Customise the DC fields to use in the item listing page.  Elements will be
			# displayed left to right in the order that they are specified here.
			#
			# The form is <schema prefix>.<element>[.<qualifier>|.*][(date)], ...
			#
			# Although not a requirement, it would make sense to include among the listed
			# fields at least the date and title fields as specified by the
			# webui.browse.index.* configuration options below.
			#
			# webui.itemlist.columns = dc.date.issued(date), dc.title, dc.contributor.*
			<itemlist>
			<columns>dc.date.issued(date)</columns>
			<columns>dc.title</columns>
			<columns>dc.contributor.*</columns>
			</itemlist>
		-->

		<!--
			#### Syndication Feed Settings ######
		-->
		<feed>
			<!-- 
				# enable syndication feeds - links display on community and collection home pages 
				webui.feed.enable = false
			-->
			<enable>false</enable>
			<!-- 
				# number of DSpace items per feed (the most recent submissions)
				webui.feed.items = 4
			-->
			<items>4</items>

			<cache>
				<!--
					# maximum number of feeds in memory cache
					# value of 0 will disable caching
					webui.feed.cache.size = 100
				-->
				<size>100</size>
				<!-- 
					# number of hours to keep cached feeds before checking currency
					# value of 0 will force a check with each request
					webui.feed.cache.age = 48
				-->
				<age>48</age>
			</cache>
			<!--
				# which syndication formats to offer
				# use one or more (comma-separated) values from list:
				# rss_0.90, rss_0.91, rss_0.92, rss_0.93, rss_0.94, rss_1.0, rss_2.0
				webui.feed.formats = rss_1.0,rss_2.0
				# URLs returned by the feed will point at the global handle server (e.g. http://hdl.handle.net/123456789/1)
				# Set to true to use local server URLs (i.e. http://myserver.myorg/handle/123456789/1)
				webui.feed.localresolve = false
			-->
			<localresolve>false</localresolve>
			<!--
				# Customize each single-value field displayed in the
				# feed information for each item.  Each of
				# the below fields takes a *single* metadata field
				#
				# The form is &lt;schema prefix>.&lt;element>[.&lt;qualifier>|.*]
				
				webui.feed.item.title = dc.title
				webui.feed.item.date = dc.date.issued
			-->
			<item>
				<title>dc.title</title>
				<date>dc.date.issued</date>

				<!--
					# Customise the metadata fields to show in the feed for each item's description.
					# Elements will be displayed in the order that they are specified here.
					#
					# The form is <schema prefix>.<element>[.<qualifier>|.*][(date)], ...
					#
					# Similar to the item display UI, the name of the field for display 
					# in the feed will be drawn from the current UI dictionary, 
					# using the key:
					# "metadata.<field>"
					#
					# e.g.   "metadata.dc.title"
					#        "metadata.dc.contributor.author" 
					#        "metadata.dc.date.issued"
					webui.feed.item.description = dc.title, dc.contributor.author, \
					dc.contributor.editor, dc.description.abstract, \
					dc.description
				-->
				<description>
					dc.title, dc.contributor.author,
					dc.contributor.editor, dc.description.abstract,
					dc.description
				</description>
			</item>

		</feed>

		<!-- 
			#### Item Recommendation Settings #####
			# show a link to the item recommendation page from item display page
			webui.suggest.enable = false
			# default name of recommender - replaced by user input if present
			webui.suggest.sender = A DSpace user
			# default name of recipient - replaced by user input if present
			webui.suggest.recipient = colleague
		-->
		<suggest>
			<enable>false</enable>
			<sender>A DSpace user</sender>
			<recipient>colleague</recipient>
		</suggest>

		<!--
			#### Controlled Vocabulary Settings #####
			# Enable or disable the controlled vocabulary add-on
			# Warning: this feature is not compatible with WAI (it requires javascript to function)
			#
			# webui.controlledvocabulary.enable = true
			
			<controlledvocabulary><enable>true</enable></controlledvocabulary>
		-->

		<!-- 
			#### Multi-file HTML document/site settings #####
			#
			# When serving up composite HTML items, how deep can the request be for us to
			# serve up a file with the same name?
			#
			# e.g. if we receive a request for "foo/bar/index.html"
			# and we have a bitstream called just "index.html"
			# we will serve up that bitstream for the request if webui.html.max-depth-guess
			# is 2 or greater.  If webui.html.max-depth-guess is 1 or less, we would not
			# serve that bitstream, as the depth of the file is greater.
			#
			# If webui.html.max-depth-guess is zero, the request filename and path must
			# always exactly match the bitstream name.  Default value is 3.
			#
			# webui.html.max-depth-guess = 3
			
			<html><max-depth-guess>3</max-depth-gess></html>
		-->
	</webui>

	<!-- 
		##### SFX Server #####
		# SFX query is appended to this URL.  If this property is commented out or
		# omitted, SFX support is switched off.
		# sfx.server.url = http://sfx.myu.edu:8888/sfx?
		<sfx><server><url>http://sfx.myu.edu:8888/sfx?</url></server></sfx>
	-->

	<!-- 
		##### Ingest settings #####
		# Default language for metadata values
		default.language = en_US
	-->
	<default>
		<language>en_US</language>
	</default>

	<!-- 
		##### Media Filter settings #####
		# maximum width and height of generated thumbnails
		thumbnail.maxwidth  80
		thumbnail.maxheight 80
	-->
	<thumbnail>
		<maxwidth>80</maxwidth>
		<maxheight>80</maxheight>
	</thumbnail>

	<!-- 
		#### OAI-PMH settings #####
		# Max response size for DIDL. This is the maximum size in bytes of the files you
		# wish to enclose Base64 encoded in your responses, remember that the base64
		# encoding process uses a lot of memory. We recommend at most 200000 for answers
		# of 30 records each on a 1 Gigabyte machine. Ultimately this will change to a
		# streaming model and remove this restriction. Also please remember to allocate
		# plenty of memory, at least 512 MB to your Tomcat.
		#
		# Optional: DSpace uses 100 records as the limit for the oai responses. You can
		# alter this by changing $DSPACE_SOURCE_DIR/src/org/dspace/app/oai/DSpaceOAICatalog.java to modify the
		# declaration:
		# private final int MAX_RECORDS = 100 to private final int MAX_RECORDS = 30
		# oai.didl.maxresponse = 0
		<oai><didl><maxresponse>0</maxresponse></didl><oai>
	-->

	<!-- 
		#### Proxy Settings ######
		# uncomment and specify both properties if proxy server required
		# proxy server for external http requests - use regular hostname without port number
		#http.proxy.host =
		
		# port number of proxy server
		#http.proxy.port = 
		<http>
		<proxy>
		<host>somedomain.com</host>
		<port>99999</port>
		</proxy>
		</http>
	-->

	<!-- 
		#### LDAP Authentication Configuration Settings ####
		#
		# If LDAP is enabled, then new users will be able to register
		# by entering their username and  password without being sent the 
		# registration token. If users do not have a username and password,
		# then they  can still register and login with just their email address 
		# the same way they do now. 
		#
		# For providing any special privileges to LDAP users,
		# you will still need to extend the SiteAuthenticator class to
		# automatically put people who have a netid into a special
		# group.  You might also want to give certain email addresses
		# special privileges. Refer to the DSpace documentation for more
		# information about how to do this.
		# 
		# It may be necessary to obtain the values of these settings from the
		# LDAP server administrators as LDAP configuration will vary from server
		# to server.	
	-->
	<ldap>
		<!-- 	
			# This setting will enable or disable LDAP authentication in DSpace.
			# With the setting off, users will be required to register and login with
			# their email address.  With this setting on, users will be able to login
			# and register with their LDAP user ids and passwords.
			ldap.enable = false
		-->
		<enable>false</enable>

		<!--
			# This is the url to the institution's ldap server. The /o=myu.edu
			# may or may not be required depending on the LDAP server setup.
			# A server may also require the ldaps:// protocol.
			#ldap.provider_url = ldap://ldap.myu.edu/o=myu.edu
			<provider_url>ldap://ldap.myu.edu/o=myu.edu</provider_url>
			
			# This is the unique identifier field in the LDAP directory
			# where the username is stored. 
			#ldap.id_field = uid
			<id_field>uid</id_field>
			
			# This is the object context used when authenticating the
			# user.  It is appended to the ldap.id_field and username. 
			# For example uid=username,ou=people,o=myu.edu.  This must match 
			# the LDAP server configuration.
			#ldap.object_context = ou=people,o=myu.edu
			<object_context>ou=people,o=myu.edu</object_context>
			
			# This is the search context used when looking up a user's
			# LDAP object to retrieve their data for autoregistering. 
			# With ldap.autoregister turned on, when a user authenticates
			# without an EPerson object, a search on the LDAP directory to
			# get their name and email address is initiated so that DSpace 
			# can create a EPerson object for them.  So after we have authenticated against
			# uid=username,ou=people,o=byu.edu we now search in ou=people
			# for filtering on [uid=username].  Often the
			# ldap.search_context is the same as the ldap.object_context
			# parameter.  But again this depends on each individual LDAP server
			# configuration.
			#ldap.search_context = ou=people
			<search_context>oou=people</search_context>
			
			# This is the LDAP object field where the user's email address
			# is stored.  "mail" is the default and the most common for
			# LDAP servers.  If the mail field is not found the username
			# will be used as the email address when creating the eperson
			# object.
			#ldap.email_field = mail
			<email_field>mail</email_field>
			
			# This is the LDAP object field where the user's last name is
			# stored.  "sn" is the default and is the most common for LDAP
			# servers.  If the field is not found the field will be left
			# blank in the new eperson object.
			#ldap.surname_field = sn
			<surname_field>sn</surname_field>
			
			# This is the LDAP object field where the user's given names
			# are stored.  This may not be used or set in all LDAP instances.
			# If the field is not found the field will be left blank in the 
			# new eperson object.
			#ldap.givenname_field = givenName
			<givenname_field>givenName</givenname_field>
			
			# This is the field where the user's phone number is stored in
			# the LDAP directory.  If the field is not found the field
			# will be left blank in the new eperson object.
			#ldap.phone_field = telephoneNumber
			<phone_field>telephoneNumber</phone_field>
		-->

	</ldap>

	<!--
		#### Media Filter plugins (through PluginManager) ####
		plugin.sequence.org.dspace.app.mediafilter.MediaFilter = \
		org.dspace.app.mediafilter.PDFFilter,
		org.dspace.app.mediafilter.HTMLFilter, \
		org.dspace.app.mediafilter.WordFilter,
		org.dspace.app.mediafilter.JPEGFilter 
		# to enable branded preview: remove last line above, and uncomment 2 lines below 
		# org.dspace.app.mediafilter.WordFilter, org.dspace.app.mediafilter.JPEGFilter, \ 
		# org.dspace.app.mediafilter.BrandedPreviewJPEGFilter
	-->
	<plugin type="sequence"
		interface="org.dspace.app.mediafilter.MediaFilter">
		<class>org.dspace.app.mediafilter.PDFFilter</class>
		<class>org.dspace.app.mediafilter.HTMLFilter</class>
		<class>org.dspace.app.mediafilter.WordFilter</class>
		<class>org.dspace.app.mediafilter.JPEGFilter</class>
	</plugin>

	<!-- 
		filter.org.dspace.app.mediafilter.PDFFilter.inputFormats = Adobe PDF
		filter.org.dspace.app.mediafilter.HTMLFilter.inputFormats = HTML, Text
		filter.org.dspace.app.mediafilter.WordFilter.inputFormats = Microsoft Word
		filter.org.dspace.app.mediafilter.JPEGFilter.inputFormats = GIF, JPEG, image/png
		filter.org.dspace.app.mediafilter.BrandedPreviewJPEGFilter.inputFormats = GIF, JPEG, image/png
	-->
	<filter class="org.dspace.app.mediafilter.PDFFilter">
		<inputFormats>Adobe PDF</inputFormats>
	</filter>
	<filter class="org.dspace.app.mediafilter.HTMLFilter">
		<inputFormats>HTML</inputFormats>
	</filter>
	<filter class="org.dspace.app.mediafilter.JPEGFilter">
		<inputFormats>GIF</inputFormats>
		<inputFormats>JPEG</inputFormats>
		<inputFormats>image/png</inputFormats>
	</filter>
	<filter
		class="org.dspace.app.mediafilter.BrandedPreviewJPEGFilter">
		<inputFormats>GIF</inputFormats>
		<inputFormats>JPEG</inputFormats>
		<inputFormats>image/png</inputFormats>
	</filter>

	<!--
		#### Checksum Checker Settings #### 
		# Default dispatcher in case none specified
		plugin.single.org.dspace.checker.BitstreamDispatcher=org.dspace.checker.SimpleDispatcher
	-->
	<plugin type="single"
		interface="org.dspace.checker.BitstreamDispatcher">
		<class>org.dspace.checker.SimpleDispatcher</class>
	</plugin>

	<!--
		# check history retention
		checker.retention.default=10y
		checker.retention.CHECKSUM_MATCH=8w
	-->
	<checker>
		<retention>
			<default>10y</default>
			<CHECKSUM_MATCH>8w</CHECKSUM_MATCH>
		</retention>
	</checker>


	<!--
		Crosswalk and Packager Plugin Settings ####
		# Configure table-driven MODS dissemination crosswalk 
		# (add lower-case name for OAI-PMH) 
		crosswalk.mods.properties.MODS = crosswalks/mods.properties
		crosswalk.mods.properties.mods = crosswalks/mods.properties
		
		# Configure XSLT-driven submission crosswalk for MODS
		crosswalk.submission.MODS.stylesheet= crosswalks/mods-submission.xsl
		
		# Configure the QDCCrosswalk dissemination plugin for Qualified DC 
		# (add lower-case name for OAI-PMH) 
		crosswalk.qdc.namespace.QDC.dc = http://purl.org/dc/elements/1.1/ 
		crosswalk.qdc.namespace.QDC.dcterms = http://purl.org/dc/terms/ 
		crosswalk.qdc.schemaLocation.QDC = \
		http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd \
		http://purl.org/dc/elements/1.1/ http://dublincore.org/schemas/xmls/qdc/2006/01/06/dc.xsd
		crosswalk.qdc.properties.QDC = crosswalks/QDC.properties
		
		crosswalk.qdc.namespace.qdc.dc = http://purl.org/dc/elements/1.1/
		crosswalk.qdc.namespace.qdc.dcterms = http://purl.org/dc/terms/
		crosswalk.qdc.schemaLocation.qdc = \ http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd \
		http://purl.org/dc/elements/1.1/ http://dublincore.org/schemas/xmls/qdc/2006/01/06/dc.xsd
		crosswalk.qdc.properties.qdc = crosswalks/QDC.properties
	-->
	<crosswalk>
		<mods>
			<properties>
				<MODS>crosswalks/mods.properties</MODS>
				<mods>crosswalks/mods.properties</mods>
			</properties>
		</mods>
		<submission>
			<MODS>
				<stylesheet>crosswalks/mods-submission.xsl</stylesheet>
			</MODS>
		</submission>
		<qdc>
			<namespace>
				<QDC>
					<dc>http://purl.org/dc/elements/1.1/</dc>
					<dcterms>http://purl.org/dc/terms/</dcterms>
				</QDC>
			</namespace>
			<schemaLocation>
				<QDC>
					http://purl.org/dc/terms/
					http://dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd
					http://purl.org/dc/elements/1.1/
					http://dublincore.org/schemas/xmls/qdc/2006/01/06/dc.xsd
				</QDC>
			</schemaLocation>
			<properties>
				<QDC>crosswalks/QDC.properties</QDC>
			</properties>
			<namespace>
				<qdc>
					<dc>http://purl.org/dc/elements/1.1/</dc>
					<dcterms>http://purl.org/dc/terms/</dcterms>
				</qdc>
			</namespace>
			<schemaLocation>
				<qdc>
					http://purl.org/dc/terms/
					http://dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd
					http://purl.org/dc/elements/1.1/
					http://dublincore.org/schemas/xmls/qdc/2006/01/06/dc.xsd
				</qdc>
			</schemaLocation>
			<properties>
				<qdc>crosswalks/QDC.properties</qdc>
			</properties>
		</qdc>
	</crosswalk>

	<!-- 
		# METS ingester configuration: 
		# map of metadata type declared in mdWrap to a crosswalk plugin name: 
		mets.submission.crosswalk.DC = QDC
		
		# Option to save METS manifest in the item: (default is false)
		mets.submission.preserveManifest = false
	-->
	<mets>
		<submission>
			<crosswalk>
				<DC>QDC</DC>
			</crosswalk>
			<preserveManifest>false</preserveManifest>
		</submission>
	</mets>


	<plugin type="named"
		interface="org.dspace.content.crosswalk.IngestionCrosswalk">
		<name>PREMIS</name>
		<class>org.dspace.content.crosswalk.PREMISCrosswalk</class>
	</plugin>
	<plugin type="named"
		interface="org.dspace.content.crosswalk.IngestionCrosswalk">
		<name>NIL</name>
		<class>
			org.dspace.content.crosswalk.NullIngestionCrosswalk
		</class>
	</plugin>
	<plugin type="selfnamed"
		interface="org.dspace.content.crosswalk.IngestionCrosswalk">
		<class>
			org.dspace.content.crosswalk.XSLTIngestionCrosswalk
		</class>
	</plugin>

	<plugin type="named"
		interface="org.dspace.content.crosswalk.DisseminationCrosswalk">
		<name>DC</name>
		<name>dc</name>
		<class>
			org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk
		</class>
	</plugin>

	<plugin type="named"
		interface="org.dspace.content.crosswalk.DisseminationCrosswalk">
		<name>PREMIS</name>
		<class>org.dspace.content.crosswalk.PREMISCrosswalk</class>
	</plugin>

	<plugin type="named"
		interface="org.dspace.content.crosswalk.DisseminationCrosswalk">
		<name>METS</name>
		<name>mets</name>
		<class>
			org.dspace.content.crosswalk.METSDisseminationCrosswalk
		</class>
	</plugin>

	<plugin type="selfnamed"
		interface="org.dspace.content.crosswalk.DisseminationCrosswalk">
		<class>
			org.dspace.content.crosswalk.MODSDisseminationCrosswalk
		</class>
	</plugin>

	<plugin type="selfnamed"
		interface="org.dspace.content.crosswalk.DisseminationCrosswalk">
		<class>
			org.dspace.content.crosswalk.XSLTDisseminationCrosswalk
		</class>
	</plugin>

	<plugin type="selfnamed"
		interface="org.dspace.content.crosswalk.DisseminationCrosswalk">
		<class>org.dspace.content.crosswalk.QDCCrosswalk</class>
	</plugin>

	<!--
		Packager Plugins:
	-->
	<plugin type="named"
		interface="org.dspace.content.packager.PackageDisseminator">
		<name>METS</name>
		<name>mets</name>
		<class>
			org.dspace.content.packager.DSpaceMETSDisseminator
		</class>
	</plugin>
	<plugin type="named"
		interface="org.dspace.content.packager.PackageIngester">
		<name>Adobe PDF</name>
		<name>PDF</name>
		<class>org.dspace.content.packager.PDFPackager</class>
	</plugin>
	<plugin type="named"
		interface="org.dspace.content.packager.PackageIngester">
		<name>METS</name>
		<class>org.dspace.content.packager.DSpaceMETSIngester</class>
	</plugin>

</configuration>