Changeset 27118 for documentation
- Timestamp:
- 2013-03-25T11:44:21+13:00 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/trunk/tutorials/xml-source/tutorial_en.xml
r27117 r27118 2829 2829 <Prerequisite id="multimedia_collection_explore"/> 2830 2830 <SampleFiles folder="beatles"/> 2831 <Version initial="2.60" current="2.85 "/>2831 <Version initial="2.60" current="2.85|3.05"/> 2832 2832 <Content> 2833 2833 <Comment> … … 2957 2957 <Tab n="2"/></gsf:when><br /> 2958 2958 <Tab n="2"/><gsf:when test='equals' test-value='Supplementary'><br /> 2959 <Tab n="3"/><gsf:link type="source"><gsf:metadata name="srcicon"/></gsf:link> <gsf:link type="document"><gsf:icon type="document"/></gsf:link><br /> 2959 <Tab n="3"/><gsf:link type="source"><gsf:metadata name="srcicon"/></gsf:link><br /> 2960 <Tab n="3" /><gsf:link type="document"><gsf:icon type="document"/></gsf:link><br /> 2960 2961 <Tab n="2"/></gsf:when><br /> 2961 2962 <Tab n="2"/><gsf:otherwise><br /> … … 3015 3016 </Heading> 3016 3017 <NumberedItem> 3017 <Text id="0597">There are sometimes several documents with the same title. For example, <AutoText text="All My Loving" type="italics"/> appears both as lyrics and tablature (under <AutoText text="ALL MY LOVING" type="italics"/>). The < AutoText key="coredm::_Global:labelTitle_"/> browser might be improved by grouping these together under a bookshelf icon. This is a job for an <AutoText text="AZCompactList"/>. In the previous tutorial we showed how to use the <AutoText text="bookshelf_type"/> option in <AutoText text="List"/> classifier to group documents with the same metadata value (<AutoText key="metadata::dc.Format"/> in that case) in one bookshelf. Here we use <AutoText text="AZCompactList"/> instead.</Text>3018 <Text id="0597">There are sometimes several documents with the same title. For example, <AutoText text="All My Loving" type="italics"/> appears both as lyrics and tablature (under <AutoText text="ALL MY LOVING" type="italics"/>). The <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> browser might be improved by grouping these together under a bookshelf icon. This is a job for an <AutoText text="AZCompactList"/>. In the previous tutorial we showed how to use the <AutoText text="bookshelf_type"/> option in <AutoText text="List"/> classifier to group documents with the same metadata value (<AutoText key="metadata::dc.Format"/> in that case) in one bookshelf. Here we use <AutoText text="AZCompactList"/> instead.</Text> 3018 3019 <BulletList> 3019 3020 <Bullet> … … 3056 3057 </MajorVersion> 3057 3058 <MajorVersion number="3"> 3058 <Text id="0606-3">Make the bookshelves show how many documents they contain by modifying the <AutoText text="VList classifierNode"/> template of the <AutoText text="browse"/> format feature in the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel. Remove the portion highlighted below:</Text> 3059 <Format> 3060 <Tab n="1"/>...<br /> 3061 <Tab n="1"/><xsl:call-template name="choose-title"/><br /> 3062 <Tab n="1"/><highlight><gsf:switch><br /> 3063 <Tab n="2"/><gsf:metadata name="Source"/><br /> 3064 <Tab n="2"/><gsf:when test="exists"><br /> 3065 <Tab n="3"/><br/><br /> 3066 <Tab n="3"/><i>(<gsf:metadata name="Source"/>)</i><br /> 3067 <Tab n="2"/></gsf:when><br /> 3068 <Tab n="1"/></gsf:switch><br /> 3069 </td></highlight> 3070 </Format> 3071 And replace it with the statements highlighted here: 3072 <Format> 3073 <Tab n="1"/>...<br /> 3074 <Tab n="1"/><xsl:call-template name="choose-title"/><br /> 3075 <highlight></td><br /> 3076 <td><br /> 3059 <Text id="0606-3">Make the bookshelves show how many documents they contain by modifying the <AutoText text="VList classifierNode"/> template of the <AutoText text="browse"/> format feature in the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel. Insert the highlighted statements:</Text> 3060 <Format> 3061 <Tab n="1"/><gsf:template match="classifierNode[@classifierStyle = 'VList']"><br /> 3062 <Tab n="1"/>...<br /> 3063 <Tab n="1"/><gsf:metadata name="Title"/><br /> 3064 </td><br /> 3065 <highlight><td><br /> 3077 3066 <Tab n="1"/>(<gsf:metadata name="numleafdocs"/>)<br /> 3078 3067 </td></highlight> 3068 <gsf:template<br /> 3079 3069 </Format> 3080 3070 <Text id="0606-3a">The complete format statement for the <AutoText text="VList classifierNode"/> template of the <AutoText text="browse"/> format feature can be copied from <Path>sample_files → beatles → format_tweaks → show_num_docs_3.txt</Path>.</Text> … … 3087 3077 <NumberedItem> 3088 3078 <Text id="0612">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section on the <AutoText key="glidict::GUI.Design"/> panel, add a <AutoText text="Phind"/> classifier. Leave the settings at their defaults: this generates a phrase browsing classifier that sources its phrases from <i>Title</i> and <i>text</i>.</Text> 3089 <Text id="0612b"><b>Build</b> the collection again and <b>preview</b> it. Select the new < AutoText key="coredm::_Global:labelPhrase_"/> option from the navigation bar. Enter a single word in the text box, such as <AutoText text="band" type="quotes"/>. The phrase browser will present you with phrases found in the collection containing the search term. This can provide a useful way of browsing a very large collection. Note that even though it is called a phrase browser, only single terms can be used as the starting point for browsing.</Text>3079 <Text id="0612b"><b>Build</b> the collection again and <b>preview</b> it. Select the new <MajorVersion number="2"><AutoText key="coredm::_Global:labelPhrase_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::PhindPhraseBrowse::PhindApplet.name" /></MajorVersion> option from the navigation bar. Enter a single word in the text box, such as <AutoText text="band" type="quotes"/>. The phrase browser will present you with phrases found in the collection containing the search term. This can provide a useful way of browsing a very large collection. Note that even though it is called a phrase browser, only single terms can be used as the starting point for browsing.</Text> 3090 3080 </NumberedItem> 3091 3081 <Heading> … … 3131 3121 </Heading> 3132 3122 <Comment> 3133 <Text id="0618a">We now clean up the < AutoText key="coredm::_Global:labelTitle_"/> browser.</Text>3123 <Text id="0618a">We now clean up the <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> browser.</Text> 3134 3124 </Comment> 3135 3125 <NumberedItem> … … 3147 3137 </NumberedItem> 3148 3138 <Comment> 3149 <Text id="0640">One powerful use of regular expressions in the exercise was to clean up the < AutoText key="coredm::_Global:labelTitle_"/> browser. Perhaps the best way of doing this would be to have proper title metadata. The metadata extracted from HTML files is messy and inconsistent, and this was reflected in the original <AutoText key="coredm::_Global:labelTitle_" type="italics"/> browser. Defining proper title metadata would be simple but rather laborious. Instead, we have opted to use regular expressions in the <AutoText text="AZCompactList"/> classifier to clean up the title metadata. This is difficult to understand, and a bit fiddly to do, but if you can cope with its idiosyncrasies it provides a quick way to clean up the extracted metadata and avoid having to enter a large amount of metadata.</Text>3139 <Text id="0640">One powerful use of regular expressions in the exercise was to clean up the <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> browser. Perhaps the best way of doing this would be to have proper title metadata. The metadata extracted from HTML files is messy and inconsistent, and this was reflected in the original <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> browser. Defining proper title metadata would be simple but rather laborious. Instead, we have opted to use regular expressions in the <AutoText text="AZCompactList"/> classifier to clean up the title metadata. This is difficult to understand, and a bit fiddly to do, but if you can cope with its idiosyncrasies it provides a quick way to clean up the extracted metadata and avoid having to enter a large amount of metadata.</Text> 3150 3140 </Comment> 3151 3141 <Heading> … … 3165 3155 <NumberedItem> 3166 3156 <Text id="0645a">Open up another file browser, and locate the small beatles collection in your Greenstone installation:</Text> 3167 <Path>Greenstone → collect → smallbea</Path>3157 <Path>Greenstone<MajorVersion number="3">3 → web → sites → localsite </MajorVersion> → collect → smallbea</Path> 3168 3158 <Text id="0645b"><AutoText text="smallbea"/> is the folder name generated by Greenstone for this collection. You can determine what the folder name is for a collection by looking at the title bar of the Librarian Interface: the folder name is displayed in brackets after the collection name.</Text> 3169 3159 </NumberedItem> … … 3185 3175 </MajorVersion> 3186 3176 <NumberedItem> 3187 <Text id="0648">Re-edit <MajorVersion number="2"><AutoText text="VList" /> your format statement</MajorVersion><MajorVersion number="3">the previously edited portion of the <AutoText text="documentNode"/> format statement of the <AutoText text="browse"/> format feature</MajorVersion> (in <AutoText key="glidict::CDM.GUI.Formats"/> on the <AutoText key="glidict::GUI.Format"/> panel) to be the following. You can copy this text from the file <Path>sample_files → beatles → format_tweaks → multi_icons<MajorVersion number="3">_3</MajorVersion>.txt</Path>.< /Text>3177 <Text id="0648">Re-edit <MajorVersion number="2"><AutoText text="VList" /> your format statement</MajorVersion><MajorVersion number="3">the previously edited portion of the <AutoText text="documentNode"/> format statement of the <AutoText text="browse"/> format feature</MajorVersion> (in <AutoText key="glidict::CDM.GUI.Formats"/> on the <AutoText key="glidict::GUI.Format"/> panel) to be the following. You can copy this text from the file <Path>sample_files → beatles → format_tweaks → multi_icons<MajorVersion number="3">_3</MajorVersion>.txt</Path>.<MajorVersion number="3">Change: </MajorVersion></Text> 3188 3178 <Format> 3189 3179 <MajorVersion number="2"> … … 3208 3198 </MajorVersion> 3209 3199 <MajorVersion number="3"> 3200 <td valign="top"><br /> 3201 <Tab n="1"/><highlight><gsf:switch><br /> 3202 <Tab n="2"/><gsf:metadata name="dc.Format"/><br /> 3203 <Tab n="2"/><gsf:when test='equals' test-value='Audio'><br /> 3204 <Tab n="3"/><gsf:link type="source"><gsf:metadata name="srcicon"/></gsf:link><br /> 3205 <Tab n="2"/></gsf:when><br /> 3206 <Tab n="2"/><gsf:when test='equals' test-value='Images'><br /> 3207 <Tab n="3"/><gsf:link type="source"><gsf:metadata name="thumbicon"/></gsf:link><br /> 3208 <Tab n="2"/></gsf:when><br /> 3209 <Tab n="2"/><gsf:when test='equals' test-value='Supplementary'><br /> 3210 <Tab n="3"/><gsf:link type="source"><gsf:metadata name="srcicon"/></gsf:link> <gsf:link type="document"><gsf:icon type="document"/></gsf:link><br /> 3211 <Tab n="2"/></gsf:when><br /> 3212 <Tab n="2"/><gsf:otherwise><br /> 3213 <Tab n="3"/><gsf:link type="document"><gsf:icon type="document"/></gsf:link><br /> 3214 <Tab n="2"/></gsf:otherwise><br /> 3215 <Tab n="1"/></gsf:switch></highlight><br /> 3216 </td> 3217 </MajorVersion> 3218 </Format> 3219 <MajorVersion number="3"> 3220 <Text id="0648a">to this:</Text> 3221 <Format> 3210 3222 <td valign="top"><br /> 3211 < Tab n="1"/><gsf:switch><br />3223 <highlight><Tab n="1"/><gsf:switch><br /> 3212 3224 <Tab n="2"/><gsf:metadata name="dc.Format"/><br /> 3213 3225 <Tab n="2"/><gsf:when test="equals" test-value="Lyrics"><br /> … … 3254 3266 <Tab n="3"/></gsf:link><br /> 3255 3267 <Tab n="2"/></gsf:when><br /> 3256 <Tab n="1"/></gsf:switch><br /> 3268 <Tab n="1"/></gsf:switch><br /></highlight> 3257 3269 </td> 3258 </MajorVersion>3259 </ Format>3270 </Format> 3271 </MajorVersion> 3260 3272 </NumberedItem> 3261 3273 <NumberedItem> … … 3324 3336 </Title> 3325 3337 <SampleFiles folder="niupepa"/> 3326 <Version initial="2.60" current="2.85 "/>3338 <Version initial="2.60" current="2.85|3.05"/> 3327 3339 <Content> 3328 3340 <Comment> … … 3342 3354 </Comment> 3343 3355 <NumberedItem> 3344 <Text id="0681">Go to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection and <b>preview</b> the result. Search for <AutoText text="waka" type="quoted"/> and view one of the titles listed (all three appear as <AutoText text="Te Whetu o Te Tau" type="italics"/>). Browse by < AutoText key="coredm::_Global:labelTitle_"/> and view one of the <AutoText text="Te Waka o Te Iwi" type="italics"/> newspapers. Note that only the <AutoText text="Te Whetu o Te Tau" type="italics"/> newspapers have text; <AutoText text="Te Waka o Te Iwi" type="italics"/> papers don't.</Text>3356 <Text id="0681">Go to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection and <b>preview</b> the result. Search for <AutoText text="waka" type="quoted"/> and view one of the titles listed (all three appear as <AutoText text="Te Whetu o Te Tau" type="italics"/>). Browse by <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> and view one of the <AutoText text="Te Waka o Te Iwi" type="italics"/> newspapers. Note that only the <AutoText text="Te Whetu o Te Tau" type="italics"/> newspapers have text; <AutoText text="Te Waka o Te Iwi" type="italics"/> papers don't.</Text> 3345 3357 </NumberedItem> 3346 3358 <Comment> … … 3351 3363 </Heading> 3352 3364 <Comment> 3353 <Text id="0684">Under < AutoText key="coredm::_Global:labelTitle_"/>, documents from the same series are repeated without any distinguishing features such as date, volume or number. It would be better to group them by series title and display other information within each group. This can be accomplished using the <AutoText text="-bookshelf_type"/> option to the <AutoText text="List"/> classifier, and tuning the classifier's format statement.</Text>3365 <Text id="0684">Under <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion>, documents from the same series are repeated without any distinguishing features such as date, volume or number. It would be better to group them by series title and display other information within each group. This can be accomplished using the <AutoText text="-bookshelf_type"/> option to the <AutoText text="List"/> classifier, and tuning the classifier's format statement.</Text> 3354 3366 </Comment> 3355 3367 <NumberedItem> … … 3360 3372 </NumberedItem> 3361 3373 <NumberedItem> 3362 <Text id="0686a"><b>Build</b> the collection, and <b>preview</b> the < AutoText key="coredm::_Global:labelTitle_" type="italics"/> list.</Text>3363 </NumberedItem> 3364 <NumberedItem> 3365 <Text id="0687">Now we change the format statement for < AutoText key="coredm::_Global:labelTitle_" type="italics"/> to display more information about the documents. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, select the <AutoText text="dc.Title;ex.Title"/> classifier (CL1) in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list<MajorVersion number="2">, and <AutoText text="VList"/> in the <AutoText key="glidict::CDM.FormatManager.Part"/> list.</MajorVersion> Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to your collection.3374 <Text id="0686a"><b>Build</b> the collection, and <b>preview</b> the <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> list.</Text> 3375 </NumberedItem> 3376 <NumberedItem> 3377 <Text id="0687">Now we change the format statement for <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> to display more information about the documents. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, select the <AutoText text="dc.Title;ex.Title"/> classifier (CL1) in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list.<MajorVersion number="2">, and <AutoText text="VList"/> in the <AutoText key="glidict::CDM.FormatManager.Part"/> list.</MajorVersion> Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to your collection. 3366 3378 <MajorVersion number="2">Delete the contents of the <AutoText key="glidict::CDM.FormatManager.Editor"/> box, and add the following text. (This format statement can be copied and pasted from the file <Path>sample_files → niupepa → formats → titles_tweak.txt</Path>.)</MajorVersion> 3367 <MajorVersion number="3">Edit the contents of the <AutoText text=" browse"/>format statement by removing the following in the <AutoText text="documentNode"/> template:</MajorVersion>3379 <MajorVersion number="3">Edit the contents of the <AutoText text="dc.Title;ex.Title"/> classifier format statement by removing the following in the <AutoText text="documentNode"/> template:</MajorVersion> 3368 3380 </Text> 3369 3381 <MajorVersion number="2"> … … 3404 3416 <Format> 3405 3417 <td valign="top"><br /> 3406 <Tab n="1"/>Volume: <gsf:metadata name="Volume"/> Number:<gsf:metadata name="Number"/> Date:<gsf:metadata format="formatDate" name="Date"/><br />3418 <Tab n="1"/>Volume: <gsf:metadata name="Volume"/> Number: <gsf:metadata name="Number"/> Date: <gsf:metadata format="formatDate" name="Date"/><br /> 3407 3419 </td><br /> 3408 3420 </Format> … … 3416 3428 </NumberedItem> 3417 3429 <NumberedItem> 3418 <Text id="0690a">Refresh in the web browser to view the new < AutoText key="coredm::_Global:labelTitle_" type="italics"/> list.</Text>3430 <Text id="0690a">Refresh in the web browser to view the new <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> list.</Text> 3419 3431 <Text id="0687c">As a consequence of using the <AutoText text="bookshelf_type"/> option of the <AutoText text="List"/> classifier, bookshelf icons appear when titles are browsed. This revised format statement has the effect of specifying in brackets how many items are contained within a bookshelf<MajorVersion number="3">, for classifier nodes</MajorVersion>. <MajorVersion number="2">It works by exploiting the fact that only bookshelf icons define <Format>[numleafdocs]</Format> metadata.</MajorVersion> For document nodes, Title is not displayed. Instead, Volume, Number and Date information are displayed.</Text> 3420 3432 </NumberedItem> … … 3427 3439 <MajorVersion number="3"> 3428 3440 <NumberedItem> 3429 <Text id="0686b-3">In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, select <AutoText text="DateList" /> in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to your collection. Replace the final <Format><td></Format> table cell element of the new <AutoText text="DateList"/>'s <AutoText text="VList classifierNode"/> template with:</Text> 3430 <Format> 3441 <Text id="0686b-3">In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, select <AutoText text="DateList" /> in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to your collection. In the <AutoText text="documentNode"/> template of the new <AutoText text="DateList"/> feature, replace:</Text> 3442 <Format> 3443 <gsf:switch><br /> 3444 <Tab n="1"/><gsf:metadata name="Source"/><br /> 3445 <Tab n="1"/><gsf:when test="exists"/><br /> 3446 <Tab n="2"/><br/><br /> 3447 <Tab n="2"/><i>(<gsf:metadata name="Source">)</i><br /> 3448 <Tab n="1"/></gsf:when><br /> 3449 </gsf:switch> 3450 </Format> 3451 <Text id="0686b-31a">with this:</Text> 3452 <Format> 3453 </td><br /> 3431 3454 <td valign="top"><br /> 3432 3455 <Tab n="1"/><xsl:call-template name="choose-date"/><br /> 3433 </td>3434 3456 </Format> 3435 3457 </NumberedItem> … … 3450 3472 </MajorVersion> 3451 3473 <NumberedItem> 3452 <Text id="0686b"><b>Build</b> the collection, and <b>preview</b> the <AutoText key="coredm::_Global:labelDate_" type="italics"/> list.</Text> 3453 </NumberedItem> 3454 <NumberedItem> 3455 <Text id="0691">The <AutoText key="coredm::_Global:labelDate_" type="italics"/> list groups documents by date. Greenstone's internal date format is YYYYMMDD, for example 18580601, and this is crucial for the <AutoText text="DateList" /> classifier to correctly parse date metadata and generate an ordered date list. However, the date has been made to look nice by adding a <MajorVersion number="2"><AutoText text="[format:]"/> macro</MajorVersion><MajorVersion number="3">"<AutoText text="format=formatDate"/>" attribute</MajorVersion> to Date metadata in the format statement.</Text> 3474 <Text id="0686b"><b>Build</b> the collection, and <b>preview</b> the <MajorVersion number="2"><AutoText key="coredm::_Global:labelDate_" type="italics"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Date.buttonname"/> 3475 </MajorVersion> list.</Text> 3476 </NumberedItem> 3477 <NumberedItem> 3478 <Text id="0691">The <MajorVersion number="2"><AutoText key="coredm::_Global:labelDate_" type="italics"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Date.buttonname"/> 3479 </MajorVersion> list groups documents by date. Greenstone's internal date format is YYYYMMDD, for example 18580601, and this is crucial for the <AutoText text="DateList" /> classifier to correctly parse date metadata and generate an ordered date list. However, the date has been made to look nice by adding a <MajorVersion number="2"><AutoText text="[format:]"/> macro</MajorVersion><MajorVersion number="3">"<AutoText text="format=formatDate"/>" attribute</MajorVersion> to Date metadata in the format statement.</Text> 3456 3480 </NumberedItem> 3457 3481 <NumberedItem> … … 3479 3503 </Format> 3480 3504 </MajorVersion> 3481 <Text id="0691c">Refresh in the web browser to view the new <AutoText key="coredm::_Global:labelDate_" type="italics"/> list. The dates are now shown in internal format. </Text> 3505 <Text id="0691c">Refresh in the web browser to view the new <MajorVersion number="2"><AutoText key="coredm::_Global:labelDate_" type="italics"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Date.buttonname"/> 3506 </MajorVersion> list. The dates are now shown in internal format. </Text> 3482 3507 </NumberedItem> 3483 3508 <NumberedItem> … … 3651 3676 <SampleFiles folder="niupepa"/> 3652 3677 <Prerequisite id="scanned_image_collection"/> 3653 <Version initial="2.70" current="2.85 "/>3678 <Version initial="2.70" current="2.85|3.05"/> 3654 3679 <Content> 3655 3680 <Comment> … … 3692 3717 1:images/12_3_6_1.gif:text/12_3_6_1.txt 3693 3718 </Format> 3694 <Text id="sc16">Note that if there is no text file, you can leave that space blank. You need to add a line for each page in the document. Make sure you increment the page number as well as the image number for each line. </Text>3695 </NumberedItem> 3696 <NumberedItem> 3697 <Text id="sc17">Save the file using <b>Filename </b> <AutoText text="12_3_6.item" type="italics"/>, and save as a plain text document. (If you are using Windows, make sure the file doesn't accidentally end up getting saved as <AutoText text="12_3_6.item.txt" type="italics"/>.) Back in the <AutoText key="glidict::GUI.Gather"/> panel of the Librarian Interface, locate the new file in the <b>Workspace</b> tree, and drag it into the collection, adding it to the <AutoText text="12"/> folder.</Text>3719 <Text id="sc16">Note that if there is no text file, you can leave that space blank. You need to add a line for each page in the document. Make sure you increment the page number as well as the image number for each line. (The full text for this file can be copied from <Path>sample_files → niupepa → formats → 12item_text.txt</Path>.)</Text> 3720 </NumberedItem> 3721 <NumberedItem> 3722 <Text id="sc17">Save the file using <b>Filename </b> <AutoText text="12_3_6.item" type="italics"/>, and save as a plain text document. (If you are using Windows, make sure the file doesn't accidentally end up getting saved as <AutoText text="12_3_6.item.txt" type="italics"/>.) Back in the <AutoText key="glidict::GUI.Gather"/> panel of the Librarian Interface, locate the new file in the <b>Workspace</b> tree, and drag it into the collection, adding it to the <AutoText text="12"/> folder.</Text> 3698 3723 </NumberedItem> 3699 3724 <NumberedItem> … … 3709 3734 </NumberedItem> 3710 3735 <NumberedItem> 3711 <Text id="sc23">Open up the file <Path>xml → 23 → 23__2.item</Path> and have a look at the XML. This is <AutoText text="Number "/> <AutoText text="2" type="italics"/> of the newspaper titled <AutoText text="Matariki 1881" type="italics"/>. The contents of this document have been grouped into two sections: <AutoText text="Supplementary Material"/>, which contains an <AutoText text="Abstract"/>, and <AutoText text="Newspaper Pages"/>, which contains the page images (and OCR text). </Text>3736 <Text id="sc23">Open up the file <Path>xml → 23 → 23__2.item</Path> and have a look at the XML. This is <AutoText text="Number "/> <AutoText text="2" type="italics"/> of the newspaper titled <AutoText text="Matariki 1881" type="italics"/>. The contents of this document have been grouped into two sections: <AutoText text="Supplementary Material"/>, which contains an <AutoText text="Abstract"/>, and <AutoText text="Newspaper Pages"/>, which contains the page images (and OCR text). </Text> 3712 3737 </NumberedItem> 3713 3738 <NumberedItem> … … 3782 3807 </Title> 3783 3808 <SampleFiles folder="oai"/> 3784 <Version initial="2.60" current="2.85 "/>3809 <Version initial="2.60" current="2.85|3.05"/> 3785 3810 <Content> 3786 3811 <Comment> … … 3971 3996 </Title> 3972 3997 <Prerequisite id="simple_image_collection"/> 3973 <Version initial="2.85" current="2.85 "/>3998 <Version initial="2.85" current="2.85|3.05"/> 3974 3999 <Content> 3975 4000 <Comment> … … 4100 4125 </Title> 4101 4126 <Prerequisite id="GS_OAI_server"/> 4102 <Version initial="2.60" current="2.85 "/>4127 <Version initial="2.60" current="2.85|3.05"/> 4103 4128 <Content> 4104 4129 <Comment> … … 4227 4252 </NumberedItem> 4228 4253 <NumberedItem> 4229 <Text id="0759">In your Windows file browser, locate the <Path>archives</Path> folder for the collection you are working with (in <Path>Greenstone → collect → <collname> → archives</Path>). For each document in the collection, Greenstone has generated two files: <Path>docmets.xml</Path>, the core METS description, and <Path>doctxt.xml</Path>, a supporting file. (Note: unless you are connected to the Internet you may be unable to view <Path>doctxt.xml</Path> in your web browser, because it refers to a remote resource.) Depending on the source documents there may be additional files, such as the images used within a web page. One of METS' many features is the ability to reference information in external XML files. Greenstone uses this to tie the content of the document, which is stored in the external XML file <Path>doctxt.xml</Path>, to its hierarchical structure, which is described in the core METS file <Path>docmets.xml</Path>.</Text>4254 <Text id="0759">In your Windows file browser, locate the <Path>archives</Path> folder for the collection you are working with (in <Path>Greenstone<MajorVersion number="3">3 → web → sites → localsite</MajorVersion> → collect → <collname> → archives</Path>). For each document in the collection, Greenstone has generated two files: <Path>docmets.xml</Path>, the core METS description, and <Path>doctxt.xml</Path>, a supporting file. (Note: unless you are connected to the Internet you may be unable to view <Path>doctxt.xml</Path> in your web browser, because it refers to a remote resource.) Depending on the source documents there may be additional files, such as the images used within a web page. One of METS' many features is the ability to reference information in external XML files. Greenstone uses this to tie the content of the document, which is stored in the external XML file <Path>doctxt.xml</Path>, to its hierarchical structure, which is described in the core METS file <Path>docmets.xml</Path>.</Text> 4230 4255 </NumberedItem> 4231 4256 </Content>
Note:
See TracChangeset
for help on using the changeset viewer.
