In the News | 2008
| Bookmark and Share |
|
|
|
Delicious |
|
Technorati |
|
|
Slashdot |
|
|
|
|
Yahoo Buzz | ||
June 27, 2008
DM Direct
Trends in Content Integration: From a Hub-and-Spoke Model to Content Mashup Model
This approach delivers the benefits of centralization without its limitations. Because content remains in its original repositories, no single system or server will create bottlenecks. Meanwhile, multiple standards and ECM systems are accommodated so the enterprise will not be tied to any one platform and new repositories and systems can easily be added. Content mashups can also work well with standards other than Java, so C++ and .NET applications will be supported. Their flexibility allows companies to quickly deploy new applications and support the broad variety of devices and networks that are standard for today’s mobile users.
Taking Stock
Content mashups are still an emerging technology, and enterprises have only just begun to adopt them. But given their strengths, they are likely to play an increasingly important role in content integration initiatives going forward. Can you start adopting content mashups for your enterprise? The first step is to take an inventory of your content assets, which includes asking:
- How many repositories are within your enterprise?
- What technologies are repositories are running on?
- What ECMs or other content management systems are already in place?
- Which repositories need to be accessed across the enterprise?
- Do you have an ongoing need for all repositories or if some can some be retired?
For companies with a relatively small number of repositories and fairly consistent types of content, consolidating them onto a single ECM system may still be a viable option. However, it’s important to consider future needs as well. If future acquisitions or a geographic expansion is planned, consolidation may not be the right solution.
Most large or rapidly growing companies will find they need more flexibility. In some limited instances, a hub-and-spoke model could be sufficient. An example, might be companies that have a relatively small pool of Java-based assets. Overall, the content mashup approach is currently the best way to accommodate the diverse assets and technologies seen in the contemporary enterprise.
The added flexibility of content mashups will allow organizations to use and reuse content across boundaries, increase the efficiency of their information workers and IT staff and remain nimble enough to adopt new repositories and technologies. Adopting a comprehensive yet highly adaptable content integration strategy has become a critical business imperative.
References
1. John F. Gantz. “The Diverse and Exploding Universe.” IDC, 2008.
2. Doug Henschen. “In Focus: Oracle the Content Integration Fray.” Intelligent Enterprise, 2005.
3. Marydee Ojala.“Searching for Efficiency.” EContent Magazine, 2007.