The converted
Classification Set no longer separates each view into its own folder. Instead, a
document subset is created for each class and the old hierarchy is removed. In the old training hierarchy, if a separate folder for
each view and class per view is present, they are merged into a single document subset in the new document set format. Each
different view that has one or more training documents is converted into its own document subset with the same name. This means
that if your project has both content and layout classification and each of these classification types has training documents, a
document subset is created for each view when the project is converted.
The old training set for classification documents called
"Learn" lists different training folders based on view, class, and subclass. This hierarchy was needed in order to
keep things organized and class specific. After conversion, this hierarchy is no longer needed because the class or subclass is
encoded in the document itself. This is visible in the blue highlighted document and its class name.
The top-level view folders for
"Content,"
"Layout," and
"Text" are converted into document subsets with the same name in the
Classification Set. These subsets contain all of the documents that used to be separated by class or
subclass, and their class is now displayed as part of the document information.
Search results
Search tips
The search returns topics that contain terms you enter. If you type more than one term, an OR is assumed, which returns topics where any of the terms are found. Enclose your search terms in quotes for exact-phrase matching.
The search also uses fuzzy matching to account for partial words (such as install and installs). The results appear in order of relevance, based on how many search terms occur per topic. Exact matches are highlighted.
To refine the search, you can use the following operators:
Type + in front of words that must be included in the search or - in front of words to exclude. (Example: user +shortcut –group finds shortcut and user shortcut, but not group or user group.)
Use * as a wildcard for missing characters. The wildcard can be used anywhere in a search term. (Example: inst* finds installation and instructions.)
Type title: at the beginning of the search phrase to look only for topic titles. (Example: title:configuration finds the topic titled “Changing the software configuration.”)
For multi-term searches, you can specify a priority for terms in your search. Follow the term with ^ and a positive number that indicates the weight given that term. A higher number indicates more weight. (Example: shortcut^10 group gives shortcut 10 times the weight as group.)
To use fuzzy searching to account for misspellings, follow the term with ~ and a positive number for the number of corrections to be made. (Example: port~1 matches fort, post, or potr, and other instances where one correction leads to a match.)
Note that operators cannot be used as search terms: + - * : ~ ^ ' "