One of the final sessions at Gilbane SF yesterday was around content standards: CMIS, JSR-170 and JSR-283.
Many realize there are several challenges with CMIS in particular and efficiently working with content from disparate content repositories in general.
The session aimed at shedding light on some of these challenges and possible solutions in the standards space.
Too Much Content in Too Many Content Repositories
Chances are, if you’re in the enterprise content management space and you have an ECM system, this still doesn’t solve all your ECM problems. There are also document management and digital asset management systems, for example, you need to be able to “talk to.” Users of one ECM system often need to access and store documents in an entirely different content repository.
Scattered data repositories only add to the challenge. The majority of companies have an assortment of repositories, be it ERP, PLM, PDM, BI, KM, WCM, or DM systems. The problems we run into with multiple repositories are compliance, eDiscovery and business intelligence.
Add to that the fact that 80% of data is unstructured, and the enterprise world looks very gloom. Search gets harder as data sets grow. It takes longer to index. Thus, it takes longer to search.
ECM: CMIS or JSR-170/283?
Naresh Devnani, managing director at Lean Management Group, gave us a peek into real-life scenarios and impressions of implementing a standard’s wrapper, from the times when he was working for Vignette PS.
Devnani talked about implementing a JSR- 170 (the standard that was led by Day Software) level 1 functionality for an RDBMS-based web content management system.
Speaking of lessons learned, Devnani mentioned:
- Lack of ease in implementing a contained 1-n parent-child relationship
- Inefficient reference model in certain cases
- Node types not useful for WCM object wrapper
- No multidimensional view of repositories
- Big ramp-up
One of the examples at the session was quite shocking, actually. According to Devnani, some customers think of interoperability in terms of a content migration and moving things around from one repository to another. But there are still high hopes for CMIS.
Full story on CMSWire: Gilbane SF: Content Integration Standards — CMIS, JSR-170, JSR-283