The Custom Metadata component of the data model enables mapping data fields, for example, invoice number or customer name, from your data model to the metadata fields defined in document profile rules configured on your Oracle WebCenter Content Server.
When you run the report and select an Oracle WebCenter Content server as the delivery destination, Oracle BI Publisher generates and stores the document on the content server with the metadata.
Certain requirements must be met to use this feature of the data model editor.
The content server must be configured as a delivery destination with custom metadata enabled.
To map the custom metadata fields to data fields from your data model data set, the data set must be of a type that the data model editor can retrieve the data structure, for example, SQL data sets and Excel data sets are supported; however, Web service data sets are not.
You can start metadata under a document profile.
To map custom metadata:
On the Custom Metadata header region, select the Rules as follows:
Server — Select the Web content server where the content profile is defined.
Content Profile — Select the content profile that includes the rules that define custom metadata fields.
Rules — Select the Rules set that specifies the metadata fields.
If you do not select a Rules set, then BI Publisher loads the metadata for all Rules under the Content Profile.
If a metadata field is required a Y is displayed in the Required column.
BI Publisher loads all the metadata fields defined for the Rules set that you select. You can delete unneeded custom metadata fields.