Changeset 36518


Ignore:
Timestamp:
2022-08-26T19:23:36+12:00 (20 months ago)
Author:
anupama
Message:

Now that I've checked the first 4 DEC collections just committed create no GS3 about page display issue or GTI translation issue when colons are escaped in their collectionConfig.properties files, updating the remaining DEC collections with this change that was found to be necessary for GTI when attempting to translate garish-e GS3 DEC collection descriptions (gs3-dec-col-cfgs module)

Location:
documented-examples/trunk
Files:
11 edited

Legend:

Unmodified
Added
Removed

  • documented-examples/trunk/gsarch-e/resources/collectionConfig.properties

    r36510 r36518  
    2323description6=<p>The third classifier is a <i>DateList</i>, which allows selection by month and year.</p>
    2424
    25 description7=<p>Finally, the <tt>documentHeading</tt> is overridden to show the header fields: <i>FromName</i>, <i>DateText</i>, <i>Subject</i>, <i>InReplyTo</i> (as the default documentHeading would not show the <i>InReplyTo</i> Field, nor to label the fields). The default <tt>documentContent</tt> already displays the message text (with the call to &lt;xsl:call-template name="documentNodeText"/&gt;). <i>FromName</i> is linked to a search on that name, while <i>InReplyTo</i> links to the email message that it refers to.</p>
     25description7=<p>Finally, the <tt>documentHeading</tt> is overridden to show the header fields\: <i>FromName</i>, <i>DateText</i>, <i>Subject</i>, <i>InReplyTo</i> (as the default documentHeading would not show the <i>InReplyTo</i> Field, nor to label the fields). The default <tt>documentContent</tt> already displays the message text (with the call to &lt;xsl\:call-template name="documentNodeText"/&gt;). <i>FromName</i> is linked to a search on that name, while <i>InReplyTo</i> links to the email message that it refers to.</p>

  • documented-examples/trunk/image-e/resources/collectionConfig.properties

    r36510 r36518  
    1313description2=<h3>How the collection works</h3><p><a href="library/collection/image-e/document/D2">Here</a> is a sample document in the collection. The configuration file, <tt>collectionConfig.xml</tt>, specifies no indexes, so the search button is suppressed.</p>
    1414
    15 description3=<p>There is only one plugin, <i>ImagePlugin</i>, aside from the others that are always present (crucially <i>GreenstoneXMLPlugin</i>, <i>MetadataXMLPlugin</i>, <i>ArchivesInfPlugin</i>, <i>DirectoryPlugin</i>). <i>ImagePlugin</i> relies on the existence of two programs from the ImageMagick suite (<a href="http://www.imagemagick.org">www.imagemagick.org</a>): <i>convert</i> and <i>identify</i>. Greenstone 3 binaries come bundled with Imagemagick as one of the components that can be optionally installed. Greenstone will not be able to build the collection correctly unless an ImageMagick is installed on your computer.</p>
     15description3=<p>There is only one plugin, <i>ImagePlugin</i>, aside from the others that are always present (crucially <i>GreenstoneXMLPlugin</i>, <i>MetadataXMLPlugin</i>, <i>ArchivesInfPlugin</i>, <i>DirectoryPlugin</i>). <i>ImagePlugin</i> relies on the existence of two programs from the ImageMagick suite (<a href="http\://www.imagemagick.org">www.imagemagick.org</a>)\: <i>convert</i> and <i>identify</i>. Greenstone 3 binaries come bundled with Imagemagick as one of the components that can be optionally installed. Greenstone will not be able to build the collection correctly unless an ImageMagick is installed on your computer.</p>
    1616
    17 description4=<p><i>ImagePlugin</i> automatically creates a thumbnail and generates the following metadata for each image in the collection:  <blockquote> <table border=0 cellspacing=0> <tr><td width=125 valign=top><i>Image</i></td><td>Name of file containing the image <tr> <tr><td valign=top><i>ImageWidth</i></td><td>Width of image (in pixels) <tr> <tr><td valign=top><i>ImageHeight</i></td><td>Height of image (in pixels) <tr> <tr><td valign=top><i>Thumb</i></td><td> Name of gif file containing thumbnail of image <tr> <tr><td valign=top><i>ThumbWidth</i></td><td>Width of thumbnail image (in pixels) <tr> <tr><td valign=top><i>ThumbHeight</i></td><td>Height of thumbnail image (in pixels) <tr> <tr><td valign=top><i>thumbicon</i></td><td>Full pathname specification of thumbnail image <tr> <tr><td valign=top><i>assocfilepath</i></td><td>Pathname of image directory in the collection\'s <i>assoc</i> directory <tr> </table> </blockquote></p>
     17description4=<p><i>ImagePlugin</i> automatically creates a thumbnail and generates the following metadata for each image in the collection\:  <blockquote> <table border=0 cellspacing=0> <tr><td width=125 valign=top><i>Image</i></td><td>Name of file containing the image <tr> <tr><td valign=top><i>ImageWidth</i></td><td>Width of image (in pixels) <tr> <tr><td valign=top><i>ImageHeight</i></td><td>Height of image (in pixels) <tr> <tr><td valign=top><i>Thumb</i></td><td> Name of gif file containing thumbnail of image <tr> <tr><td valign=top><i>ThumbWidth</i></td><td>Width of thumbnail image (in pixels) <tr> <tr><td valign=top><i>ThumbHeight</i></td><td>Height of thumbnail image (in pixels) <tr> <tr><td valign=top><i>thumbicon</i></td><td>Full pathname specification of thumbnail image <tr> <tr><td valign=top><i>assocfilepath</i></td><td>Pathname of image directory in the collection\'s <i>assoc</i> directory <tr> </table> </blockquote></p>
    1818
    1919description5=<p>The image is stored as an "associated file" in the <i>assoc</i> subdirectory of the collection\'s <i>index</i> directory. (<i>Index</i> is where all files necessary to serve the collection are placed, to make it self-contained.) For any document, its thumbnail and image are both in a subdirectory whose filename is given by <i>assocfilepath</i>. The metadata element <i>thumbicon</i> is set to the full pathname specification of the thumbnail image, and can be used in the same way as <i>srcicon</i> (see the MSWord and PDF demonstration collection).</p>
    2020
    21 description6=<p>The <tt>browse</tt> format statement in the collection configuration file, <tt>collectionConfig.xml</tt>, dictates how the document will appear, and <a href="library/collection/image-e/document/D2">this</a> is the result. There is no document text (if there were, it would be producible by <i>&lt;gsf:metadata name="rawtext"/&gt;</i> in format statements). What is shown is the image itself, along with some metadata extracted from it.</p>
     21description6=<p>The <tt>browse</tt> format statement in the collection configuration file, <tt>collectionConfig.xml</tt>, dictates how the document will appear, and <a href="library/collection/image-e/document/D2">this</a> is the result. There is no document text (if there were, it would be producible by <i>&lt;gsf\:metadata name="rawtext"/&gt;</i> in format statements). What is shown is the image itself, along with some metadata extracted from it.</p>
    2222
    2323description7=<p>The configuration file specifies one classifier, a <i>List</i> based on <i>Image</i> metadata, shown <a href="library/collection/image-e/browse/CL1">here</a>. The format statement shows the thumbnail image along with some metadata. (Any other classifiers would have the same format, since this statement does not name the classifier.)</p>
    … …  
    2727description9=<p>The reason is to save communication bandwidth by not sending large images when small ones would do.</p>
    2828
    29 description10=<p>For a more comprehensive image collection, see the <a href="http://www.nzdl.org/cgi-bin/library?a=p&sa=about&c=aircraft">kiwi aircraft images</a> in the New Zealand Digital Library. The structure of this collection is quite different, however: it is a collection of web pages that include many images along with the text. The HTML plugin <i>HTMLPlugin</i> also processes image files, but it does so in a different way from ImagePlugin (for example, it does not produce the metadata described above).</p>
     29description10=<p>For a more comprehensive image collection, see the <a href="http\://www.nzdl.org/cgi-bin/library?a=p&sa=about&c=aircraft">kiwi aircraft images</a> in the New Zealand Digital Library. The structure of this collection is quite different, however\: it is a collection of web pages that include many images along with the text. The HTML plugin <i>HTMLPlugin</i> also processes image files, but it does so in a different way from ImagePlugin (for example, it does not produce the metadata described above).</p>

  • documented-examples/trunk/isis-e/resources/collectionConfig.properties

    r36475 r36518  
    3333Edition^all=edition     
    3434
    35 shortDescription=<p>This collection shows a <a href="http://portal.unesco.org/ci/ev.php?URL_ID=2071&amp;URL_DO=DO_TOPIC&amp;URL_SECTION=201">CDS/ISIS</a> database of bibliography entries.</p>
     35shortDescription=<p>This collection shows a <a href="http\://portal.unesco.org/ci/ev.php?URL_ID=2071&amp;URL_DO=DO_TOPIC&amp;URL_SECTION=201">CDS/ISIS</a> database of bibliography entries.</p>
    3636
    37 description1=<h3>How the collection works</h3><p>The collection configuration file, <tt>etc/collectionConfig.xml</tt> specifies the ISISPlugin plugin, which processes CDS/ISIS databases. These databases have several files, but ISISPlugin uses just three: CDS.fdt (where CDS is the name of the database), containing the field names used in the database, CDF.xrf (a cross-reference file), and CDS.mst, containing the actual records. Whenever ISISPlugin encounters an ".mst" file, it looks for the corresponding ".fdt" and ".xrf" files. In this case the plugin has been given an <i>input_encoding</i> argument because some entries in the database contain extended characters (in a form that was used in early versions of the DOS operating system). It has also been given a subfield separator argument, whose purpose is explained below. The <i>-OIDtype incremental</i> plugin option was used to give identifiers that are consistent across different operating systems (which may not happen with HASH identifiers), so that we can link to a document in this description.</p>
     37description1=<h3>How the collection works</h3><p>The collection configuration file, <tt>etc/collectionConfig.xml</tt> specifies the ISISPlugin plugin, which processes CDS/ISIS databases. These databases have several files, but ISISPlugin uses just three\: CDS.fdt (where CDS is the name of the database), containing the field names used in the database, CDF.xrf (a cross-reference file), and CDS.mst, containing the actual records. Whenever ISISPlugin encounters an ".mst" file, it looks for the corresponding ".fdt" and ".xrf" files. In this case the plugin has been given an <i>input_encoding</i> argument because some entries in the database contain extended characters (in a form that was used in early versions of the DOS operating system). It has also been given a subfield separator argument, whose purpose is explained below. The <i>-OIDtype incremental</i> plugin option was used to give identifiers that are consistent across different operating systems (which may not happen with HASH identifiers), so that we can link to a document in this description.</p>
    3838
    3939description2=<p>Like the <a href="library/collection/bibtex-e/page/about">bibliography collection</a>, this collection incorporates a <a href="library/collection/isis-e/search/FieldQuery">form-based search interface</a> that allows fielded searching. This is specified by the line <i>format SearchTypes "form,plain"</i> in the configuration file; the <i>plain</i> argument ensures that there is a plain textual full-text search feature as well (which can be selected from the <a href="library/page/pref">Preferences</a> page). The <i>&lt;importOption name="groupsize" value="100"/&gt;</i> line in the <tt>collectionConfig.xml</tt> file puts documents together into groups of 100 (as explained in the <a href="library/collection/bibtex-e/page/about">bibliography collection</a>).</p>

  • documented-examples/trunk/lomdemo-e/resources/collectionConfig.properties

    r36510 r36518  
    1212description1=<p>Traditional educational learning object repositories base searching and browsing around the provided metadata. This demonstration collection goes one step further and provides <i>full-text</i> indexing of the on-line resources, where possible.</p>
    1313
    14 description2=<p>Browse around the collection\'s items ordered by subject then title, or view the items chronologically. Alternatively search the text or titles of the items in the collection, optionally restricted to arts or science. When you view an item from the collection various views of it are available. You start by viewing its Learning Object Metadata (LOM) record in a tabulated form and divided into sections: these sections can be expanded or contracted to reveal more or less information as desired. Use the tabs at the top of the table to change the view of the learning object. There will always be a tab for "XML Record" which displays the metadata in its original IEEE LOM format. Depending on whether or not the learning object references an on-line resource that is available for indexing, a third tab may be present that displays the source document.</p>
     14description2=<p>Browse around the collection\'s items ordered by subject then title, or view the items chronologically. Alternatively search the text or titles of the items in the collection, optionally restricted to arts or science. When you view an item from the collection various views of it are available. You start by viewing its Learning Object Metadata (LOM) record in a tabulated form and divided into sections\: these sections can be expanded or contracted to reveal more or less information as desired. Use the tabs at the top of the table to change the view of the learning object. There will always be a tab for "XML Record" which displays the metadata in its original IEEE LOM format. Depending on whether or not the learning object references an on-line resource that is available for indexing, a third tab may be present that displays the source document.</p>
    1515
    1616description3=<h3>How the collection works</h3><p>The records were exported from the Calgary Repository in LOM format. LOMPlugin is used to process the records. Using the <tt>-download_srcdocs</tt> option to the plugin will search for <tt>general^identifier^entry</tt> or <tt>technical^location</tt>, and attempt to download the source document into a <i>_gsdldown.all</i> folder (<tt>import/arts/_gsdldown.all</tt>) in the same folder as the LOM record.</p>
    1717
    18 description4=<p>In porting the lomdemo-e collection from Greenstone 2 (GS2) to Greenstone 3, the predefined GS2 macros of <i>_httpopenmdicon_</i> and <i>httpclosemdicon_</i>, used to show and hide sections of the tabular display of LOM metadata, needed to be defined in <tt>siteConfig.xml</tt> by inserting the following 2 lines into the file: \
     18description4=<p>In porting the lomdemo-e collection from Greenstone 2 (GS2) to Greenstone 3, the predefined GS2 macros of <i>_httpopenmdicon_</i> and <i>httpclosemdicon_</i>, used to show and hide sections of the tabular display of LOM metadata, needed to be defined in <tt>siteConfig.xml</tt> by inserting the following 2 lines into the file\: \
    1919<pre>\
    2020&lt;replace macro="_httpopenmdicon_" scope="metadata" text="sites/localsite/collect/lomdemo-e/images/open.gif" data-img-path="sites/localsite/collect/lomdemo-e/images/" resolve="false"/&gt; \n\
    … …  
    2323</p>
    2424
    25 description5=<p>The open and close icon images themselves were then placed into the location indicated above: <tt>lomdemo-e/images/</tt> subfolder. The JavaScript to show and hide associated sections of LOM metadata when the close and open icons are clicked is defined in <tt>lomdemo-e/script/lomscript.js</tt>, and the CSS styling rules for the tabular display of the LOM metadata is in <tt>lomdemo-e/style/lom-style.css</tt>.</p>
     25description5=<p>The open and close icon images themselves were then placed into the location indicated above\: <tt>lomdemo-e/images/</tt> subfolder. The JavaScript to show and hide associated sections of LOM metadata when the close and open icons are clicked is defined in <tt>lomdemo-e/script/lomscript.js</tt>, and the CSS styling rules for the tabular display of the LOM metadata is in <tt>lomdemo-e/style/lom-style.css</tt>.</p>

  • documented-examples/trunk/manifest-demo-e/resources/collectionConfig.properties

    r36510 r36518  
    88dls.Subject=Subjects
    99
    10 textdate=publication date:
    11 textnumpages=no. of pages:
    12 textsource=source ref:
     10textdate=publication date\:
     11textnumpages=no. of pages\:
     12textsource=source ref\:
    1313
    1414shortDescription=<p>This demonstration collection contains the same material as the original Greenstone demo collection. In addition it has some predefined manifest files, to show off their use with incremental building.</p>
    … …  
    2727description0=<h3>Instructions</h3><br /><p>0. Run setup/source setup.bash in top level before starting.</p><br />
    2828
    29 description1=<p>1. Build the collection initially:<br /> \n\
     29description1=<p>1. Build the collection initially\:<br /> \n\
    3030<pre>perl -S import.pl -site localsite documented-examples/manifest-demo-e \n\
    3131perl -S buildcol.pl -site localsite -activate documented-examples/manifest-demo-e</pre> \n\
    32 <i>Note:</i> If you forget to pass in the <tt>-activate</tt> flag to the <tt>buildcol</tt> command, use a file explorer to go into your Greenstone 3 installations\'s <tt>web/sites/localsite/collect/documented-examples/manifest-demo-e</tt> folder, and rename the <tt>building</tt> subfolder there to <tt>index</tt>.)<br /> \n\
     32<i>Note\:</i> If you forget to pass in the <tt>-activate</tt> flag to the <tt>buildcol</tt> command, use a file explorer to go into your Greenstone 3 installations\'s <tt>web/sites/localsite/collect/documented-examples/manifest-demo-e</tt> folder, and rename the <tt>building</tt> subfolder there to <tt>index</tt>.)<br /> \n\
    3333<br /> \n\
    3434Preview the collection. Contains 8 documents, 5 from BOSTID and 3 from EC Courier.</p><br />

  • documented-examples/trunk/marc-e/resources/collectionConfig.properties

    r36510 r36518  
    44sampleoid=D0s156
    55
    6 shortDescription=<p>This collection, which contains _about:numdocs_ MARC entries, is based on the MARC records of working papers published by <a href="http://www.cs.waikato.ac.nz">Computer Science Department</a> at <a href="http://www.waikato.ac.nz">the University of Waikato</a>. <a href="_sampleoid_">Here</a> is a sample document in the collection.</p>
     6shortDescription=<p>This collection, which contains _about\:numdocs_ MARC entries, is based on the MARC records of working papers published by <a href="http\://www.cs.waikato.ac.nz">Computer Science Department</a> at <a href="http\://www.waikato.ac.nz">the University of Waikato</a>. <a href="_sampleoid_">Here</a> is a sample document in the collection.</p>
    77
    88description1=<h3>How the collection works</h3><p>The configuration file, <tt>collectionConfig.xml</tt>, uses <i>MARCPlugin</i> to process the MARC records, as well as the standard plugins. There are three classifiers, based on <i>dc.Title</i>, <i>dc.Creator</i>, and <i>dc.Subject</i> metadata. The <i>Title</i> classifier uses AZList, while the other two use AZCompactList, which groups items with the same metadata into a bookshelf. The <i>-removesuffix</i> argument for the <i>Title</i> and <i>Creator</i> classifiers removes suffixes from the metadata string (<i>dc.Title</i> and <i>dc.Creator</i> respectively). This is specified as a PERL regular expression, and trims characters (such as trailing punctuation) from the strings for display.</p>
    99
    10 description2=<p>The <i>VList</i> format statement controls the display of search results and all classifiers. For bookshelves, the number of leaf documents is displayed on the right-hand side. For documents, <i>dc.Title</i> is displayed, along with <i>dc.Creator</i> and <i>dc.Publisher</i>. <i>[sibling:dc.Creator]</i> is used as dc.Creator has multiple values, and specifies that all values be output, not just the first one.</p>
     10description2=<p>The <i>VList</i> format statement controls the display of search results and all classifiers. For bookshelves, the number of leaf documents is displayed on the right-hand side. For documents, <i>dc.Title</i> is displayed, along with <i>dc.Creator</i> and <i>dc.Publisher</i>. <i>[sibling\:dc.Creator]</i> is used as dc.Creator has multiple values, and specifies that all values be output, not just the first one.</p>
    1111
    1212description3=<p>The MARC plugin uses a special file to map MARC field numbers to Greenstone-style metadata. This file resides in the greenstone3 installation folder\'s <i>gs2build/etc</i> directory, and is called <tt>marc2dc.txt</tt>. It lists the correspondences between MARC field numbers and Greenstone metadata. Any MARC fields that are not listed simply do not appear as metadata, though they are still present in the Greenstone document. Each line in the file has the format <blockquote> &lt;MARC field number&gt; -&gt; GreenstoneMetadataName </blockquote> Lines in the file that begin with "\#" are comments.</p>
    1313
    14 description4=<p>The standard version of this file is loosely based on the MARC to Dublin Core mapping found at <a href="http://www.loc.gov/marc/marc2dc.html">http\://www.loc.gov/marc/marc2dc.html</a> (which assumes USMARC/MARC21).</p>
     14description4=<p>The standard version of this file is loosely based on the MARC to Dublin Core mapping found at <a href="http\://www.loc.gov/marc/marc2dc.html">http\://www.loc.gov/marc/marc2dc.html</a> (which assumes USMARC/MARC21).</p>
    1515
    1616description5=<p>Multiple MARC fields may map to a single Dublin Core field. For example, fields 720 ("Uncontrolled name"), 100 ("Personal name"), 110 ("Corporate name") and 111 ("Meeting name") all map to <i>dc.Creator</i>. Actual MARC records normally define only one of these fields, and anyway Greenstone allows multi-valued metadata.</p>
    1717
    18 description6=<p>Some mappings are dependent on subfields. For example, MARC field 260 contains information about publication and distribution. Subfields "c" (Date of Publication) and "g" (Date of manufacture) are mapped to <i>dc.Date</i>, using the following mapping line: <blockquote> 260$c$g -&gt; dc.Date </blockquote>  Greenstone also provides a file for mapping MARC to <b>qualified</b> dublin core: in your Greenstone 3 installation folder\'s <tt>gs2build/etc/marc2qdc.txt</tt>. This can be used by the MARC plugin by setting the <i>-metadata_mapping_file</i> option to "marc2qdc.txt".</p>
     18description6=<p>Some mappings are dependent on subfields. For example, MARC field 260 contains information about publication and distribution. Subfields "c" (Date of Publication) and "g" (Date of manufacture) are mapped to <i>dc.Date</i>, using the following mapping line\: <blockquote> 260$c$g -&gt; dc.Date </blockquote>  Greenstone also provides a file for mapping MARC to <b>qualified</b> dublin core\: in your Greenstone 3 installation folder\'s <tt>gs2build/etc/marc2qdc.txt</tt>. This can be used by the MARC plugin by setting the <i>-metadata_mapping_file</i> option to "marc2qdc.txt".</p>

  • documented-examples/trunk/oai-e/resources/collectionConfig.properties

    r36510 r36518  
    1111
    1212
    13 shortDescription=<p>This collection demonstrates Greenstone\'s <i>ImportFrom</i> feature. Using the <a href="http://www.openarchives.org">Open Archive Protocol</a> (version 1.1), it retrieves metadata from <a href="http://rocky.dlib.vt.edu/~jcdlpix">rocky.dlib.vt.edu/~jcdlpix</a>, a collection of photographs taken at the inaugural <a href="http://www.acm.org/jcdl/jcdl01/">Joint Conference on Digital Libraries</a>. A Greenstone collection is built from the records exported from this OAI data provider. The implementation is flexible enough to cope with the minor syntax differences between OAI 1.1 and OAI 2.0.</p>
     13shortDescription=<p>This collection demonstrates Greenstone\'s <i>ImportFrom</i> feature. Using the <a href="http\://www.openarchives.org">Open Archive Protocol</a> (version 1.1), it retrieves metadata from <a href="http\://rocky.dlib.vt.edu/~jcdlpix">rocky.dlib.vt.edu/~jcdlpix</a>, a collection of photographs taken at the inaugural <a href="http\://www.acm.org/jcdl/jcdl01/">Joint Conference on Digital Libraries</a>. A Greenstone collection is built from the records exported from this OAI data provider. The implementation is flexible enough to cope with the minor syntax differences between OAI 1.1 and OAI 2.0.</p>
    1414
    15 description1=<h3>How the collection works</h3><p>The collection configuration file, <tt>collectionConfig.xml</tt>, includes an <i>acquire</i> line that is interpreted by a special program called <i>importfrom.pl</i>. Like other Greenstone programs, this takes as argument the name of the collection, and provides a summary of other arguments when invoked with argument <i>-help</i>. It reads the collection configuration file, finds the acquire line, and processes it. In this case, it is run with the command: <pre> importfrom.pl oai-e </pre> (the collection\'s name is <i>oai-e</i>).</p>
     15description1=<h3>How the collection works</h3><p>The collection configuration file, <tt>collectionConfig.xml</tt>, includes an <i>acquire</i> line that is interpreted by a special program called <i>importfrom.pl</i>. Like other Greenstone programs, this takes as argument the name of the collection, and provides a summary of other arguments when invoked with argument <i>-help</i>. It reads the collection configuration file, finds the acquire line, and processes it. In this case, it is run with the command\: <pre> importfrom.pl oai-e </pre> (the collection\'s name is <i>oai-e</i>).</p>
    1616
    1717description2=<p>The <i>acquire</i> line in the configuration file specifies the OAI protocol and gives the base URL of an OAI repository. The <i>importfrom</i> program downloads all the metadata in that repository into the collection\'s <i>import</i> directory. The <i>getdoc</i> argument instructs it to also download the collection\'s source documents, whose URLs are given in each document\'s Dublin Core <i>Identifier</i> field (this is a common convention). The metadata files, which each contain an XML record for one source document, are placed in the <i>import</i> file structure along with the documents themselves, and the document filename is the same as the filename in the URL. The <i>Identifier</i> field is overridden to give the local filename, and its original value is retained in a new field called <i>OrigURL</i>.</p>
    … …  
    1919description3=<p>This <i>oai-e</i> collection\'s own <tt>etc/oai.txt</tt> is an example of a downloaded metadata file.</p>
    2020
    21 description4=<p>Once the OAI information has been imported, the collection is processed in the usual way. Besides the four standard plugins (GreenstoneXMLPlugin, MetadataXMLPlugin, ArchivesInfPlugin and DirectoryPlugin), the configuration file specifies the OAI plugin, which processes OAI metadata, and the image plugin, because in this case the collection\'s source documents are image files. The OAI plugin has been supplied with an <i>input_encoding</i> argument because data in this archive contains extended characters. It also has a <i>default_language</i> argument. Greenstone normally determines the language of documents automatically, but these metadata records are too small for this to be done reliably: hence English is specified explicitly in the <i>language</i> argument. The OAI plugin parses the metadata and passes it to the appropriate source document file, which is then processed by an appropriate plugin -- in this case <i>ImagePlugin</i>. This plugin specifies the resolution for the screen versions of the images.</p>
     21description4=<p>Once the OAI information has been imported, the collection is processed in the usual way. Besides the four standard plugins (GreenstoneXMLPlugin, MetadataXMLPlugin, ArchivesInfPlugin and DirectoryPlugin), the configuration file specifies the OAI plugin, which processes OAI metadata, and the image plugin, because in this case the collection\'s source documents are image files. The OAI plugin has been supplied with an <i>input_encoding</i> argument because data in this archive contains extended characters. It also has a <i>default_language</i> argument. Greenstone normally determines the language of documents automatically, but these metadata records are too small for this to be done reliably\: hence English is specified explicitly in the <i>language</i> argument. The OAI plugin parses the metadata and passes it to the appropriate source document file, which is then processed by an appropriate plugin -- in this case <i>ImagePlugin</i>. This plugin specifies the resolution for the screen versions of the images.</p>
    2222
    2323description5=<p>Extracted metadata from OAI records are mapped to Dublin Core Metadata Set by default. As a result, classifiers and indexes in this collection are built with Dublin meatadata elements.</p>

  • documented-examples/trunk/oai-e/resources/collectionConfig.properties.template

    r36307 r36518  
    1313search/TextQuery?qs=1&rt=rd&s1.level=&startPage=1&s1.query=cat&s1.index=dte
    1414
    15 http://localhost:8383/greenstone3/library/collection/gsarch-e/search/TextQuery?qs=1&rt=rd&s1.level=&startPage=1&s1.query=%22cat+and+dog%22&s1.index=dte
     15http\://localhost\:8383/greenstone3/library/collection/gsarch-e/search/TextQuery?qs=1&rt=rd&s1.level=&startPage=1&s1.query=%22cat+and+dog%22&s1.index=dte
    1616
    1717
    … …  
    2222
    2323
    24         <td><b><gsf:link type="document"><gsf:metadata name="Subject"/></gsf:link></b><br/><gsf:displayItem name="From"/>:<gsf:metadata name="FromName"/> (<a href="_httpquery_&amp;q=&amp;h=dfr"><gsf:displayItem name="SearchBySender"/></a>)<br/><gsf:displayItem name="Date"/>:<gsf:metadata name="DateText"/></td>
     24        <td><b><gsf\:link type="document"><gsf\:metadata name="Subject"/></gsf\:link></b><br/><gsf\:displayItem name="From"/>\:<gsf\:metadata name="FromName"/> (<a href="_httpquery_&amp;q=&amp;h=dfr"><gsf\:displayItem name="SearchBySender"/></a>)<br/><gsf\:displayItem name="Date"/>\:<gsf\:metadata name="DateText"/></td>
    2525       
    2626       
    2727       
    28         <a><xsl:attribute name="href"><gsf:metadata name="httpPath" type="collection"/>/index/assoc/<gsf:metadata name="archivedir"/>/<gsf:metadata name="srclinkFile"/>#search=&amp;quot;<gsf:cgi-param name="query"/>&amp;quot;</xsl:attribute>src doc link with query highlighting</a>
     28        <a><xsl\:attribute name="href"><gsf\:metadata name="httpPath" type="collection"/>/index/assoc/<gsf\:metadata name="archivedir"/>/<gsf\:metadata name="srclinkFile"/>#search=&amp;quot;<gsf\:cgi-param name="query"/>&amp;quot;</xsl\:attribute>src doc link with query highlighting</a>
    2929       
    30         <td><b><gsf:link type="document"><gsf:metadata name="Subject"/></gsf:link></b><br/><gsf:displayItem name="From"/>:<gsf:metadata name="FromName"/> (
    31         <a><xsl:attribute name="href"><gsf:metadata name="httpPath" type="collection"/>/search/TextQuery?qs=1&amp;rt=rd&amp;s1.level=&amp;startPage=1&amp;s1.index=dfr&amp;s1.query=&amp;quot;<gsf:cgi-param name="query"/>&amp;quot;</xsl:attribute><gsf:displayItem name="SearchBySender"/></a>
     30        <td><b><gsf\:link type="document"><gsf\:metadata name="Subject"/></gsf\:link></b><br/><gsf\:displayItem name="From"/>\:<gsf\:metadata name="FromName"/> (
     31        <a><xsl\:attribute name="href"><gsf\:metadata name="httpPath" type="collection"/>/search/TextQuery?qs=1&amp;rt=rd&amp;s1.level=&amp;startPage=1&amp;s1.index=dfr&amp;s1.query=&amp;quot;<gsf\:cgi-param name="query"/>&amp;quot;</xsl\:attribute><gsf\:displayItem name="SearchBySender"/></a>
    3232       
    3333       
    34           <td><b><gsf:link type="document"><gsf:metadata name="Subject"/></gsf:link></b><br/><gsf:displayItem name="From"/>:<gsf:metadata name="FromName"/> (<a><xsl:attribute name="href">library/collection/gsarch-e/search/TextQuery?qs=1&amp;rt=rd&amp;s1.level=&amp;startPage=1&amp;s1.index=dfr&amp;s1.query=&amp;quot;<gsf:metadata name="FromName"/>&amp;quot;</xsl:attribute><gsf:displayItem name="SearchBySender"/></a>)<br/><gsf:displayItem name="Date"/>:<gsf:metadata name="DateText"/></td>
     34          <td><b><gsf\:link type="document"><gsf\:metadata name="Subject"/></gsf\:link></b><br/><gsf\:displayItem name="From"/>\:<gsf\:metadata name="FromName"/> (<a><xsl\:attribute name="href">library/collection/gsarch-e/search/TextQuery?qs=1&amp;rt=rd&amp;s1.level=&amp;startPage=1&amp;s1.index=dfr&amp;s1.query=&amp;quot;<gsf\:metadata name="FromName"/>&amp;quot;</xsl\:attribute><gsf\:displayItem name="SearchBySender"/></a>)<br/><gsf\:displayItem name="Date"/>\:<gsf\:metadata name="DateText"/></td>
    3535         
    3636         
    37           <xslt:value-of disable-output-escaping="yes" select="/page/pageRequest/paramList/param[@name='c']/@value" />
    38           <xslt:value-of disable-output-escaping="yes" select="/page/pageResponse/interfaceOptions/option[@name='library_name']/@value" />
     37          <xslt\:value-of disable-output-escaping="yes" select="/page/pageRequest/paramList/param[@name='c']/@value" />
     38          <xslt\:value-of disable-output-escaping="yes" select="/page/pageResponse/interfaceOptions/option[@name='library_name']/@value" />
    3939         
    40           <a><xsl:attribute name="href"><xsl:value-of disable-output-escaping="yes" select="/page/pageResponse/interfaceOptions/option[@name='library_name']/@value" />/collection/<xsl:value-of disable-output-escaping="yes" select="/page/pageRequest/paramList/param[@name='c']/@value" />/search/TextQuery?qs=1&amp;rt=rd&amp;s1.level=&amp;startPage=1&amp;s1.index=dfr&amp;s1.query=&amp;quot;<gsf:metadata name="FromName"/>&amp;quot;</xsl:attribute><gsf:displayItem name="SearchBySender"/></a>
     40          <a><xsl\:attribute name="href"><xsl\:value-of disable-output-escaping="yes" select="/page/pageResponse/interfaceOptions/option[@name='library_name']/@value" />/collection/<xsl\:value-of disable-output-escaping="yes" select="/page/pageRequest/paramList/param[@name='c']/@value" />/search/TextQuery?qs=1&amp;rt=rd&amp;s1.level=&amp;startPage=1&amp;s1.index=dfr&amp;s1.query=&amp;quot;<gsf\:metadata name="FromName"/>&amp;quot;</xsl\:attribute><gsf\:displayItem name="SearchBySender"/></a>
    4141         
    4242         

  • documented-examples/trunk/pagedimg-e/resources/collectionConfig.properties

    r36477 r36518  
    22section_text=newspaper pages
    33
    4 shortDescription=<p>This collection contains a few newspapers from the <a href='http://www.nzdl.org/cgi-bin/library?a=p&amp;p=about&amp;c=niupepa'> Niupepa</a> collection of Maori newspapers.</p>
     4shortDescription=<p>This collection contains a few newspapers from the <a href='http\://www.nzdl.org/cgi-bin/library?a=p&amp;p=about&amp;c=niupepa'> Niupepa</a> collection of Maori newspapers.</p>
    55
    66description1=<h3>How the collection works</h3> <p>Each newspaper issue consists of a set of images, one per page, and a set of text files for the OCR\'d text. An item file links the set of pages into a single newspaper document. PagedImagePlugin is used to process the item files.</p>
    77
    8 description2=<p>There are two styles of item files, and this collection demonstrates both. The first uses a text based format, and consists of a list of metadata for the document, and a list of pages. Some examples are: <i>Te Waka o Te Iwi, Vol. 1, No. 1</i> (in <tt>import/09/09_1_1.item</tt>) and <i>Te Whetu o Te Tau, Vol. 1, No. 3</i> (in <tt>import/10/10_1_3.item</tt>. This format allows specification of document level metadata, and a single list of pages.</p>
     8description2=<p>There are two styles of item files, and this collection demonstrates both. The first uses a text based format, and consists of a list of metadata for the document, and a list of pages. Some examples are\: <i>Te Waka o Te Iwi, Vol. 1, No. 1</i> (in <tt>import/09/09_1_1.item</tt>) and <i>Te Whetu o Te Tau, Vol. 1, No. 3</i> (in <tt>import/10/10_1_3.item</tt>. This format allows specification of document level metadata, and a single list of pages.</p>
    99
    10 description3=<p>The second style is an extended format, and uses XML. It allows a hierarchy of pages, and metadata specification at the page level as well as at the document level. An example is <i>Matariki 1881, No. 2</i> in <tt>import/xml/23/23__2.item</tt>. This newspaper also has an abstract associated with it. The contents have been grouped into two sections: Supplementary Material, which contains the Abstract, and Newspaper Pages, which contains the page images.</p>
     10description3=<p>The second style is an extended format, and uses XML. It allows a hierarchy of pages, and metadata specification at the page level as well as at the document level. An example is <i>Matariki 1881, No. 2</i> in <tt>import/xml/23/23__2.item</tt>. This newspaper also has an abstract associated with it. The contents have been grouped into two sections\: Supplementary Material, which contains the Abstract, and Newspaper Pages, which contains the page images.</p>
    1111
    1212description4=<p>Paged documents can be presented with a hierarchical table of contents (e.g. <a href="library/collection/pagedimg-e/document/23__1?ed=1">23__1.2.1</a>), or with a single-depth structure (e.g. <a href="library/collection/pagedimg-e/document/10_1_2">10_1_2</a>). This is specified by the <tt>-documenttype (hierarchy|paged)</tt> option to PagedImagePlugin. Ordinarily, a Greenstone collection would have one plugin per document type, and all documents of that type get the same processing. In this case, we want to treat the XML-based item files differently from the text-based item files. We can achieve this by adding two PagedImagePlugin plugins to the collection, and configuring them differently.</p>

  • documented-examples/trunk/style-e/resources/collectionConfig.properties

    r36510 r36518  
    11name=Cascading Style Sheets<br/> Demo collection
    2 textdate=publication date:
    3 textnumpages=no. of pages:
    4 textsource=source ref:
     2textdate=publication date\:
     3textnumpages=no. of pages\:
     4textsource=source ref\:
    55section_chapter=chapter
    66document_book=book
    … …  
    1313dls.Titles=Titles
    1414dls.Keyword=How to
    15 depositormetadata={"name":"dls.Title","label":"Title","tooltip":"dls.Title: The title of this resource.","type":"text"}, {"name":"dls.Organization","label":"Organization","tooltip":"dls.Organization: The organization responsible for producing this resource.","type":"text"}, {"name":"dls.Subject","label":"Subject","tooltip":"dls.Subject: The subject of this resource.","type":"text"}, {"name":"dls.Keyword","label":"Keyword","tooltip":"dls.Keyword: A more specific indication of what the resource can be used for.","type":"text"}, {"name":"dls.Language","label":"Language","tooltip":"dls.Language: The language of this resource.","type":"text"}
     15depositormetadata={"name"\:"dls.Title","label"\:"Title","tooltip"\:"dls.Title\: The title of this resource.","type"\:"text"}, {"name"\:"dls.Organization","label"\:"Organization","tooltip"\:"dls.Organization\: The organization responsible for producing this resource.","type"\:"text"}, {"name"\:"dls.Subject","label"\:"Subject","tooltip"\:"dls.Subject\: The subject of this resource.","type"\:"text"}, {"name"\:"dls.Keyword","label"\:"Keyword","tooltip"\:"dls.Keyword\: A more specific indication of what the resource can be used for.","type"\:"text"}, {"name"\:"dls.Language","label"\:"Language","tooltip"\:"dls.Language\: The language of this resource.","type"\:"text"}
    1616
    1717
    … …  
    5252</p>
    5353
    54 description3=<p>If you want to download any of these stylesheets for your own collections, here are links to them: \n\
     54description3=<p>If you want to download any of these stylesheets for your own collections, here are links to them\: \n\
    5555<ul> \n\
    56 <li><a href='https://trac.greenstone.org/browser/documented-examples/trunk/style-e/style/gs3-style-default-extra.css'>GS3 default extra</a> - builds on top of GS3\'s default style</li> \n\
    57 <li><a href='https://trac.greenstone.org/browser/documented-examples/trunk/style-e/style/gs3-style-blue.css'>Blue theme</a> - modifies the GS3 default style for a blue colouring</li> \n\
    58 <li><a href='https://trac.greenstone.org/browser/documented-examples/trunk/style-e/style/gs3-style-olive-purple.css'>olive-purple theme</a> - modifies the GS3 default style for a vivid colouring of vine green and purples</li> \n\
     56<li><a href='https\://trac.greenstone.org/browser/documented-examples/trunk/style-e/style/gs3-style-default-extra.css'>GS3 default extra</a> - builds on top of GS3\'s default style</li> \n\
     57<li><a href='https\://trac.greenstone.org/browser/documented-examples/trunk/style-e/style/gs3-style-blue.css'>Blue theme</a> - modifies the GS3 default style for a blue colouring</li> \n\
     58<li><a href='https\://trac.greenstone.org/browser/documented-examples/trunk/style-e/style/gs3-style-olive-purple.css'>olive-purple theme</a> - modifies the GS3 default style for a vivid colouring of vine green and purples</li> \n\
    5959<li>None - clears all CSS styling from the current page (needs reload to get the default GS3 style back)</li> \n\
    6060</ul> \n\
    … …  
    6464<ul> \n\
    6565<li>To use a stylesheet as the default, place it in greenstone/web/interfaces/default/style and rename it to <tt>style.css</tt>. This will affect all collections.</li> \n\
    66 <li>To use a stylesheet for a particular collection, place it in <tt>greenstone/web/sites/localsite/collect/&lt;collection&gt;/style</tt> then specify the stylesheet link in the <b>additionalHeaderContent</b> of GLI\'s <i>global</i> format statement (<tt>Format &gt; Format Features &gt; global</tt>) as follows: \n\
     66<li>To use a stylesheet for a particular collection, place it in <tt>greenstone/web/sites/localsite/collect/&lt;collection&gt;/style</tt> then specify the stylesheet link in the <b>additionalHeaderContent</b> of GLI\'s <i>global</i> format statement (<tt>Format &gt; Format Features &gt; global</tt>) as follows\: \n\
    6767<pre>&lt;xsl\:template name="additionalHeaderContent"&gt; \n\
    6868    &lt;xsl\:variable name="httpCollection"&gt; \n\

  • documented-examples/trunk/wrdpdf-e/resources/collectionConfig.properties

    r36510 r36518  
    88description2=<h3>How the collection works</h3> <p> This collection\'s configuration file, <tt>collectionConfig.xml</tt>, contains the four plugins <i>WordPlugin</i>, <i>RTFPlugin</i>, <i>PDFPlugin</i> and <i>PostScriptPlugin</i> (along with the standard four, <i>GreenstoneXMLPlugin</i>, <i>MetadataXMLPlugin</i>, <i>ArchivesInfPlugin</i> and <i>DirectoryPlugin</i>). These four plugins all extract <i>Title</i> and <i>Source</i> (i.e. filename) metadata.</p>
    99
    10 description3=<p>Greenstone contains third-party software that is used to convert Word, RTF, PDF and PostScript files into HTML. The Greenstone team does not maintain these modules, although we do try to include the latest versions with each Greenstone release. Bugs arise with unusual Word documents (e.g. from older Macintosh systems), and sometimes the text is badly extracted. Some PDF files have no machine-readable text at all, comprising instead a sequence of page <i>images</i> from which text can only be extracted by optical character recognition (OCR), which Greenstone does not attempt. If you encounter these problems, you can either remove the offending documents from your collection, or try using some of the advanced plugin options to process the documents in different ways. For more information, see the Enhanced PDF and Word tutorials on the <a href='http://wiki.greenstone.org/wiki/index.php/Tutorial_exercises'>Greenstone wiki</a>. Alternatively, a new Greenstone 3 collection will add in a pre-configured <i>UnknownConverterPlugin</i> that will use <i>apache tika</i> by default to process docx files. You can reconfigure it, or add another UnknownConverterPlugin and configure it appropriately, to process other document types, refer to <a href="http://wiki.greenstone.org/doku.php?id=en:plugin:unknownconverterplugin">The UnknownConverterPlugin</a> page on the Greenstone wiki.</p>
     10description3=<p>Greenstone contains third-party software that is used to convert Word, RTF, PDF and PostScript files into HTML. The Greenstone team does not maintain these modules, although we do try to include the latest versions with each Greenstone release. Bugs arise with unusual Word documents (e.g. from older Macintosh systems), and sometimes the text is badly extracted. Some PDF files have no machine-readable text at all, comprising instead a sequence of page <i>images</i> from which text can only be extracted by optical character recognition (OCR), which Greenstone does not attempt. If you encounter these problems, you can either remove the offending documents from your collection, or try using some of the advanced plugin options to process the documents in different ways. For more information, see the Enhanced PDF and Word tutorials on the <a href='http\://wiki.greenstone.org/wiki/index.php/Tutorial_exercises'>Greenstone wiki</a>. Alternatively, a new Greenstone 3 collection will add in a pre-configured <i>UnknownConverterPlugin</i> that will use <i>apache tika</i> by default to process docx files. You can reconfigure it, or add another UnknownConverterPlugin and configure it appropriately, to process other document types, refer to <a href="http\://wiki.greenstone.org/doku.php?id=en\:plugin\:unknownconverterplugin">The UnknownConverterPlugin</a> page on the Greenstone wiki.</p>
    1111
    12 description4=<p>The collection configuration file, <tt>collectionConfig.xml</tt>, includes a single index, based on document text, and one classifier, an <i>AZList</i> based on <i>Title</i> metadata, shown in <tt>CL1</tt> (the alphabetic selector is suppressed automatically because the collection contains only a few documents). However, no format statement is specified. In the absence of explicit information, Greenstone supplies sensible defaults. In this case, the default format statement for the classifier gives: \n\
     12description4=<p>The collection configuration file, <tt>collectionConfig.xml</tt>, includes a single index, based on document text, and one classifier, an <i>AZList</i> based on <i>Title</i> metadata, shown in <tt>CL1</tt> (the alphabetic selector is suppressed automatically because the collection contains only a few documents). However, no format statement is specified. In the absence of explicit information, Greenstone supplies sensible defaults. In this case, the default format statement for the classifier gives\: \n\
    1313<ul> \n\
    1414<li>an icon for the HTML version of the document (the text that is actually indexed, essentially the same as the Greenstone Archive format);</li> \n\
    … …  
    2121<pre>\
    2222&lt;format&gt; \n\
    23     &lt;gsf:template match="documentNode"&gt; \n\
    24         &lt;gsf:format-gs2&gt;&lt;![CDATA[&lt;td valign="top"&gt;[link][icon][/link]&lt;/td&gt; \n\
     23    &lt;gsf\:template match="documentNode"&gt; \n\
     24        &lt;gsf\:format-gs2&gt;&lt;![CDATA[&lt;td valign="top"&gt;[link][icon][/link]&lt;/td&gt; \n\
    2525&lt;td valign="top"&gt;[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink]&lt;/td&gt; \n\
    26 &lt;td valign="top"&gt;[highlight] {Or}{[dc.Title],[exp.Title],[ex.Title],Untitled} [/highlight]{If}{[ex.Source],&lt;br&gt;&lt;i&gt;([ex.Source])&lt;/i&gt;}&lt;/td&gt;]]&gt;&lt;/gsf:format-gs2&gt; \n\
     26&lt;td valign="top"&gt;[highlight] {Or}{[dc.Title],[exp.Title],[ex.Title],Untitled} [/highlight]{If}{[ex.Source],&lt;br&gt;&lt;i&gt;([ex.Source])&lt;/i&gt;}&lt;/td&gt;]]&gt;&lt;/gsf\:format-gs2&gt; \n\
    2727        &lt;td valign="top"&gt; \n\
    28             &lt;gsf:link type="document"&gt; \n\
    29                 &lt;gsf:icon type="document"/&gt; \n\
    30             &lt;/gsf:link&gt; \n\
     28            &lt;gsf\:link type="document"&gt; \n\
     29                &lt;gsf\:icon type="document"/&gt; \n\
     30            &lt;/gsf\:link&gt; \n\
    3131        &lt;/td&gt; \n\
    3232        &lt;td valign="top"&gt; \n\
    33             &lt;gsf:link type="source"&gt; \n\
    34                 &lt;gsf:choose-metadata&gt; \n\
    35                     &lt;gsf:metadata name="thumbicon"/&gt; \n\
    36                     &lt;gsf:metadata name="srcicon"/&gt; \n\
    37                 &lt;/gsf:choose-metadata&gt; \n\
    38             &lt;/gsf:link&gt; \n\
     33            &lt;gsf\:link type="source"&gt; \n\
     34                &lt;gsf\:choose-metadata&gt; \n\
     35                    &lt;gsf\:metadata name="thumbicon"/&gt; \n\
     36                    &lt;gsf\:metadata name="srcicon"/&gt; \n\
     37                &lt;/gsf\:choose-metadata&gt; \n\
     38            &lt;/gsf\:link&gt; \n\
    3939        &lt;/td&gt; \n\
    4040        &lt;td valign="top"&gt; \n\
    4141            &lt;span class="highlight"&gt; \n\
    42                 &lt;gsf:choose-metadata&gt;&lt;gsf:metadata name="dc.Title"/&gt;&lt;gsf:metadata name="exp.Title"/&gt;&lt;gsf:metadata name="Title"/&gt;Untitled&lt;/gsf:choose-metadata&gt; \n\
     42                &lt;gsf\:choose-metadata&gt;&lt;gsf\:metadata name="dc.Title"/&gt;&lt;gsf\:metadata name="exp.Title"/&gt;&lt;gsf\:metadata name="Title"/&gt;Untitled&lt;/gsf\:choose-metadata&gt; \n\
    4343            &lt;/span&gt; \n\
    44             &lt;gsf:switch&gt; \n\
    45                 &lt;gsf:metadata name="Source"/&gt; \n\
    46                 &lt;gsf:when test="exists"&gt; \n\
     44            &lt;gsf\:switch&gt; \n\
     45                &lt;gsf\:metadata name="Source"/&gt; \n\
     46                &lt;gsf\:when test="exists"&gt; \n\
    4747                    &lt;br/&gt; \n\
    48                     &lt;i&gt;(&lt;gsf:metadata name="Source"/&gt;)&lt;/i&gt; \n\
    49                 &lt;/gsf:when&gt; \n\
    50             &lt;/gsf:switch&gt; \n\
     48                    &lt;i&gt;(&lt;gsf\:metadata name="Source"/&gt;)&lt;/i&gt; \n\
     49                &lt;/gsf\:when&gt; \n\
     50            &lt;/gsf\:switch&gt; \n\
    5151        &lt;/td&gt; \n\
    52     &lt;/gsf:template&gt; \n\
     52    &lt;/gsf\:template&gt; \n\
    5353&lt;/format&gt;
    5454</pre> \n\
Note: See TracChangeset for help on using the changeset viewer.