Changeset 36454

Timestamp:

2022-08-22T17:56:44+12:00 (20 months ago)

Author:

anupama

Message:

Correcting more of the newly added GS3 DEC collection strings after testing them

Location:

documented-examples/trunk

Files:

• lomdemo-e/resources/collectionConfig.properties (modified) (1 diff)
• pagedimg-e/resources/collectionConfig.properties (modified) (2 diffs)

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

@@ -16 +16 @@
 description3=<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>
 
-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: \n\
-<pre> \n\
+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: \
+<pre>\
 &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\
-\n\
-&lt;replace macro="_httpclosemdicon_" scope="metadata" text="sites/localsite/collect/lomdemo-e/images/close.gif" data-img-path="sites/localsite/collect/lomdemo-e/images/" resolve="false"/&gt;
+&lt;replace macro="_httpclosemdicon_" scope="metadata" text="sites/localsite/collect/lomdemo-e/images/close.gif" data-img-path="sites/localsite/collect/lomdemo-e/images/" resolve="false"/&gt; \n\
 </pre> \n\
 </p>

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

@@ -6 +6 @@
 description1=<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>
 
-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>
+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>
 
-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>
+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>
 
-description4=<p>Paged documents can be presented with a hierarchical table of contents (e.g. <tt>23\_\_1.2.1</tt>), or with next and previous page arrows, and a goto page box (e.g. <tt>10\_1\_2</tt>). This is specified by the <tt>-documenttype (hierarchy|paged)</tt> option to PagedImagePlugin. The next and previous arrows suit the linear sequence documents, while the table of contents suits the hierarchically organised document. 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>
+description4=<p>Paged documents can be presented with a hierarchical table of contents (e.g. <tt>23__1.2.1</tt>), or with next and previous page arrows, and a goto page box (e.g. <tt>10_1_2</tt>). This is specified by the <tt>-documenttype (hierarchy|paged)</tt> option to PagedImagePlugin. The next and previous arrows suit the linear sequence documents, while the table of contents suits the hierarchically organised document. 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>
 
 description5=<p><tt>plugin PagedImagePlugin -documenttype hierarchy -process_exp xml.*\.item$; <br/> plugin PagedImagePlugin -documenttype paged</tt></p>
@@ -16 +16 @@
 description6=<p>XML based newpapers have been grouped into a folder called <tt>xml</tt>. This enables us to process these files differently, by utilising the <tt>process_exp</tt> option which all plugins support. The first PagedImagePlugin in the list looks for item files underneath the xml folder. These documents will be processed as hierarchical documents. Item files that don\'t match the process expression (i.e. aren\'t underneath the xml folder) will be passed onto the second PagedImagePlugin, and these are treated as paged documents.</p>
 
-description7=<p><b>Formatting</b> <p>Unlike in Greenstone 2, where the document formatting was modified to customize the display, in Greenstone 3 we rely for the rest on Greenstone\s default behaviour.</p>
+description7=<p><b>Formatting</b> <p>Unlike in Greenstone 2, where the document formatting was modified to customize the display, in Greenstone 3 we rely for the rest on Greenstone\'s default behaviour.</p>