Ignore:
Timestamp:
2022-08-20T17:57:50+12:00 (20 months ago)
Author:
anupama
Message:

On testing the GTI now updated to incorporate the gs3-dec-col-cfgs module (the DEC collection's GS3 display strings), it turns out that GTI doesn't like the quot HTML entity and only the actual doublequote character is accepted. I had thought it would be the other way around. I've now fixed up all the affected DEC collectionConfig.properties files to replace the HTML entity with the doublequote character.

File:
1 edited

Legend:

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

    r36394 r36404  
    1010description2=<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
    12 description3=<p>The MARC plugin uses a special file to map MARC field numbers to Greenstone-style metadata. This file resides in the <i>greenstone/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 &quot;\#&quot; are comments.</p>
     12description3=<p>The MARC plugin uses a special file to map MARC field numbers to Greenstone-style metadata. This file resides in the <i>greenstone/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
    1414description4=<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
    16 description5=<p>Multiple MARC fields may map to a single Dublin Core field. For example, fields 720 (&quot;Uncontrolled name&quot;), 100 (&quot;Personal name&quot;), 110 (&quot;Corporate name&quot;) and 111 (&quot;Meeting name&quot;) 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>
     16description5=<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 &quot;c&quot; (Date of Publication) and &quot;g&quot; (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: <tt>greenstone/etc/marc2qdc.txt</tt>. This can be used by the MARC plugin by setting the <i>-metadata_mapping_file</i> option to &quot;marc2qdc.txt&quot;.</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: <tt>greenstone/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>
Note: See TracChangeset for help on using the changeset viewer.