Changeset 19786 for collections/documented-examples
- Timestamp:
- 2009-06-10T12:14:42+12:00 (15 years ago)
- Location:
- collections/documented-examples/trunk
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
collections/documented-examples/trunk/authen-e/etc/collect.cfg
r19691 r19786 203 203 <p> 204 204 <!-- _text1_ --> 205 The <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>collection 206 configuration file</a> is exactly the same as for the original demo collection apart from the authentication directives, one plugin option (and this description). 205 207 206 208 <p> … … 213 215 214 216 <p> 215 <!-- _text3_ --> СпеÑОÑÐžÐºÑ ÑÐ°ÐŒÐžÑ 217 <!-- _text3_ -->Authentication is activated by the <i>authenticate</i> directive with the value 218 <i>collection</i> or <i>document</i> depending on whether authentication is to 219 be performed on the full collection or on a per-document basis (the default 220 value is <i>collection</i>). If authentication is on a <i>document</i> basis, 221 then one can <i>either</i> specify a list of private documents (in which 222 case all others are public) or a list of public documents (in which case 223 all others are private) using directives <i>private_documents</i> or 224 <i>public_documents</i>. СпеÑОÑÐžÐºÑ ÑÐ°ÐŒÐžÑ 216 225 ЎПкÑЌеМÑПв ПпÑеЎелÑÑÑ, ОÑпПлÑзÑÑ ÐžÐŽÐµÐœÑОÑОкаÑПÑÑ ÐŽÐŸÐºÑЌеМÑа в Greenstone (ÑаÑпÑеЎелеММÑÑ 217 226 пП ПблаÑÑÑÐŒ). СаЌÑй легкОй ÑпПÑПб ÐžÑ … … 219 228 ПжЎеМОе кажЎПгП ЎПкÑЌеМÑа в кПллекÑОО О ÑаÑÑЌПÑÑеÑÑ ÐµÐ³ÐŸ <i>d</i>-аÑгÑÐŒÐµÐœÑ Ð² URL Greenstone. 220 229 221 <p><!-- _text2_ -->\n 230 <p><!-- _text2_ --> 231 In this case, we have used the <i>-OIDtype dirname</i> option to HTMLPlugin, 232 which specifies that directory names should be used as identifiers. This works 233 for collections where each document is in a separate directory. We have used 234 this option to ensure that identifiers remain the same across different 235 platforms (which may not be the case for HASH identifiers), as we need to 236 specify identifiers here for the authentication directives.\n 237 222 238 <p> 223 239 ÐОÑекÑОва <i>auth_groups</i> ПпÑеЎелÑÐµÑ Ð³ÑÑÐ¿Ð¿Ñ Greenstone, к кПÑПÑÑÐŒ ЎПÑÑÑп бÑÐŽÐµÑ ÑазÑеÑеМ, еÑлО ЎПкÑÐŒÐµÐœÑ (ОлО кПллекÑОÑ) ПÑМПÑОÑÑÑ Ðº ÑеЌ, ÐŽÐ»Ñ ÐºÐŸÑПÑÑÑ -
collections/documented-examples/trunk/bibtex-e/etc/collect.cfg
r19691 r19786 517 517 вЌеÑÑе пÑеЎПÑвÑаÑÐ°ÐµÑ Ð²ÐœÑÑÑеММОе ÑайлПвÑе ÑÑÑÑкÑÑÑÑ Greenstone ÐŸÑ ÑвелОÑÐµÐœÐžÑ ÐŸÐ±ÑÑЌа О заМÑÑÐžÑ Ð±ÐŸÐ»ÑÑегП ЎОÑкПвПгП пÑПÑÑÑаМÑÑва, ÑеЌ ÐœÐµÐŸÐ±Ñ 518 518 ПЎОЌП. 519 <!-- 520 <p> 521 _text1_ 522 523 <p> 524 _text5_ 525 526 <p> 527 _text3_ 528 --> 519 520 <p> 521 <!-- _text1_ --> 522 Apart from the standard plugins, this collection uses <i>BibTexPlugin</i>, 523 which processes references in the BibTeX format (well known to computer 524 scientists). Two options have been set for BibTexPlugin: 525 <i>-OIDtype assigned -OIDmetadata Number</i>. This means the metadata 526 element \"Number\" will be used as the record identifier, instead of 527 Greenstone's default hash identifiers. These options are available for 528 all plugins.\n 529 530 <p> 531 <!-- _text5_ --> 532 Fielded searching, with a form-based interface, is selected by <i>format SearchTypes \"form,plain\" 533 </i> in the configuration file. In fact, a plain textual full-text search 534 index is included in this collection as well (since <i>form</i> comes first, 535 it is the default interface; you reach the <i>plain</i> search through 536 the <i>Preferences</i> page).\n 537 538 <p> 539 <!-- _text3_--> 540 The <i>buildtype</i> option shows that the default search engine <i>mgpp</i> is 541 used. The <i>indexes</i> line specifies indexes for \"text\", and \"metadata\". In this case, \"text\" will be the original BibTeX record. \"metadata\" is a special keyword signifying that an index should be built for any metadata item found in the collection. 529 542 530 543 <p> … … 534 547 . ÐеÑаЎаММÑе Ма ÑÑПвМе кПллекÑОО <i>collectionmeta</i> ЌПгÑÑ Ð±ÑÑÑ Ð·Ð°ÐŽÐ°ÐœÑ ÐŽÐ»Ñ Ð»ÑбПгП ОМЎекÑа, ÑÑÐŸÐ±Ñ ÐŸÐ¿ÑеЎелОÑÑ, ÑÑП ÑÑП ПзМаÑÐ°ÐµÑ Ð² ÐŒÐµÐœÑ (за ОÑклÑÑеМОеЌ <i>metadata</i>, кПÑПÑПе ÑÐŸÐ·ÐŽÐ°ÐµÑ ÐŒÐœÐŸÐ³ÐŸ пÑМкÑПв ЌеМÑ). Ð ÑÑПЌ ÑлÑÑае <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>кПМÑОгÑÑаÑОПММÑй Ñайл</a> ПпÑеЎелÑеÑ, ÑÑП ÑекÑÑПвÑй ÐžÐœÐŽÐµÐºÑ ÐŽÐŸÐ»Ð¶ÐµÐœ бÑÑÑ ÐœÐ°Ð·Ð²Ð°Ðœ \"<i>full record</i>\", пПÑÐŸÐŒÑ ÑÑП ПМа ÑПЎеÑÐ¶ÐžÑ ÐŸÑОгОМалÑÐœÑÑ Ð±ÐžÐ±Ð»ÐžÐŸÐ³ÑаÑОÑеÑкÑÑ Ð·Ð°Ð¿ÐžÑÑ. 535 548 536 <!-- <p>_text4_ --> 549 <p> 550 <!-- _text4_ --> 551 An additional keyword, \"allfields\", could also be used in the <i>indexers</i> line, specifying that combined searching over all indexes should be available. 552 <p> 553 The <i>levels</i> lines specifies only document level, as bibliographic records don't have internal structure. 554 537 555 <p> 538 556 ÐÑа кПллекÑÐžÑ ÑПЎеÑÐ¶ÐžÑ Ð¿ÑПгÑÐ°ÐŒÐŒÑ Ð¿ÑПÑЌПÑÑа пП <i>ÐазваМОÑ</i>, <i>ÐвÑПÑÑ Ðž ÐаÑе</i>, О ÑпеÑОалÑÐœÑй вОЎ ОМЎекÑа ÑÑазÑ, МазÑваеЌÑй \"<i>Phind</i>\". ÐлаÑÑОÑОкаÑÐŸÑ <i>AZCompactList</i>, ОÑпПлÑзÑеЌÑй ÐŽÐ»Ñ Ð¿ÑПÑЌПÑÑа пП <i>ÐвÑПÑÑ</i>, Ð¿ÐŸÑ -
collections/documented-examples/trunk/bibtex-supp-e/etc/collect.cfg
r19691 r19786 426 426 supercollection documented-examples/bibtex-supp-e documented-examples/bibtex-e 427 427 </pre> 428 428 429 <!-- _text1_ --> 430 The \"documented-examples/\" parts of the collection names are necessary 431 because these collections reside in the \"documented-examples\" collection 432 group subfolder in the collect directory.\n 429 433 <p> 430 434 -
collections/documented-examples/trunk/dls-e/etc/collect.cfg
r19691 r19786 540 540 541 541 <!-- _text1_ --> 542 The DLS collection is fairly complex. 542 543 еÑлО ÐÑ ÑвлÑеÑеÑÑ ÑПлÑкП МаÑОМаÑÑОЌ пПлÑзПваÑелеЌ, ÑП лÑÑÑе вМаÑале ПзМакПЌОÑÑÑÑ Ñ ÐœÐµÐºÐŸÑПÑÑЌО ÐŽÑÑгОЌО кПллекÑОÑЌО (МапÑОЌеÑ, Ñ <a href=\"_gwcgi_?l=_cgiargl_&c=documented-examples/wrdpdf-e&a=p&p=about\">msword О pdf ЎеЌПМÑÑÑаÑОÑЌО</a> ОлО же Ñ Ð°ÑÑ 543 544 ОваЌО ОлО Ñ Ð¿ÑПÑÑПй гÑаÑОÑеÑкПй кПллекÑОей). … … 545 546 546 547 <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>ÐПМÑОгÑÑаÑОПММÑй Ñайл</a> кПллекÑОО, пПЎПбМП вÑеЌ кПМÑОгÑÑаÑОПММÑÐŒ ÑайлаЌ ÐŽÑÑÐ³ÐžÑ 547 кПллекÑОй, МаÑОМаеÑÑÑ ÑП ÑÑÑПкО «СПзЎаÑелÑ» (\"Сreator\"), кПÑПÑÐ°Ñ ÑППбÑÐ°ÐµÑ Ð°ÐŽÑÐµÑ ÑлекÑÑПММПй пПÑÑÑ Ð¡ÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑОО, О ÐŽÑÑгПй -- «ÐÑблОка» (\"Public\"), кПÑПÑÐ°Ñ ÐŸÐ¿ÑеЎелÑеÑ, пПÑвОÑÑÑ Ð»Ðž кПллекÑÐžÑ ÐœÐ° ЎПЌаÑМей ÑÑÑаМОÑе ÑÑÑаМПвкО Greenstone. <!-- _text3_ --> 548 кПллекÑОй, МаÑОМаеÑÑÑ ÑП ÑÑÑПкО «СПзЎаÑелÑ» (\"Сreator\"), кПÑПÑÐ°Ñ ÑППбÑÐ°ÐµÑ Ð°ÐŽÑÐµÑ ÑлекÑÑПММПй пПÑÑÑ Ð¡ÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ ÐºÐŸÐ»Ð»ÐµÐºÑОО, О ÐŽÑÑгПй -- «ÐÑблОка» (\"Public\"), кПÑПÑÐ°Ñ ÐŸÐ¿ÑеЎелÑеÑ, пПÑвОÑÑÑ Ð»Ðž кПллекÑÐžÑ ÐœÐ° ЎПЌаÑМей ÑÑÑаМОÑе ÑÑÑаМПвкО Greenstone. <!-- _text3_ -->Note that setting \"public\" to \"false\" only removes it from the home page; it will still be accessible in the library to anyone that knows the URL (a=p&p=about&c=coll-shortname). 548 549 549 550 <p> … … 584 585 585 586 <!-- _text6_ --> 587 The second classifier provides access by title. It is also a <i>Hierarchy</i> classifier, this time based on 588 <i>dls.AZList</i> metadata, whose hierarchy is defined in <a href=\"_httpcollection_/etc/dls.Title.txt\" target=text>dls.AZList.txt</a>. This file is discussed below. 586 589 587 590 ТÑеÑОй ÐŽÐ°ÐµÑ ÐŽÐŸÑÑÑп пП ПÑгаМОзаÑОÑÐŒ: ÑÑП клаÑÑОÑОкаÑÐŸÑ <i>СпОÑПк</i> ПÑМПваММÑй Ма ЌеÑаЎаММÑÑ 588 <i>dls.Organization</i>. <!-- _text8_ --> 589 590 <!-- _text9_ --> 591 592 591 <i>dls.Organization</i>. <!-- _text8_ -->The <i>-bookshelf_type always</i> option creates a new bookshelf for each organization, even if only one document belongs to that category. 592 593 <!-- _text9_ -->The fourth provides access by \"Howto\" text: it is a <i>List</i> classifier based on <i>dls.Keyword</i> metadata. The <i>-bookshelf_type never</i> option prevents bookshelves being created even if two documents share the same keywords. 593 594 594 595 <p> … … 596 597 597 598 <p> 598 <b>ÐпеÑаÑПÑÑ ÑПÑЌаÑа</b>. <!-- _text10_ --> 599 <!-- <p> 600 _text11_ --> 599 <b>ÐпеÑаÑПÑÑ ÑПÑЌаÑа</b>. 600 <!-- _text10_ --> 601 The lines beginning with <i>format</i>, called \"format statements\", govern how various parts of the collection should be displayed. The <i>VList</i> format statement applies to lists of items displayed vertically, such as the lists of titles, subjects and organisations, and the table of contents for the target documents. It is overridden for the search results list by the <i>SearchVList</i> format statement, and also for the <i>Howto</i> classifier by the <i>CL4VList</i> statement (CL4 specifies the fourth classifier). 602 <p> 603 <!--_text11_ --> 604 The <i>DocumentText</i> statement governs how the document text is formatted, 605 with <i>Title</i> metadata ([<i>Title</i>]) in HTML <<i>h3</i>> format 606 followed by the text of the document [<i>Text</i>]. Setting the <i>DocumentImages</i> format statement to <i>true</i> ensures that cover images are shown with each document. The <i>DocumentButtons</i> statement calls for the <i>Expand 607 Text, Expand Contents, Detach</i> and <i>Highlight</i> buttons to be shown with each document. 608 601 609 <p> 602 610 … … 615 623 <b>ÐеÑаЎаММÑе ÑÑÐŸÐ²ÐœÑ ÐºÐŸÐ»Ð»ÐµÐºÑОО</b>. СÑÑПкО <i>collectionmeta</i> в кПМÑОгÑÑаÑОПММПЌ Ñайле Ñакже ÑÑаМЎаÑÑÐœÑ Ð²ÐŸ вÑÐµÑ 616 624 кПллекÑОÑÑ 617 Greenstone. ÐМО ЎаÑÑ ÐŸÐ±ÑÑÑ ÐžÐœÑПÑЌаÑÐžÑ ÐŸ кПллекÑОО, ПпÑеЎелÑÑ ÐµÐµ МазваМОе (ОЌÑ), пÑеЎÑÑавлÑÑÑ ÐºÑаÑкПе ПпОÑаМОе, кПÑПÑПе пПÑвлÑеÑÑÑ ÐœÐ° ее ЎПЌаÑМей ÑÑÑаМОÑе. ÐÑаÑкПе ПпОÑаМОе (в <i>collectionextra</i>) ЌПжМП вОЎеÑÑ ÐœÐ° ЎПЌаÑМей ÑÑÑаМОÑе кПллекÑОО <!-- (_text2_) --> 625 Greenstone. ÐМО ЎаÑÑ ÐŸÐ±ÑÑÑ ÐžÐœÑПÑЌаÑÐžÑ ÐŸ кПллекÑОО, ПпÑеЎелÑÑ ÐµÐµ МазваМОе (ОЌÑ), пÑеЎÑÑавлÑÑÑ ÐºÑаÑкПе ПпОÑаМОе, кПÑПÑПе пПÑвлÑеÑÑÑ ÐœÐ° ее ЎПЌаÑМей ÑÑÑаМОÑе. ÐÑаÑкПе ПпОÑаМОе (в <i>collectionextra</i>) ЌПжМП вОЎеÑÑ ÐœÐ° ЎПЌаÑМей ÑÑÑаМОÑе кПллекÑОО <!-- (_text2_) -->(this text is part of it) 618 626 <p> 619 627 … … 660 668 <<i>FileSet</i>> ... <<i>FileSet</i>>. ÐМО ПпÑеЎелÑÑÑ <i>dls.Title, dls.Language, dls.Subject</i> О ЌеÑаЎаММÑе <i>dls.AZList</i>. ÐПлÑÑе ÑеЌ ПЎМП зМаÑеМОе ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐŸÐ¿ÑеЎелеМП ÐŽÐ»Ñ Ð»ÑбÑÑ 661 669 пÑМкÑПв ЌеÑаЎаММÑÑ 662 . <!-- _text5_ --> Ðба ÑПÑ670 . <!-- _text5_ -->For example, this book has two dls.Subject classifications. Ðба ÑÐŸÑ 663 671 ÑÐ°ÐœÐµÐœÑ Ð² каÑеÑÑве ЌеÑаЎаММÑÑ 664 672 ÐŽÐ»Ñ ÑÑПгП ÑпеÑОÑОÑеÑкПгП ЎПкÑЌеМÑа, пПÑÐŸÐŒÑ ÑÑП ÑПÑÑПÑМОе=МакаплОваÑÑ (<i>mode=accumulate</i>) ПпÑеЎелеМП, а в каÑеÑÑве алÑÑеÑМаÑÐžÐ²Ñ - зМаÑеМОе пП ÑЌПлÑаМОÑ, кПÑПÑÑÐŒ ÑвлÑеÑÑÑ <i>mode=override</i>. … … 666 674 667 675 <b>ÐеÑаÑÑ 668 ОÑеÑкОе ÑайлÑ</b>. <!-- _text12_ 669 670 <p> 671 _text13_ --> 676 ОÑеÑкОе ÑайлÑ</b>. 677 <!-- _text12_ --> 678 Hierarchy files contain a 679 succession of lines each of which has three items. The first item is a text string which is matched against the metadata that occurs in the <i>metadata.xml</i> file described above. The second item is a number that defines the position in the hierarchy. The third item is a text string that describes the node of the hierarchy on the web pages that Greenstone generates. 680 681 <p> 682 <!-- _text13_ --> 683 For example, the following shows three lines from the subject hierarchy file <a href=\"_httpcollection_/etc/dls.Subject.txt\" target=text>dls.Subject.txt</a>. 672 684 673 685 <pre> … … 677 689 </pre> 678 690 679 <!-- 680 <p> 681 _text14_ 682 683 <p> 684 _text15_ 685 686 <p> 687 _text16_ 688 --> 691 <p> 692 <!--_text14_ --> 693 These three lines define one top level bookshelf (at position 7), titled \"Animal Husbandry and Animal Product Processing\", with two bookshelves underneath it, titled \"Cattle\" and \"Other animals (micro-livestock, little known animals, silkworms, reptiles, frogs, snails, game, etc.)\" respectively. 694 695 <p> 696 <!--_text15_--> 697 In this case, the first strings (and therefore the entries in metadata.xml files) contain the entire hierarchy values. Levels in the hierarchy are separated by \"|\". They could be used directly by a <i>Hierarchy</i> classifier without the use of the hierarchy file. However, then the entries would be ordered alphabetically, not in the special order defined by the file. 698 699 <p> 700 <!--_text16_ --> 701 The <a href=\"_httpcollection_/etc/dls.AZList.txt\" target=text>dls.AZList.txt</a> hierarchy file used by the titles classifier contains a similar structure. Ordinarily, a titles browser would use a <i>List</i> (or <i>AZList</i>) classifier. In this case, we want to predefine the A-Z groupings, and include a separate entry for periodicals, as can be seen <a href=\"_gwcgi_?l=_cgiargl_&c=_cgiargc_&a=d&cl=CL2.7\">here</a>. 689 702 " 690 703 -
collections/documented-examples/trunk/gsarch-e/etc/collect.cfg
r19719 r19786 308 308 collectionmeta collectionextra [l=ru] " 309 309 <!-- _text1_ --> 310 310 This is a collection of email messages 311 from the Greenstone mailing list archives, from November/December, 2008. 311 312 312 313 <h3>Ðак ÑабПÑÐ°ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑОÑ</h3> … … 314 315 ÐПллекÑÐžÑ Ð°ÑÑ 315 316 ОвПв Greenstone ОÑпПлÑзÑÐµÑ Ð¿Ð»Ð°Ð³ÐžÐœ Ðmail, кПÑПÑÑй аМалОзОÑÑÐµÑ ÑÐ°Ð¹Ð»Ñ Ð² ÑПÑЌаÑÐ°Ñ 316 ÑлекÑÑПММПй пПÑÑÑ. <!-- _text2_ --> ÐлагОМ Ðmail ÑÐ°Ð·Ð±ÐžÐ²Ð°ÐµÑ ÐžÑ317 ÑлекÑÑПММПй пПÑÑÑ. <!-- _text2_ -->In this case, there is a file per month per mailing list, and each file contains many email messages. ÐлагОМ Ðmail ÑÐ°Ð·Ð±ÐžÐ²Ð°ÐµÑ ÐžÑ 317 318 Ма ОМЎОвОЎÑалÑÐœÑе ЎПкÑЌеМÑÑ Ðž ÑÐŸÐ·ÐŽÐ°ÐµÑ <i>ÐазваМОе</i>, <i>ÐÑеЎЌеÑ</i>, <i>ÐÑ</i>, <i>ÐÐŒÑ ÐŸÑпÑавОÑелÑ</i>, <i>ÐÐŽÑÐµÑ ÐŸÑпÑавОÑелÑ</i>, <i>ÐаÑа</i>, <i>ÐаÑа ÑекÑÑПЌ</i>, <i>ÐÐŸÐŒÑ ÐÑвеÑ</i> О вÑбПÑПÑМП <i>ÐагПлПвкО</i>. 318 319 <p> … … 336 337 , Ð¿ÐŸÑ 337 338 Пж Ма <i>AZLIST</i>, МП ПМ ÑПÑЌОÑÑÐµÑ ÐºÐœÐžÐ¶ÐœÑÑ Ð¿ÐŸÐ»ÐºÑ ÐŽÐ»Ñ ÐŽÑблОкаÑПв ÑлеЌеМÑПв, как пПказаМП <a href=\"_gwcgi_?l=_cgiargl_&c=_cgiargc_&a=d&cl=CL1\">зЎеÑÑ</a>. ÐМа пÑеЎÑÑавлеМа ÑÑÑÑкÑÑÑПй ЎеÑева, ÑÐ·Ð»Ñ ÐºÐŸÑПÑПй ÑвлÑÑÑÑÑ ÐžÐ»Ðž ÑзлаЌО лОÑÑа, пÑеЎÑÑавлÑÑ ÐŽÐŸÐºÑЌеМÑÑ, ОлО вМÑÑÑеММОЌО ÑзлаЌО. ÐеÑаЎаММÑе ÑлеЌеМÑПв, МазÑваеЌÑе numleafdocs, ЎаÑÑ ÐŸÐ±Ñее кПлОÑеÑÑвП ЎПкÑЌеМÑПв, ÑаÑпПлПжеММÑÑ 338 МОже вМÑÑÑеММегП Ñзла. ÐпеÑаÑПÑÑ ÑПÑЌаÑа ÐŽÐ»Ñ Ð¿ÐµÑвПгП клаÑÑОÑОкаÑПÑа, МазÑваеЌÑе <i>CL1Vlist</i>, пÑПвеÑÑÑÑ, ÑÑÑеÑÑвÑÐµÑ Ð»Ðž ÑÑÐŸÑ ÑлеЌеМÑ. ÐÑлО ÑÑП Ñак, ÑП Ñзел ЎПлжеМ бÑÑÑ Ð²ÐœÑÑÑеММОЌ, в ÑлÑÑае ÑегП ПМ пПЌеÑаеÑÑÑ ÐµÐ³ÐŸ <i>ÐазваМОеЌ (Title)</i>. <!-- _text4_ --> 339 МОже вМÑÑÑеММегП Ñзла. ÐпеÑаÑПÑÑ ÑПÑЌаÑа ÐŽÐ»Ñ Ð¿ÐµÑвПгП клаÑÑОÑОкаÑПÑа, МазÑваеЌÑе <i>CL1Vlist</i>, пÑПвеÑÑÑÑ, ÑÑÑеÑÑвÑÐµÑ Ð»Ðž ÑÑÐŸÑ ÑлеЌеМÑ. ÐÑлО ÑÑП Ñак, ÑП Ñзел ЎПлжеМ бÑÑÑ Ð²ÐœÑÑÑеММОЌ, в ÑлÑÑае ÑегП ПМ пПЌеÑаеÑÑÑ ÐµÐ³ÐŸ <i>ÐазваМОеЌ (Title)</i>. <!-- _text4_ -->Otherwise the node\'s label starts with the 340 <i>Subject</i> which links to the document, then gives <i>FromName</i> metadata, with a link to \"Search by Sender\", followed by the <i>DateText</i>. 339 341 <p> 340 342 … … 342 344 ÑзлПв ÑакÑОÑеÑкПе ÑОÑлП ЎПкÑЌеМÑПв в ÑпОÑке (<i>numleafdocs</i>) ЎаеÑÑÑ Ð² кÑÑглÑÑ 343 345 ÑÐºÐŸÐ±ÐºÐ°Ñ 344 пПÑле <i>ÐазваМОÑ</i>. <!-- _text5_ --> 346 пПÑле <i>ÐазваМОÑ</i>. <!-- _text5_ -->For 347 document nodes the <i>FromName</i>, with a link to \"Search By Sender\", <i>Subject</i> (linked to the document), and <i>DateText</i> metadata is 348 shown. 345 349 <p> 346 350 … … 348 352 <p> 349 353 350 <!-- _text6_ --> 354 <!-- _text6_ -->Finally, the document text is formatted to show the header fields (<i>FromName</i>, <i>DateText</i>, <i>Subject</i>, <i>InReplyTo</i>), followed by 355 the message text (written as <i>[Text]</i> in the format statement). FromName is linked to a search on that name, while InReplyTo links to the email message that it refers to. 351 356 " 352 357 -
collections/documented-examples/trunk/image-e/etc/collect.cfg
r19719 r19786 299 299 <p> 300 300 <!-- _text1_ --> 301 301 The images in this collection have been produced by members of the Department of Computer Science, University of Waikato. 302 The University of Waikato holds copyright. They may be distributed freely, without any restrictions. 302 303 303 304 <h3>Ðак ÑабПÑÐ°ÐµÑ ÐºÐŸÐ»Ð»ÐµÐºÑОÑ</h3> -
collections/documented-examples/trunk/isis-e/etc/collect.cfg
r19691 r19786 393 393 CDS/ISIS. 394 394 <!-- _text1_ --> 395 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. 396 395 397 Ð ÑÑПЌ ÑлÑÑае плагОМ бÑл ЎаМ паÑаЌеÑÑ <i>input_encoding</i>, пПÑкПлÑÐºÑ ÐœÐµÐºÐŸÑПÑÑе запОÑО в базе ЎаММÑÑ 396 398 ÑПЎеÑÐ¶Ð°Ñ Ð·ÐœÐ°ÐºÐž ÑаÑÑОÑÐµÐœÐžÑ ( в ÑПÑЌе, кПÑПÑÐ°Ñ ÐžÑпПлÑзПвалаÑÑ Ð² ÑÐ°ÐœÐœÐžÑ … … 398 400 ПпеÑаÑОПММПй ÑОÑÑÐµÐŒÑ DOS). ÐÐŒÑ Ñакже бÑл ЎаМ паÑаЌеÑÑ ÑазЎелеМОÑ, ÑÐµÐ»Ñ ÐºÐŸÑПÑПгП ПбÑÑÑÐœÑеÑÑÑ ÐœÐžÐ¶Ðµ. 399 401 <!-- _text2_ --> 402 The <i>-OIDtype incremental</i> plugin option was used to give identifiers 403 that are consistent across different operating systems (which may not happen with HASH identifiers), so that we can link to a document in 404 this description. 400 405 <p> 401 406 ÐПЎПбМП <a href=\"_gwcgi_?l=_cgiargl_&a=p&p=about&c=documented-examples/bibtex-e\">бОблОПгÑаÑОÑеÑкПй кПллекÑОО</a>, ÑÑа кПллекÑÐžÑ Ð²ÐºÐ»ÑÑÐ°ÐµÑ Ð±Ð»Ð°ÐœÐŸÑÐœÑй <a href=\"_gwcgi_?l=_cgiargl_&a=q&c=_cgiargc_&ct=1&qto=3&qt=1\">ОМÑеÑÑÐµÐ¹Ñ Ð¿ÐŸÐžÑка</a>, кПÑПÑÑй пПзвПлÑÐµÑ Ð¿ÑПОзвПЎОÑÑ Ð¿ÐŸÐžÑк пП пПлÑÐŒ. ÐÑП ПпÑеЎелеМП ÑÑÑПкПй <i>format SearchTypes \"form,plain\"</i> в кПМÑОгÑÑаÑОПММПЌ Ñайле; паÑаЌеÑÑ <i>plain</i> гаÑаМÑОÑÑеÑ, ÑÑП зЎеÑÑ ÐžÐŒÐµÐµÑÑÑ Ñакже пÑПÑÑПе ÑÑеЎÑÑвП пПлМПгП ÑекÑÑПвПгП пПОÑка (кПÑПÑПе ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð²Ð·ÑÑП Оз ÑÑÑаМОÑÑ <a href=\"_gwcgi_?l=_cgiargl_&a=p&c=_cgiargc_&p=preferences\">ÐÑеЎпПÑÑеМОй</a>). СÑÑПка <i>groupsize 100</i> ПбÑеЎОМÑÐµÑ ÐŽÐŸÐºÑЌеМÑÑ Ð² гÑÑÐ¿Ð¿Ñ Ð¿ÐŸ 100 (как ПбÑÑÑМеМП в <a href=\"_gwcgi_?l=_cgiargl_&a=p&p=about&c=documented-examples/bibtex-e\">бОблОПгÑаÑОÑеÑкПй кПллекÑОО</a>). -
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 -
collections/documented-examples/trunk/oai-e/etc/collect.cfg
r19719 r19786 395 395 396 396 Ðак ÑПлÑкП ОМÑПÑЌаÑÐžÑ ÐžÐ· ÐAI ОЌпПÑÑОÑПваМа, кПллекÑÐžÑ ÐŸÐ±ÑабаÑÑваеÑÑÑ ÐŸÐ±ÑÑÐœÑÐŒ ÑпПÑПбПЌ. ÐПМÑОгÑÑаÑОПММÑй Ñайл ПпÑеЎелÑÐµÑ Ð¿Ð»Ð°Ð³ÐžÐœ OAI, кПÑПÑÑй ПбÑабаÑÑÐ²Ð°ÐµÑ ÐŒÐµÑаЎаММÑе OAI, О плагОМ ОзПбÑажеМОй, пПÑкПлÑÐºÑ Ð² ÑÑПЌ ÑлÑÑае ЎПкÑЌеМÑÑ ÐžÑÑ 397 ПЎМПй кПллекÑОО - ÑÑП ÑÐ°Ð¹Ð»Ñ ÐžÐ·ÐŸÐ±ÑажеМОй. <!-- _text1_ -->Greenstone ПбÑÑМП ПпÑеЎелÑÐµÑ ÑзÑк ЎПкÑЌеМÑПв авÑПЌаÑОÑеÑкО, МП ÑÑО запОÑО ЌеÑаЎаММÑÑ 397 ПЎМПй кПллекÑОО - ÑÑП ÑÐ°Ð¹Ð»Ñ ÐžÐ·ÐŸÐ±ÑажеМОй. 398 <!-- _text1_ --> 399 Besides the four standard plugins (GreenstoneXMLPlugin, MetadataXMLPlugin, ArchivesInfPlugin and DirectoryPlugin), 400 the configuration file specifies the OAI plugin, which processes OAI 401 metadata, and the image plugin, because in this case the collection\'s source 402 documents are image files. 403 Greenstone ПбÑÑМП ПпÑеЎелÑÐµÑ ÑзÑк ЎПкÑЌеМÑПв авÑПЌаÑОÑеÑкО, МП ÑÑО запОÑО ЌеÑаЎаММÑÑ 398 404 ÑвлÑÑÑÑÑ ÑлОÑкПЌ МебПлÑÑОЌО ÐŽÐ»Ñ ÑПгП, ÑÑÐŸÐ±Ñ ÑÑП ÑЎелаÑÑ ÐœÐ°ÐŽÐµÐ¶ÐœÐŸ: пПÑÑÐŸÐŒÑ Ð°ÐœÐ³Ð»ÐžÐ¹ÑкОй ÑзÑк ПпÑеЎелеМ ÑвМП в паÑаЌеÑÑе <i>ÑзÑка</i> (<i>language</i>). ÐÐ»Ð°Ð³ÐžÐœÑ ÐAI аМалОзОÑÑÑÑ ÐŒÐµÑаЎаММÑе О пеÑеÑÑлаÑÑ ÐžÑ 399 405 к ÑППÑвеÑÑÑвÑÑÑÐµÐŒÑ ÑÐ°Ð¹Ð»Ñ ÐžÑÑ 400 406 ПЎМПгП ЎПкÑЌеМÑа, кПÑПÑÑй заÑеЌ ПбÑабаÑÑваеÑÑÑ ÑППÑвеÑÑÑвÑÑÑОЌ плагОМПЌ -- в ЎаММПЌ ÑлÑÑае <i>ImagePlugin</i>. ÐÑÐŸÑ Ð¿Ð»Ð°Ð³ÐžÐœ ПпÑеЎелÑÐµÑ ÑазлОÑÐœÑе веÑÑОО ÑазÑеÑÐµÐœÐžÑ ÐžÐ·ÐŸÐ±ÑÐ°Ð¶ÐµÐœÐžÑ ÐœÐ° ÑкÑаМе. 401 407 402 <!-- 403 <p> 404 _text2_ 405 406 <p> 407 _text3_ 408 --> 409 410 <p> 411 408 <p> 409 <!--_text2_--> 410 Extracted metadata from OAI records are mapped to Dublin Core Metadata Set by default. 411 As a result, classifiers and indexes in this collection are built with Dublin meatadata elements. 412 413 <p> 414 <!-- _text4_ --> 415 The <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>collection 416 configuration file</a> has a single full-text index containing 417 <i>dc.Description</i> metadata. When a document is displayed, the 418 <i>DocumentHeading</i> format statement puts out its <i>dc.Subject</i>. Then the 419 <i>DocumentText</i> statement follows this with <i>screenicon</i>, which is 420 produced by <i>ImagePlugin</i> and gives a screen-resolution version of the 421 image; it is hyperlinked to the <i>dc.OrigURL</i> metadata -- that is, the original 422 version of the image on the remote OAI site. This is followed by the image\'s 423 <i>dc.Description</i>, also with a hyperlink; the image\'s size and type, again 424 generated as metadata by <i>ImagePlugin</i>; and then <i>dc.Subject</i>, 425 <i>dc.Publisher</i>, 426 and <i>dc.Rights</i> metadata. 427 <a href=_gwcgi_?l=_cgiargl_&a=d&c=_cgiargc_&cl=search&d=_sampleoid_>This</a> 428 is the result.\n 429 430 431 <p> 412 432 ÐЌееÑÑÑ ÐŽÐ²Ð° клаÑÑОÑОкаÑПÑа пÑПÑЌПÑÑа, ПЎОМ Оз кПÑПÑÑÑ 413 433 ПÑМПваМ Ма ЌеÑаЎаММÑÑ … … 441 461 <p> 442 462 <!-- _text3_ --> 463 <p> 464 Greenstone's OAI server currently supports Dublin Core, qualified Dublin Core and rfc1807 metadata sets. The <i>oaimetadata</i> line specifies which sets should be used. For collections that use other metadata sets, 465 metadata mapping rules should be provided to map the existing metadata 466 to the sets in use. See the <i>oai.cfg</i> file for details.\n 443 467 " 444 468 -
collections/documented-examples/trunk/text-for-translation.txt
r19394 r19786 211 211 metadata mapping rules should be provided to map the existing metadata 212 212 to the sets in use. See the <i>oai.cfg</i> file for details.\n 213 214 oai._text4_:The <a href=\"_httpcollection_/etc/collect.cfg\" target=collect.cfg>collection 215 configuration file</a> has a single full-text index containing 216 <i>dc.Description</i> metadata. When a document is displayed, the 217 <i>DocumentHeading</i> format statement puts out its <i>dc.Subject</i>. Then the 218 <i>DocumentText</i> statement follows this with <i>screenicon</i>, which is 219 produced by <i>ImagePlugin</i> and gives a screen-resolution version of the 220 image; it is hyperlinked to the <i>dc.OrigURL</i> metadata -- that is, the original 221 version of the image on the remote OAI site. This is followed by the image\'s 222 <i>dc.Description</i>, also with a hyperlink; the image\'s size and type, again 223 generated as metadata by <i>ImagePlugin</i>; and then <i>dc.Subject</i>, 224 <i>dc.Publisher</i>, 225 and <i>dc.Rights</i> metadata. 226 <a href=_gwcgi_?l=_cgiargl_&a=d&c=_cgiargc_&cl=search&d=_sampleoid_>This</a> 227 is the result.\n -
collections/documented-examples/trunk/wrdpdf-e/etc/collect.cfg
r19691 r19786 235 235 ЎПкÑЌеМÑПв Word (МапÑОЌеÑ, ÐŸÑ ÑÑаÑÑÑ 236 236 ÑОÑÑеЌ ÐакОМÑПÑа), О ОМПгЎа ÑекÑÑ ÑжаÑМП ОзвлекаеÑÑÑ. ÐекПÑПÑÑе PDF ÑÐ°Ð¹Ð»Ñ ÐœÐµ ÑПзЎаÑÑ ÐœÐžÐºÐ°ÐºÐŸÐ³ÐŸ ЌаÑОММПÑОÑаеЌПгП ÑекÑÑа вППбÑе, а вЌеÑÑП ÑÑПгП вклÑÑаÑÑ Ð¿ÐŸÑлеЎПваÑелÑМПÑÑÑ <i>ОзПбÑажеМОй</i> ÑÑÑаМОÑÑ, Оз кПÑПÑÑÑ 237 ÑекÑÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐ·Ð²Ð»ÐµÑеМ ÑПлÑкП пÑÑеЌ ПпÑОÑеÑкПгП ÑаÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ (OCR), ÑÑП в Greenstone Ме пÑеЎÑÑЌПÑÑеМП. <!-- _text1_ --> 237 ÑекÑÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐ·Ð²Ð»ÐµÑеМ ÑПлÑкП пÑÑеЌ ПпÑОÑеÑкПгП ÑаÑÐ¿ÐŸÐ·ÐœÐ°Ð²Ð°ÐœÐžÑ (OCR), ÑÑП в Greenstone Ме пÑеЎÑÑЌПÑÑеМП. 238 <!-- _text1_ --> 239 If you encounter these problems, you 240 can either remove the offending documents from your collection, or try using 241 some of the advanced plugin options to process the documents in different ways. 242 For more information, see the Enhanced PDf and Word tutorials on the 243 <a href=\'http://wiki.greenstone.org/wiki/index.php/Tutorial_exercises\'>Greenstone wiki</a>. 238 244 <p> 239 245
Note:
See TracChangeset
for help on using the changeset viewer.