ODS and Inclusion Engine Integration
What is it?
The integration enables an open standards based metadata to be injected into ODS pages.
Why is it important?
The ODS Framework and ODS Application collect RDF data but they are not part form HTML code. Inclusion Engine enables agile management of open standards based metadata embedded in HTML docs as part of Search Engine Optimization (SEO) and related content discovery related activities.
How do I use it?
The injection can be enabled for every ODS Application by an instance creation or edit its properties:
The metadata injection is possible only for public instances. They collect data in the public RDF graph [Host]/dataspace used by Inclusion Engine to prepare injected metadata. The injection is only for URL which are URI of the ODS objects.
The injected data can be browse using Openlink Structured Data Sniffer (OSDS).
Wiki Post Metadata
Briefcase Instance Metadata
Calendar Instance Metadata
API Description
The following procedures are located in the sql/hosted_services.sql file of ODS Framework VAD:
| API Name | API Entry parameters | Description |
|---|---|---|
| ODS.DBA.incluson_engine_domain | in app varchar | Determine the instance ID based on URL or params. The 'app' parameter is a instance type name. |
| ODS.DBA.incluson_engine_is_possible | None | This procedure checks if the inclusion is possible. Returns true or false. |
| ODS.DBA.incluson_engine_post | in app_id integer | This procedure enables or disables the injection for the instance with ID = app_id |
| ODS.DBA.incluson_engine_path_escape | in path varchar | This procedure escapes the path. |
| ODS.DBA.incluson_engine_wiki | None | This procedure is a virtual dir post procedure special for ODS Wiki instances. |
| ODS.DBA.incluson_engine | in app varchar | This procedure is a virtual dir post procedure which prepare parameters for the metadata injection. The 'app' parameter is a instance type name. |
References