MySource Matrix Evaluations

Main Content

MySource Matrix provides a number of tools to allow you to integrate with other systems for the import and export of content, the use of which depends on what is trying to be achieved.

The strategies for integrating systems to import content are (in order of increasing complexity):

  • MySource Matrix also provides the DB Data Source to allow you to connect to a local or an external database and execute a query. The results of the query will be displayed as shadow assets in the asset map. The DB data source asset also contains a GUI interface to build simple queries.
  • RSS Data Source - MySource Matrix provides a data source asset to read RSS feeds and display the entries from the feed as shadow assets in the asset map. When used with the Asset Listing, you can redisplay RSS feeds from other sites inside your MySource Matrix system.
  • The Remote Content asset – this page template allows you to embed the contents of an external web site within the design of your own site. You can even define the start and end tags to specify content on the remote page will be discarded until this tag is reached. This allows you to strip off the design component of the remote page, to simplify its look when nested in your site.

In addition, MySource Matrix provides the following tools for exporting content:

  • RSS Publishing - MySource Matrix fully supports the creation of RSS with the RSS Feed asset. This asset generates outbound RSS Feeds without the need for formatting, and takes care of sending the correct headers and suppressing the site design. The RSS Feed asset currently supports RSS 1.0 (RDF), RSS 2.0 and Atom 1.0.
  • Some assets allow XML or CSV export of content, for example form submissions may be exported in XML or CSV format.

If you find that these tools do not suit your needs, the following can be developed request:

  • a Custom asset – this involves building an asset to interface to a specific system that is proprietary to a particular client.
  • an Asset Bridge – this involves building an asset to interface to a system that is not proprietary to a particular client. An example is the LDAP Bridge asset.

.