Fri, 25 March 2011
Alan said that every organisation he had worked with had their content (documents/records etc.) spread across numerous different repositories.
These repositories had typically grown up as the organisation had merged or acquired other organisations, and/or as they had added new systems for specific lines of business.
At the recent Info 360 trade show lots of people had come up to Alan to ask him what they could do about the problems caused by the multiple repository issue.
James said that the two obvious approaches were to either:
Alan was sceptical as to the feasibility of either approach.
Migrating all content into one repository was almost impossible because:
Running a federated search over each repository is no panacea either. Lets assume you have connected the search engine to the various different repositories. Your search engine now has the problem of understanding the way each repository keeps metadata. And even it managed to understand the metadata in each repository, it still has the challenge of normalising across the various repositories, so it could rank and present one set of coherent search results from them all. Alan thought you could make federated search work over three or four content repositories, but most of the organisations that he had advised had way more than four content repositories.
Near the end of the podcast we discussed the prospects for a challenger to SharePoint's market dominance emerging.
This podcast was recorded via Skype on 25 March 2011