text:showcase:bibtex-e:choose-style text:showcase:bibtex-e:style.default, text:showcase:bibtex-e:style.blue, text:showcase:bibtex-e:style.olive, text:showcase:bibtex-e:style.none

CSS Demo


text:showcase:bibtex-e:description1a

How the collection works

The collection configuration file (the collection's etc/collectionConfig.xml) begins with the specification groupsize 200. This groups 200 documents together into a single archive file. Bibliography collections typically have many small documents, and grouping them together prevents Greenstone's internal file structures from becoming bloated and occupying more disk space than necessary.

text:showcase:bibtex-e:description1b

Apart from the standard plugins, this collection uses BibTexPlugin, which processes references in the BibTeX format (well known to computer scientists). Two options have been set for BibTexPlugin: -OIDtype assigned -OIDmetadata Number. This means the metadata element "Number" will be used as the record identifier, instead of Greenstone's default hash identifiers. These options are available for all plugins.

  <xsl:template name="additionalHeaderContent-collection"> 
    <xsl:variable name="httpCollection"> 
      <xsl:value-of select="/page/pageResponse/collection/metadataList/metadata[@name='httpPath']"/> 
    </xsl:variable> 
	<link rel="stylesheet" href="{$httpCollection}/style/gs3-style-default-extra.css" type="text/css"  
	   title="GS3 Style" id="custom-style" charset="UTF-8"/> 
	<script src="{$httpCollection}/script/custom-script.js" type="text/javascript"> 
	</script> 
  </xsl:template> 
 
  <xsl:template name="create-banner">   
	<div class="choose_style"> 
		Choose a style: 
		<a href="#" onclick="replaceStyle('gs3-style-default-extra');return false;">Default Greenstone</a>, 
		<a href="#" onclick="replaceStyle('gs3-style-blue');return false;">Blue</a>, 
		<a href="#" onclick="replaceStyle('gs3-style-olive-purple');return false;">OlivePurple</a>,		 
		<a href="#" onclick="replaceStyle('');return false;">None</a> 
		</div> 
    <div id="gs_banner" class="ui-widget-header ui-corner-bottom">	     
      <div id="titlesearchcontainer"> 
	<xsl:call-template name="page-title-area"/>	 
	<xsl:call-template name="quick-search-area"/> 
	<div style="clear:both;"><xsl:text> </xsl:text></div>	 
      </div> 
      <xsl:call-template name="browsing-tabs"/>	 
    </div> 
  </xsl:template>

Fielded searching, with a form-based interface, is selected by format SearchTypes "form,plain" in the configuration file. In fact, a plain textual full-text search index is included in this collection as well (since form comes first, it is the default interface; you reach the plain search through the Preferences page).

The buildtype option shows that the default search engine mgpp is used. The indexes line specifies indexes for "text", and "metadata". In this case, "text" will be the original BibTeX record. "metadata" is a special keyword signifying that an index should be built for any metadata item found in the collection. Thus when the "field" menus in the collection's search page are pulled down, they show full records followed by an entry for each metadata element. In the collection's resources/collectionConfig.properties file, collection-level metadata collectionmeta can be specified for any index to determine what it is called (except for metadata, which produces many menu items). In this case, the collectionConfig.properties file specifies that the text index (referred to by collection's configuration file, collectionConfig.xml) should be named "full records" because it contains the original bibliographic record.

View this collection's configuration and other files: