“Enterprise Search is Dead” – so said well-known commentator @JamesLappin when speaking at the ARMA / NAID / PRISM joint conference in London last week. No-one is buying it and no-one is really selling it, he went on, and I must admit the glister does appear to have gone from this particular technology trend. His point, and one I agree with, is that everyone thought we were going to get Google-style search and everyone was therefore disappointed when that didn’t happen – and it didn’t happen because optimising search for one type of system (albeit a big one), the Internet, is far more straightforward than searching multiple complex systems with different architectures, platforms, databases and security models.
But of course, the demise on one particular marketing tag doesn’t stop us all needing to be able to find stuff when we need it, get rid of it when it is no longer of any use, and produce it when we are asked (or forced) to. So how do we do that? Well, of course, we have to use metadata (often alongside searching the content) and so the challenge moving forward will remain as it was before Enterprise Search came along - extracting, storing and accessing metadata from a variety of repositories via a single interface or integration (say, Outlook?) to allow us to create, capture, store, manage, preserve and deliver our precious content. And then when we need it, for an auditor, regulator, legislator or litigator we can produce it without having to start a new project every time – document production is business-as-usual these days.
So what technology do we use to help us? Well that is the wrong question to ask first. What we need to do first is take a good, long hard look at our current information environment and the needs of our information workers and start looking at awareness, skill sets, organisational and operational accountability, the current information map, integrity, security and availability and then, perhaps, when we know where we are now and where we want to get to, we can have a look at the technology we might need to support our requirements, whatever the label on the tin. And what do we call that? We call it Information Governance – for now.