##### Properties file for configuring a servlet
##### (Note, edit the resources/web/servlet.properties.in file, not resources/web/servlet.properties.svn file nor web/WEB-INF/classes/servlet.properties)
##### The name of this file is specified in resources/web/servlets.xml.in
##### So you can copy and rename the file if you want different params for
##### different servlets - The name needs to match servlet-*.properties.in
#####  Then update resources/web/servlets.xml.in - set the new name in the properties_file init-param (without the .in suffix)
##### If you only want a few properties different bewteen servlets, instead
##### of making separate properties files, you can comment out the differing
##### params here, and add them as init-params in your resources/web/servlets.xml.in

##### If you modify this servlet.properties.in file, or create a new copy,
##### you need to restart the library


# If you want to add new properties here, they will be accessible to you in
# the XSLT by adding a new <xsl:param name="property name"/> to the list in
# web/interfaces/default/transform/gslib.xsl

# does this servlet provide the favourites functionality? true/false
favouritebasket=true
# does this servlet provide the documentbasket functionality? true/false. Currently not available
documentbasket=false
# Does this servlet display the web-gli link? true/false
webglilink=true

# If you want to use recpatcha on your site, eg in verify page or in user
# admin pages, replace these testing keys with the real ones for your site
recaptcha.site_key=6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI
recaptcha.secret_key=6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe

# Do you want the cookie consent manager in the library?
# The cookie consent manager is a component of the default interface that
# alerts the end user to Greenstone's cookie usage. It also allows them to
# consent to non-essential cookies.
# It can be customised by editing the 'cookieconsent-init.js' file in the
# default interface's 'js' folder.
cookie_consent=true

# By default, Greenstone will use its context as the cookie_path (greenstone.context in build.properties)
# If you need to change it, eg you are proxying to a different url with Apache
# uncomment and set the cookie_path value below.
# If you are mapping to an address without the context part (eg my-site.org/library), then the cookie_path will be /
# Note, cookie_path must start with /
#cookie_path=

# Google Signin
# If you want to allow signing in to your library using Google, you
# will need to set your client id in build.properties.
# This will be copied here. Comment this line out if you
# have a client id specified in build.properties, but you don't want
# google sign in for this particular servlet
googlesignin_client_id=@googlesigninclientid@

# Google Maps Platform
# If your documents have Latitude+Longitude or Coordinate metadata, you can display their locations on a google map
# Add <gsf:option mapEnabled="true"/> to <search>, <browse> and/or <display> elements in collectionConfig.xml to have the map displayed on the search results pages, classifier browsing pages, and document display pages, respectively.
# Then set up a google maps Javascript API Key (use a demo key to get started) and enter it below.
# Google Maps Documentation: https://developers.google.com/maps/documentation/
# Javascript API Documentation: https://developers.google.com/maps/documentation/javascript
# Getting a Javascript API Key: https://developers.google.com/maps/documentation/javascript/get-api-key
googlemaps_api_key=

# Google Tag 
# If you want to add a google tag to all your pages, add the tag id here
# This uses the gstag.js mechanism - no need to use TagManager
# used by Google Analytics, Google Ads, Google Floodlight
# Google Tag Documentation: https://developers.google.com/tag-platform/devguides
# How to find your Tag ID: https://developers.google.com/tag-platform/gtagjs - see the section 'Add the Google tag to your website'
google_tag_id=