- Timestamp:
- 2010-09-20T12:12:11+12:00 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/trunk/tutorials/xml-source/tutorial_en.xml
r22922 r22927 3039 3039 </Heading> 3040 3040 <NumberedItem> 3041 <Text id="0790a">Open a DOS window to access the command-line prompt. This facility should be located somewhere within your <Menu>Start → Programs</Menu> menu, but details vary between different Windows systems. If you cannot locate it , select <Menu>Start → Run</Menu> and enter <Command>cmd</Command> in the popup window that appears.</Text>3041 <Text id="0790a">Open a DOS window to access the command-line prompt. This facility should be located somewhere within your <Menu>Start → Programs</Menu> menu, but details vary between different Windows systems. If you cannot locate it and you are running <AutoText text="Windows XP"/>, select <Menu>Start → Run</Menu> and enter <Command>cmd</Command> in the popup window that appears. In either <AutoText text="Windows Vista"/> or <AutoText text="Windows 7"/>, click the Start button and type <Command>cmd</Command> in the search box at the bottom of the Start menu.</Text> 3042 3042 </NumberedItem> 3043 3043 <NumberedItem> … … 3073 3073 <Text id="gems-1">Editing metadata sets</Text> 3074 3074 </Title> 3075 <Version initial="2.70w" current="2.8 2"/>3075 <Version initial="2.70w" current="2.84"/> 3076 3076 <Content> 3077 3077 <Text id="gems-2">GEMS (Greenstone Editor for Metadata Sets) can be used to modify existing metadata sets or create new ones. GEMS is launched from the Librarian Interface when you want to create a new metadata set, or edit an existing one. In this exercise, we run GEMS outside of the Librarian Interface.</Text> … … 3080 3080 </Heading> 3081 3081 <NumberedItem> 3082 <Text id="gems-4">Start the Greenstone Editor for Metadata Sets (GEMS), for versions 2.81 and greater:</Text> 3083 <Text id="gems-5"><Menu>Start → All Programs → Greenstone-2.81 → Metadata Set Editor</Menu></Text> 3084 <Text id="gems-5a">and for versions below 2.81:</Text> 3085 <Text id="gems-5b"><Menu>Start → All Programs → Greenstone Digital Library Software → Greenstone Editor for Metadata Sets</Menu></Text> 3082 <Text id="gems-4">Start the Greenstone Editor for Metadata Sets (GEMS)</Text> 3083 <Text id="gems-5"><Menu>Start → All Programs → Greenstone-2.84 → Metadata Set Editor (GEMS)</Menu></Text> 3086 3084 </NumberedItem> 3087 3085 <NumberedItem> … … 3116 3114 </Title> 3117 3115 <SampleFiles folder="demo"/> 3118 <Version initial="2.70w" current="2.8 1"/>3116 <Version initial="2.70w" current="2.84"/> 3119 3117 <Content> 3120 3118 <Text id="indexers-2">Greenstone supports three indexers <b>MG</b>, <b>MGPP</b> and <b>Lucene</b>. </Text> 3121 3119 <Text id="indexers-3"><b>MG</b> is the original indexer used by Greenstone which is described in the book <b>"Managing Gigabytes"</b>. It does section level indexing and compression of the source documents. <b>MG</b> is implemented in C. </Text> 3122 3120 <Text id="indexers-4"><b>MGPP</b> is re-implementation of <b>MG</b> that provides word-level indexes and enables proximity, phrase and field searching. <b>MGPP</b> is implemented in C++ and is the default indexer for new collections.</Text> 3123 <Text id="indexers-5"><b>Lucene</b> ( http://lucene.apache.org/) is java-based full-featured text indexing and searching system developed by Apache. It provides a similar range of search functionality to MGPP with the addition of single-character wildcards and range searching. It was added to Greenstone to facilitate incremental collection building, which <b>MG</b> and <b>MGPP</b> can't provide.</Text>3121 <Text id="indexers-5"><b>Lucene</b> (<Link>http://lucene.apache.org/</Link>) is java-based full-featured text indexing and searching system developed by Apache. It provides a similar range of search functionality to MGPP with the addition of single-character wildcards and range searching. It was added to Greenstone to facilitate incremental collection building, which <b>MG</b> and <b>MGPP</b> can't provide.</Text> 3124 3122 <Heading> 3125 3123 <Text id="indexers-6">Build with Lucene</Text> … … 3135 3133 </NumberedItem> 3136 3134 <NumberedItem> 3137 <Text id="indexers-9">Go to the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that associated with each directory. Go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section in the <AutoText key="glidict::GUI.Design"/> panel. The <b>MG indexer</b> is in use because the original <b>Greenstone Demo</b> collection, which this collection is based on, uses <b>MGindexer</b>.</Text>3135 <Text id="indexers-9">Go to the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that associated with each directory. Go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section in the <AutoText key="glidict::GUI.Design"/> panel. The <b>MGPP indexer</b> is in use because the <b>Greenstone Demo</b> collection, which this collection is based on, uses <b>MGPP indexer</b>.</Text> 3138 3136 </NumberedItem> 3139 3137 <NumberedItem> … … 3236 3234 <SampleFiles folder="demo_NewFiles"/> 3237 3235 <Prerequisite id="indexers"/> 3238 <Version initial="2.71" current="2.8 1"/>3236 <Version initial="2.71" current="2.84"/> 3239 3237 <Content> 3240 3238 <Text id="depositor-2">Collections built with <i>Lucene</i> indexer support incremental addition of documents. The <b>import</b> and <b>build</b> process by default delete old index files in the <b>index</b> directory and intermediate files in the <b>archives</b> directory. With incremental building, the <b>import</b> and <b>build</b> process will keep the old files and only process the new ones that havenât been indexed.</Text>
Note:
See TracChangeset
for help on using the changeset viewer.
