- Timestamp:
- 2009-06-10T12:14:42+12:00 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
collections/documented-examples/trunk/marc-e/etc/collect.cfg
r19691 r19786 188 188 189 189 <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>ÐПМÑОгÑÑаÑОПММÑй Ñайл</a> ОÑпПлÑзÑÐµÑ Ð¿Ð»Ð°Ð³ÐžÐœÑ <i>ZIPPlug</i> О <i>MARCPlug</i>, пПЌОЌП ÑÑеÑÑегП ÑÑаМЎаÑÑа. ÐЌеÑÑÑÑ ÑÑО клаÑÑОÑОкаÑПÑа, ПÑМПваММÑе Ма ЌеÑаЎаММÑÑ 190 <i>ÐÐ°Ð·Ð²Ð°ÐœÐžÑ (dc.Title)</i>, <i>СПзЎаÑÐµÐ»Ñ (dc.Creator)</i> О <i>ÐÑеЎЌеÑа (dc.Subject)</i>. <!-- _text1_ --> ÐÑП ÑÑебÑÐµÑ ÑÑÑаМПвкО PERL ÐŽÐ»Ñ Ð¿ÑавОлÑМПгП вÑÑажеМОÑ, О ÑÑÐµÐ·Ð°ÐµÑ Ð·ÐœÐ°ÐºÐž (ÑОпа кПМеÑÐœÑÑ 190 <i>ÐÐ°Ð·Ð²Ð°ÐœÐžÑ (dc.Title)</i>, <i>СПзЎаÑÐµÐ»Ñ (dc.Creator)</i> О <i>ÐÑеЎЌеÑа (dc.Subject)</i>. <!-- _text1_ -->The <i>dc.Title</i> classifier is an AZList, while the other two are 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> 191 classifiers removes suffixes from the metadata string (<i>dc.Title</i> and 192 <i>dc.Creator</i> respectively). ÐÑП ÑÑебÑÐµÑ ÑÑÑаМПвкО PERL ÐŽÐ»Ñ Ð¿ÑавОлÑМПгП вÑÑажеМОÑ, О ÑÑÐµÐ·Ð°ÐµÑ Ð·ÐœÐ°ÐºÐž (ÑОпа кПМеÑÐœÑÑ 191 193 зМакПв пÑепОМаМОÑ) Оз ÑÑÑПкО ÐŽÐ»Ñ ÐŸÑПбÑажеМОÑ. 192 194 <p> 193 195 <!-- _text2_ --> 196 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. 194 197 <p> 195 198 … … 208 211 209 212 <!-- _text3_ --> 213 Multiple MARC fields may map to a single Dublin Core field. 214 For example, fields 720 (\"Uncontrolled name\"), 100 (\"Personal name\"), 215 110 (\"Corporate name\") and 111 (\"Meeting name\") all map to 216 <i>dc.Creator</i>. Actual MARC records normally 217 define only one of these fields, and anyway Greenstone allows 218 multi-valued metadata.\n 219 <p> 220 Some mappings are dependent on subfields. For example, MARC field 260 contains 221 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: 222 <blockquote> 223 260$c$g -> dc.Date 224 </blockquote> 225 226 Greenstone also provides a file for mapping MARC to <b>qualified</b> dublin core: <a href=\"_httpprefix_/etc/marc2qdc.txt\" target=marc2qdc>greenstone/etc/marc2qdc.txt</a>. This can be used by the MARC plugin by setting the <i>-metadata_mapping_file</i> option to \"marc2qdc.txt\". 210 227 " 211 228
Note:
See TracChangeset
for help on using the changeset viewer.