Using IDOL for Content Enrichment during content migration.

Phil Cox

The purpose of this article is to show and share knowledge on how easy it is to use IDOL to "look" inside any type of content then in this case use that to correct the description of that content in it's target destination. In our example we will take content from Extended ECM and put that content into Core Content.

Looking at our source documents in our HR Directory with Extended ECM, everything looks fine. However one of these documents has been incorrectly named with an incorrect HR Number as part of it's metadata. IDOL will help us to discover this error and make any corrections before we transfer our content to our target, in this example to Core Content.

The first step is to bring the files locally and add the required metadata into a small DB.

We can see below the table and we added the original NodeID so this could be referenced from the new target system.

Now comes IDOL which will use Eduction to find any occurrence of HR-XX in these documents. Once found new Entities will be added to the FlowFile and we will extract those values and put them into a different table in the same database.

We can see that the Employee Code of Conduct file which is called HR-34 Policy - Employee Code of Conduct is incorrectly named as INSIDE the document it's described as HR-29. Now we have the chance to amend the file name to the correct one which will be HR-29 - Policy Employee Code of Conduct and send to our target of Core Content.

Our IDOL Flow looks like the following..

Here we make the corrections and save before running our upload into Core Content.

Here is the result and we see that in fact the HR-34 was incorrectly named and now we have correctly named and applied the correct metadata.

I hope this serves as an introduction into just some of the capabilities of IDOL.

#GoBeyond Always Be Learning

Phil ****