See the article Federated Search – Indexing Module for more information about this module.




Enable the Federatedsearchindexing module.



When clicking Save, a feed will be generated listing all changes to published-only content since last ping. Set limitToItemsNotOlderThan to a value matching (or slightly larger than) the federated search ping interval. Provide the generated url to the team responsible for your organization's Federated Search to ping MediaSpace periodically and keep their federated search index in sync. Click Regenerate to have a new feed created.




Enter a value in minutes. Limits items to return to only fresh ones, those whose lastUpdated datetime is newer or equals to now()-limitToItemsNotOlderThan. Minimum value enforced by module is 5. If you changed the value, you need to save the admin configuration and regenerate the sync feed after the save was successful.




Enter, or generate, an App Token (app-specific API key) to limit consumer calls to only those which use the right App Token.
This is considered a best-practice, as prevents handing the master admin API key to a BU's developers. If used, calls with a KS (Kaltura Session) not generated by this App Token will result in an error. Leave empty if planning to use a regular KS which has account-wide access.

Click "Generate" to conveniently (re)create a dedicated app token. Once created, provide both id and value to the Federated Search developers.






Click "Generate" to (re)create the indexing "seed", a feed which will include ALL published-only content currently in this MediaSpace. Provide the feed's URL to the Federated Search developers, to serve as the baseline set of data indexed. Developers can also use the seed to periodically clean up the index of content no longer published in MediaSpace.




Upload custom XSLT file. This will automatically regenerate both sync and seed feeds. Check default.xsl as an example of how to create your own.

In This Article
Was this article helpful?
Thank you for your feedback!