Adding a property to a Hyper.Net schema
Hyper.Net schemas have two purposes:
| |
· |
They define the fine-grained transformation settings used to create the Rich Hypertext rendition. Settings include heading-level detection, image management and processing, glossary management and hyperlink detection.
|
| |
· |
They define additional options used for all renditions, for example, PDF options (for the Acrobat Distiller) and metadata management options.
|
To map a property from the content type through to the publication, you need to add it to the Hyper.Net Topic content type in SharePoint, and then to the metadata management options in the Hyper.Net schema associated with the document type profile corresponding to your SharePoint content type. Here's how to add a metadata property to a schema:
| |
|
|
|
Step
|
|
1
|
Go to the Hyper.Net Administration Console and click on Schema Editor:
|
| |
|
|
2
|
The following screen will appear:
Let's assume the document type profile uses the Structured schema. If you click on the icon in the Action column, the context menu will appear. Here you can modify the schema or create a new one based on it. You need to decide whether you will use one schema for all document types, if each document type will have its own schema, or something in between. For illustrative purposes, select Modify this Schema.
|
|
3
|
The following dialog will appear:
Select MetaData Management from the navigation bar on the left, and then Filtered Values. A few example property mappings are already defined for you.
Hyper.Net allows you to define the following metadata types:
Default Values: Properties that may or may not exist on the content type and that do not exist on the document type profile, but which you wish to publish into the publication for use within your WCMS application. All documents saved into SharePoint that use a content type corresponding to a document type profile that uses a Hyper.Net schema with such a default value will have the specified values in their publications. These metadata definitions can be extremely useful for creating "global variables" you can use from your WCMS application that are based on the content type or document type profile being used for a document.
Filtered Values: Values mapped from properties on the SharePoint content type. The values are referred to as "filtered" because you have three possibilities during the transformation process:
| |
· |
You can pass the value from the content type through to the publication without modification.
|
| |
· |
You can change the data type to be more useful within the WCMS application.
|
| |
· |
You can change the output name to be more useful within the WCMS application. This option is especially useful for large document sets when properties were inconsistently named across content types and you would like to normalize all occurrences of the property to a single name in all publications to make creating the WCMS application easier. The Filtered Values function thus allows you to avoid resetting properties across the document set and also to avoid having to handle exceptions in the WCMS application. For any given schema, you may have multiple filtered values with different input names and the same output name.
|
| |
|
|
Note
|
If you do not define a given document metadata in the Filtered Values list in the schema, any existing value for it on the content type profile will not be populated into the resulting publication.
If a document metadata has been set up as a Filtered Value and a Default Value has been defined for it as well, the Default Value will be used whenever the metadata is not found on the content type profile in SharePoint. In this way you can ensure there is always a value for a specific metadata in the publication that is usable in your WCMS application.
|
Mapped Values: Mapped Values are used only during the creation of the Rich Hypertext rendition within the publication. This function allows you to extract information from the source document within the topic currently being processed and publish this information into a property in the publication. Options for detecting the information to extract include the use of matchers that allow you to search for styles, formatting, text patterns, Word fields and Word properties.
|
| |
|
|
Note
|
Hyper.Net automatically maps publication metadata into every publication, regardless of whether the value for each property is obtained from the document type profile or the content type profile in SharePoint. You do not need to add it to the Filtered Values in the corresponding Hyper.Net schema.
|