OpenAsset was developed as a web based application that can integrate with complex IT systems such as a projects database or intranet portals. OpenAsset can be integrated and accessed via your SharePoint system.

This is a brief summary of what can be achieved by integrating OpenAsset into a SharePoint intranet portal.

Integration Features

Out of the box SharePoint provides some basic functionality, and with further development work it is a very extensible platform for building a wide variety of web based business applications. Some common integration points include:

  • Displaying OpenAsset within SharePoint using the SharePoint Page Viewer Web Part.

  • Using OpenAsset APIs to display images in SharePoint, as well as push project data from an external database into OpenAsset. 

  • Using SharePoint federated Search to pull search results into SharePoint

Web Part Integration

OpenAsset can be displayed in SharePoint using the SharePoint Page Viewer Web Part

RSS Feeds and APIs

Our APIs for pushing data into OpenAsset are accessed using SOAP Web Services, a standard pioneered by Microsoft. There are also URL APIs that enable you to link to content directly in OpenAsset, as well as embed content in Sharepoint. You can also use RSS feeds for displaying selections of images on SharePoint pages.

RSS Feeds 

Files can be displayed using RSS feeds. The 2 types of RSS feed available are for the files in an Album or a Search. The options for requesting additional data in the feed (e.g. available image sizes and dimensions) are the same for both Album and Search feeds.


Our APIs for pushing data into OpenAsset are REST. 

You can add search links as well as use OEmbed to display images. 

SharePoint Federated Search can pull results from OpenSearch 1.0/1.1 sources, and OpenSearch supports the RSS 2.0 format produced by OpenAsset.

Step 1 - Configure a Federated Search Location

  • Log in to SharePoint Central Administration site as an Administrator.

  • Click "Application Management" -> "Manage service applications"

  • Click "Search Service Application"

  • Click "Queries and Results" -> "Federated Locations"

  • Click "New Location"

  • Fill in the info for a new federated location and click "OK"

Location Name - OpenAsset
Display Name - OpenAsset
Description - OpenAsset
Location Type - OpenSearch 1.0/1.1

Query Template:{searchTerms}

"More Results" Link Template:{searchTerms}

 Specify Credentials - Anonymous: 

Federated Search Results Display Metadata: XSL - Might work in a basic way if you enter nothing, but alternatively a basic XSL example is given at the bottom.

Step 2 - Add Web Part to Search Results

  • Go to SharePoint Search Site and search for anything

  • On the results page click "Site Actions" then "Edit Page"

  • Click "Add a Web Part"

  • Select the Federated Results Web Part

  • Click the "Add"

  • Open the "Edit" menu for the Web Part just added and select "Edit Web Part"

  • Select "OpenAsset"

  • Click "OK" then "Stop Editing"

Example XSL

Here is an example piece of XSL that might work and could be modified. You will need to replace [YOUR_SERVER_NAME] with the name of your OpenAsset server.

<?xml version='1.0' encoding='iso-8859-1' ?>

<xsl:stylesheet version='1.0'




<xsl:template match='/rss/channel' priority='1'>

 <xsl:apply-templates select='item'/>



<xsl:template match='item' priority='1'>




 <xsl:attribute name='href'>

  <xsl:value-of select='link'/>


 <xsl:apply-templates select='openAsset:imageSizes/openAsset:imageSize[@postfix=""thumbnail""]'/>







<xsl:template match='openAsset:imageSize'>

 <img alt=''>

  <xsl:attribute name='src'>


   <xsl:value-of select='@httpFileRoot'/>

   <xsl:value-of select='@relativePath'/>








This should produce HTML of the form:

<a href="">

    <img alt="" src=""/>



<a href="">

    <img alt="" src=""/>



<a href="">

    <img alt="" src=""/>



Note: newer versions of SharePoint have some compatibility issues with XML, XLS and RSS-related webparts. Please check with our support team whether your planned integration will be supported.

Did this answer your question?