Ignore:
Timestamp:
2022-09-16T11:17:49+12:00 (20 months ago)
Author:
anupama
Message:

Part 2/2 Removing (after adding) the usual dummy insertion of QQQQ in all English language DEC collection description strings as part of forcing GTI to mark each translated string as needing updating.

File:
1 edited

Legend:

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

    r36624 r36625  
    1 name=QQQQCDS/ISIS example
    2 Collation=QQQQCollation
    3 HideCDSrecord=QQQQHide CDS/ISIS record
    4 CorporateAuthors=QQQQCorporate authors
    5 ShowCDSrecord=QQQQShow CDS/ISIS record
    6 Series=QQQQSeries
    7 Authors=QQQQAuthors
    8 OtherLanguageTitles=QQQQOther language titles
    9 Imprint=QQQQImprint
    10 sampleoid=QQQQD0s103
    11 Keywords=QQQQKeywords
    12 Title=QQQQTitle
    13 Conference=QQQQConference
    14 Notes=QQQQNotes
    15 CDSrecord=QQQQCDS/ISIS record
    16 AddedTitle=QQQQAdded title
    17 Edition=QQQQEdition
    18 Meetings=QQQQMeetings
     1name=CDS/ISIS example
     2Collation=Collation
     3HideCDSrecord=Hide CDS/ISIS record
     4CorporateAuthors=Corporate authors
     5ShowCDSrecord=Show CDS/ISIS record
     6Series=Series
     7Authors=Authors
     8OtherLanguageTitles=Other language titles
     9Imprint=Imprint
     10sampleoid=D0s103
     11Keywords=Keywords
     12Title=Title
     13Conference=Conference
     14Notes=Notes
     15CDSrecord=CDS/ISIS record
     16AddedTitle=Added title
     17Edition=Edition
     18Meetings=Meetings
    1919
    20 Notes^all=QQQQnotes
    21 PersonalAuthors^all=QQQQpersonal authors
    22 AddedTitle^all=QQQQadded title
    23 Imprint^all=QQQQimprint
    24 ConferenceMainEntry^all=QQQQconference main entry
    25 CorporateBodies^all=QQQQcorporate bodies
    26 Series^all=QQQQseries
    27 OtherLanguageTitles^all=QQQQother language titles
    28 Keywords^all=QQQQkeywords
    29 Collation^all=QQQQcollation
    30 Title^all=QQQQtitle
    31 text=QQQQraw record
    32 Meetings^all=QQQQmeetings
    33 Edition^all=QQQQedition
     20Notes^all=notes
     21PersonalAuthors^all=personal authors
     22AddedTitle^all=added title
     23Imprint^all=imprint
     24ConferenceMainEntry^all=conference main entry
     25CorporateBodies^all=corporate bodies
     26Series^all=series
     27OtherLanguageTitles^all=other language titles
     28Keywords^all=keywords
     29Collation^all=collation
     30Title^all=title
     31text=raw record
     32Meetings^all=meetings
     33Edition^all=edition
    3434
    35 shortDescription=QQQQ<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. <a href="library/collection/isis-e/document/D0s103">Here</a> is an example record.</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. <a href="library/collection/isis-e/document/D0s103">Here</a> is an example record.</p>
    3636
    37 description1=QQQQ<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
    39 description2=QQQQ<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>
     39description2=<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>
    4040
    41 description3=QQQQ<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>
     41description3=<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>
    4242
    43 description4=QQQQ<p>The designer of this collection has decided to create searchable indexes on all the <i>^all</i> metadata fields, as well as one on <i>text</i> which makes the raw records searchable too. Of course, the designer could have created searchable indexes on any of the subfields instead -- or as well.</p>
     43description4=<p>The designer of this collection has decided to create searchable indexes on all the <i>^all</i> metadata fields, as well as one on <i>text</i> which makes the raw records searchable too. Of course, the designer could have created searchable indexes on any of the subfields instead -- or as well.</p>
    4444
    45 description5=QQQQ<p>There are two browsing classifiers, an <i>AZList</i> based on <i>Title</i> metadata and an <i>AZCompactList</i> based on <i>Keyword</i> metadata. Recall that the <i>AZCompactList</i> classifier is like <i>AZList</i> but generates a bookshelf for duplicate items. The <i>VList</i> format specification applies to both the search results list and the <i>Title</i> classifier, while the <i>CL2VList</i> puts the number of documents associated with each keyword as described in the <a href="library/collection/marc-e/page/about">MARC example collection</a>. In Greenstone, and in CDS/ISIS, any metadata item can have several different values. The <i>VList</i> specification <nobr><i>sibling(All'; ')</i></nobr> gathers together all the values, separated (in this case) by semicolon.</p>
     45description5=<p>There are two browsing classifiers, an <i>AZList</i> based on <i>Title</i> metadata and an <i>AZCompactList</i> based on <i>Keyword</i> metadata. Recall that the <i>AZCompactList</i> classifier is like <i>AZList</i> but generates a bookshelf for duplicate items. The <i>VList</i> format specification applies to both the search results list and the <i>Title</i> classifier, while the <i>CL2VList</i> puts the number of documents associated with each keyword as described in the <a href="library/collection/marc-e/page/about">MARC example collection</a>. In Greenstone, and in CDS/ISIS, any metadata item can have several different values. The <i>VList</i> specification <nobr><i>sibling(All'; ')</i></nobr> gathers together all the values, separated (in this case) by semicolon.</p>
    4646
    47 description6=QQQQ<p>The <i>DocumentContent</i> format specification incorporates the same mechanism for hiding and showing raw records as explained for the <a href="library/collection/bibtex-e/page/about">Bibliography collection</a>, using the <i>DocumentHeading</i> to show the formatted record and <i>DocumentContent</i> to show (or hide) the original database entry.</p>
     47description6=<p>The <i>DocumentContent</i> format specification incorporates the same mechanism for hiding and showing raw records as explained for the <a href="library/collection/bibtex-e/page/about">Bibliography collection</a>, using the <i>DocumentHeading</i> to show the formatted record and <i>DocumentContent</i> to show (or hide) the original database entry.</p>
Note: See TracChangeset for help on using the changeset viewer.