Ignore:
Timestamp:
2022-08-24T17:42:31+12:00 (20 months ago)
Author:
anupama
Message:

Kathy explained what the groupsize importOption, that GS3 needs to mimic for 2 DEC collections which used this option in GS2. Also adjusted the documentHeading in gsarch-e collection, to better match the original collection description.

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r36391 r36472  
    3737description1=<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
    39 description2=<p>Like the <i>bibliography collection</i>, this collection incorporates a <tt>form-based search interface</tt> 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 <tt>Preferences</tt> page). The <i>groupsize 100</i> line puts documents together into groups of 100 (as explained in the <i>bibliography collection</i>).</p>
     39description2=<p>Like the <i>bibliography collection</i>, this collection incorporates a <tt>form-based search interface</tt> 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 <tt>Preferences</tt> 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 <i>bibliography collection</i>).</p>
    4040
    4141description3=<p>Some fields in CDS/ISIS databases have subfields. For example, in this case the <i>Imprint</i> field has subfields <i>Imprint.a</i> for place, <i>Imprint.b</i> for publisher and <i>Imprint.c</i> for date. For each field and subfield, ISISPlugin generates a metadata element -- in this case there will be metadata called <i>Imprint^a</i>, <i>Imprint^b</i> and <i>Imprint^c</i>. (There could be a field called just <i>Imprint</i>, although in this case there is not.) ISISPlugin also generates a metadata element called <i>Imprint^all</i> that gives all subfields concatenated together, separated by the character string that was specified as a plugin argument (in this case ", ").</p>
Note: See TracChangeset for help on using the changeset viewer.