This entry will discuss the nature of the changing market – with regards to BIG DATA and Unstructured Data. Of course, the rise of use or storage of semi and unstructured data is part of the lead in to big data. I will dive in to an executive overview of where I think the market is going this year, what I think you should know as an executive, and why you should focus your talent and efforts in these areas. The Data Vault model and methodology is clearly a solution, but only a part of the solution – as there is more, much more to it than just a data model!
How can I deal with Unstructured Data? How do I get that information in to my warehouse?
Then, once it’s in, how do I hook it together with the structured data? How do I deal with the data explosion?
Defining Unstructured or Semi-Structured Data
Well, in reality – one could argue that ALL data is structured – since it all reduces to ones and zeros, and from there, it is generally categorized as bytes, and from there, artifical or logical structures are placed on top of it. In reality, music (mp3 files, wav files, and others) all have a “specific structure” that they adhere to. So do pict, jpeg, mpeg, mp4, m4v, bmp and so on – as do doc, docx, xlsx, xls, and many other types. So is it really fair to call it “unstructured data”? Well, for the sake of discussion, I think YES.
Because the content that defines the context of the data is variable in both form and function. Like this blog post for example, the content are the words and sentences that I use – the context is defined by the entire post (the overall theme or major points I am attempting to put across).
When we compare this with structured data, we find that there are specific columns defined by metadata or logical names like customer account number – which are supposed to house specific content, and even further – sometimes defined by a format mask or even a boundary constraint. Structures and therefore structured data is usually much easier to understand, and therefore represent in a semi-static manner (meaning that the structure once defined, stays static for longer periods of time).
In the unstructured world, the content can shift every time an edit is made. In fact, the context can also shift – as can the visible structure of the document. In other words, I can change sentence order, headings, words, and even meaning of any document, email, or even music and images simply through editing them. Again, as opposed to customer account number – where I can change the content but the defined meaning is supposed to stay residual. However, I am not taking in to exception the notion of field or column overloading – which clearly changes the context of the field based on the content.
So what does this all add up to for me in business?
So if you’re an executive in business, you’re probably reading this declaration and thinking: gee, that’s a lot of technical jargon – what does it all mean? Or perhaps you understand what it all means, and you want to know how to solve the problems – so what exactly are the problems you are faced with when trying to make use of unstructured or semi-structured data?
- Establishing an understanding of context
- Tying multiple contexts together (those that are related are what’s truly important here)
- Enriching the related contexts with additional structured data sets (or the other way around)
Technically, what does this mean? What am I faced with?
Well, there are many technical challenges – some of the top challenges I’ve already named, but here’s a list none-the-less:
- Dealing with Exploding data sets – HUGE volume / explosive volume
- Moving the results of unstructured mining in to a structured world (perhaps)
- Capturing the full unstructured content – then relating it through use of XML databases, triple stores, or key-value stores
- Attaching the unstructured data sets to the structured data sets through dynamically allocated structures
All the while, ensuring your team remains agile, that your existing data integration (be it data warehouse, or ODS, or alternative store) remains consistent, and up to date. Making sure your business changes can and are reflected in the existing system in a timely manner. Keeping your systems running at peak performance so that all these data are usable by the business and so on.
So, What do I need to Know?
Well, the answers are simple – getting there is not so simple. But I will do my best this year to try to explain the proper steps to getting to a successful implementation in this effort – so stick with me, and if you disagree with something I’ve proposed, please comment and provide me with feedback.
Ok, first, as an executive, there are several terms and technologies you should familiarize yourself with:
- RDF, OWL, and Semantic Web
- Ontologies, Glossaries, and Business Terminology with Data Governance
- Data Vault Modeling, Data Vault Methodology
- Unstructured Data Mining
- XML data stores, triple stores, key-value stores, XPATH and XQUERY
- And finally: Context, and Content and Inference Engines
There are several other secrets from a technical standpoint that will make your world rock with success!
You see, I’ve been teaching big data and huge data warehousing for years. I’ve also been teaching big data systems performance and tuning for about the same – maybe 22 to 25 years or so. I’ve collected a lot of knowledge and seen a lot of things – both done right and done wrong. So from a technical standpoint I will tell you this:
- INVEST in new infrastructure components – more specifically: SSD or RAM drives for your critical or hot data assets
- INVEST in CPU or computational power – so you can either turn on compression or buy devices where compression is built in.
- INVEST in XML storage technologies and train your resources to deal with the technical components listed above! (get familiar with Protoge and XML data stores)
- INVEST in a good structured data set data architecture (yes, the Data Vault Model meets these needs)
Because these things solve performance problems with very big data sets. I’m talking about 47% to 70% to 700% performance improvements, I’m talking about reduction in storage necessities of over 70%, I’m talking about reduction in I/O requests, and reduction in bandwidth. But I’m also talking about hooking in business assets and business glossary metadata – applying context to the unstructured world.
How do I do this? (at an executive level)
Step 1: Establish control over your structured database world, integrate your disparate silos, leverage the power of the Data Vault Model & Methodology to boost IT agility
Step 2: Evaluate textual mining engines and their ability to provide context related answer sets spanning multiple languages – in preparation for next year!
Step 3: Invest in infrastructure as suggested above
Step 4: TRAIN your work-force on XML, RDF, OWL, Business Glossaries, Ontologies and Data Governance
Step 5: Institute some policies around the items in Step 4
Step 6: Hire a great consultant (as an adviser) who can help you select technology, and architect an unstructured data solution for you
Step 7: MOVE your unstructured data sets to XML if you can – convert them to OWL ontologies, and RDF data stores AND take the results of a data mining engine, and place them in a structured database following the Data Vault Modeling techniques
Step 8: Use inference engines across ontologies to link common terms together, establishing dynamic and ever-changing linking tables between the structured world and unstructured data sets
In other words, use a combination of physical Data Vault LINK tables (set with confidence and strength ratings for similarity matches), XPATH/XQUERY results against the raw documents, and standard SQL queries against the structured world to produce incredibly well associated and well defined results.
I BELEIVE THIS IS YOUR PATH TO SUCCESS with these technologies and of course, I can help you get there if you like. If you’d like to simply chat with me, pick up the phone and call me at 802-524-8566, I’d be happy to discuss these things with you.
What are the benefits of all of this?
Well, from an executive level you probably are feeling pressure to:
a) integrate your existing structured silo solutions
b) make the existing IT team more agile
c) begin incorporating unstructured data sets
d) establish a data governance program
e) establish data as an asset on the corporate books
f) find a way to integrate unstructured data sets
g) manage the ever-growing data explosion while still providing good response times
h) manage more and more XML data interchanges in business to business transactions
So the benefits are many, and of course all depend on how much effort you put in to following the instructions I laid out here. I hope to hear from you, either by phone, email, or comment on this blog entry – tell me what you see – or if I’m way off base! I’d like to know!
Hope this has been helpful,
PS: you can learn more about the Data Vault model and methodology at: http://LearnDataVault.com
Or call me at: 802-524-8566 (9am to 5pm Eastern Standard Time)