Configuring the example situation
To set up the structural decomposition of the Rich Hypertext rendition associated with this document, proceed as follows:
| |
|
|
|
Step
|
|
1
|
Go to the Hyper.Net Administration console and click on Schema Editor.
|
|
2
|
Click on the Action icon next to an existing schema and select Modify this Schema or create a new schema.
|
| |
|
|
3
|
Within the Schema Editor, click on Structural Manipulation in the left navigator, then on Table Of Contents as shown:
|
|
4
|
Enter a title to be used for the front matter topic for all Rich Hypertext renditions created with this schema. A few examples are: Publication information, About this Publication, About, Front Matter and Overview. The front matter topic will contain all material before the first level 1 section is found. This often includes the title page, acknowledgements, the table of contents and other preliminary information. The front matter topic is created in the online table of contents (pubTOC.xml) as the first level 1 topic in the publication. We'll enter the title Front Matter and click on Apply.
|
|
5
|
We now need to configure out structural levels. Click on Add Level. The following dialog appears:
|
|
6
|
If no levels previously existed for the schema, the information you enter now will be applied to the first structural level. Define the matchers you require to detect level 1 structural elements in the source document. In our example, we want to match the style Heading 1. Click on Add Style Matcher, enter the name of the style as shown and click on Apply.
| |
|
|
Note
|
Subtraction matchers are an advanced subject beyond the scope of this document. For information about subtraction matchers, refer to the Hyper.Net Support database at www.coextant.com.
|
|
| |
|
|
7
|
Your level 1 list should now be similar to the image below. To save this level, click on Apply as shown:
|
|
8
|
Returning to the Table of Contents window, we now need to define structural level 2. Click on Add Level.
|
|
9
|
The dialog allowing you to enter matchers for level 2 appears. First create a Style Matcher for Heading 2 exactly the same way you did for Heading 1. But this time, after you have clicked on Apply for the Style Matcher, you should now click on Add Formatting Matcher as shown:
|
| |
|
|
10
|
Configure the formatting matcher as follows (remember in our example the authors used Arial 20 Bold):
|
|
11
|
Click on Apply. Then at the level 2 matcher list click on Apply again. You will return to the Table Of Contents window.
|
|
12
|
Back at the Table of Contents window, click on Add Level to create level 3 matchers.
|
|
13
|
At the list of matchers for level 3, click on Add Formatting Matcher. Configure the formatting matcher as follows:
|
|
14
|
Click on Apply, then click on Apply again at the list of matchers for level 3. When you return to the Table of Contents window, it should look like this:
|
|
15
|
Briefly compare the specification you have created with the document's structural descriptor we created while analyzing the document's structure:
Level 1: Match style Heading 1
Level 2: Match style Heading 2, Match format Arial 20 Bold
Level 3: Match format Arial 16 Bold
If your specifications in the schema match the structural description of your source document properly, Hyper.Net will function properly and reproduce the table of contents for you in SharePoint.
|
|
16
|
Click on Save to update the specifications in your schema, and be sure that the schema is associated properly with the required document type profiles by editing the appropriate document type profiles using Hyper.Net's Document Type Profile Editor.
|
| |
|
|
Tip
|
There are many options for matching the structure of source documents. Refer to the online Hyper.Net Support Database at www.coextant.com to learn about other possibilities.
|