Changeset 29369 for main/trunk/gli/help/en/help.xml

Timestamp:

2014-10-16T09:35:41+13:00 (10 years ago)

Author:

kjdon

Message:

small changes

File:

• main/trunk/gli/help/en/help.xml (modified) (2 diffs)

main/trunk/gli/help/en/help.xml

@@ -242 +242 @@
 </Title>
 <Text id="105">This section describes how to import previously assigned metadata: metadata assigned to documents before they were added to the collection.</Text>
-<Text id="106">If metadata in a form recognized by the Librarian Interface has been previously assigned to a file -- for example, when you choose documents from an existing Greenstone collection -- it is imported automatically when you add the file. To do this, the metadata must be mapped to the metadata sets available in the collection.</Text>
-<Text id="107">The Librarian Interface prompts for the necessary information.  The prompt gives brief instructions and then shows the name of the metadata element that is being imported, just as it appears in the source file.  This field cannot be edited or changed.  Next you choose what metadata set the new element should map to, and then the appropriate metadata element in that set.  The system automatically selects the closest match, in terms of set and element, for the new metadata.</Text>
+<Text id="106">If a document has some assigned metadata in a form recognized by the Librarian Interface (i.e. in a metadata.xml file in the same folder as the document) -- for example, when you choose documents from an existing Greenstone collection -- it is imported automatically when you add the document to a (new) collection. Greenstone will recognize the metadata.xml (which does not have to be added to the collection), and automatically attempt to import the metadata. </Text>
+<Text id="107">To import the metadata, the metadata must be mapped to the metadata sets available in the collection. The Librarian Interface prompts for the necessary information.  The prompt gives brief instructions and then shows the name of the metadata element that is being imported, just as it appears in the source file.  This field cannot be edited or changed.  Next you choose what metadata set the new element should map to, and then the appropriate metadata element in that set.  The system automatically selects the closest match, in terms of set and element, for the new metadata.</Text>
 <Text id="108">Having checked the mapping, you can choose "Add" to add the new metadata element to the chosen metadata set.  (This is only enabled if there is no element of the same name within the chosen set.) "Merge" maps the new element to the one chosen by the user.  Finally, "Ignore" does not import any metadata with this element name.  Once you have specified how to import a certain piece of metadata, the mapping information is retained for the collection's lifetime.</Text>
 <Text id="109">For details on the metadata.xml files which Greenstone uses to store the metadata, see Chapter 2 of the Greenstone Developer's Guide -- Getting the most out of your documents.</Text>
@@ -317 +317 @@
 <Text id="150">To remove a filter, select it from the list and click "Remove Filter".</Text>
 <Text id="151">To alter a filter, select it from the list, change any of the values that appear in the editing controls and click "Replace Filter" to commit the changes.</Text>
-<Text id="151a">Defining filters does not create sub-collections. Sub-collections are specified in the <AutoText key="glidict::CDM.SubcollectionManager.Subindex_Controls"/>, based on the filters you have just defined.</Text>
+<Text id="151a">Defining filters does not create sub-collections. Sub-collections are specified in the <AutoText key="glidict::CDM.SubcollectionManager.Subindex_Controls"/> tab, based on the filters you have just defined.</Text>
 </Section>
 <Section name="assignpartitions">