Scott Baker

Content Intelligence Developers - Getting Started

Blog Post created by Scott Baker on Nov 23, 2016

The first steps to building a custom plugin to extend Hitachi Content Intelligence.

 

Last week we launched Hitachi Content Intelligence (link to blog) as a new edition to our Hitachi Content Portfolio.  The attention from the launch has been outstanding - both internally and externally.  This is truly an exciting time for HDS and offers us new ways to engage and support our customers as they contend with copious amounts of "discontinuous data".

 

To begin, it's important to note that Content Intelligence includes a number of drag-and-drop user experiences.  Building connectors to different data sources, designing pipelines to process files, and even customizing how users interact with the results - all of these processes are interface driven.  But you are not limited to using our interfaces.  What happens when the data connector you need isn't available, or you want to process data in a way that is unique to your organization?  These questions are answered with the software developer's kit (SDK) that is included with  Content Intelligence.  Getting started with the software developers kit is straight forward - it includes the necessary programming libraries and interfaces you need to design your own custom experiences.  It even includes sample code to get you started.

 

In this blog series, I thought it would be worthwhile to include a video that walks through the initial setup of a development environment and creation of a sample project using the SDK.  This video is an initial recording of a larger set that will go into more detail regarding the development and testing of a fully functional plugin.  I recommend viewing it in full-screen mode to prevent eye-strain.

 

 

The extensibility of Content Intelligence essentially means that you can do almost anything you want with it.  The Plugin SDK allows you to build your own data source connectors and data processing stages used in building workflows.  The same SDK includes a test harness to support end-to-end development activities before moving the custom plugin into production.  Once you've completed the testing, the administrative interfaces of Content Intelligence are used to upload the resulting plugin bundle for inclusion in your Content Intelligence cluster.

 

In addition to the Plugin SDK, plans for Services and Application SDKs are in the works.  The Services SDK will allow you to build your own containerized services to support activities within your Content Intelligence cluster.  For example, you could create your own speech-to-text engine, virus scanner, entity extractor, database, etc. services that scale as your cluster does.  Similarly, if the you're looking to build your own end-user experience or integrate Content Intelligence into existing applications, the Application SDK will support you in this endeavor.

 

I've digressed just a bit at the end - it's just difficult to contain the excitement sometimes.  More to come on this.

 

Scott

Outcomes