Open Text Corporation, the provider of enterprise content management (ECM) software, today announced that it has expanded its solutions in the global legal market including introducing key integrations between Open Text Document Management, eDOCS Edition (eDOCS DM) and Open Text Social Workplace available this fall. First released in the summer of 2009, Open Text Social Workplace supports a team’s ability to form, organize and collaborate on projects. Built to be flexibly deployed either standalone or as part of another solution, Open Text Social Workplace will integrate with Open Text eDOCS allowing users from within law firms to collaborate on documents and matters stored and governed within eDOCS. This includes new microblogging and instant messaging features and respects current permissions and governance rules. Open Text Document Management, eDOCS Edition helps eliminate inefficiencies caused by an inability to manage documents as well as the “islands of information” prevalent in many organizations. It helps control document-based knowledge assets by enabling users to capture, organize, locate and share business content in an integrated environment. With the release of eDOCS DM 5.3, full Windows 7 and Microsoft® Office® 2010 support and updated integrations are available. Also added in this release is new platform support for 32 and 64 Bit versions of Windows Server 2008,SQL Server 2008, and Windows Communication Foundation (WCF) support, while deployment costs are lowered through native Microsoft Windows Installer (MSI) support. eDOCS DM customers can now use the Open Text flagship records management offering with native integration, search and access from within the native eDOCS DM user interface. Records management of physical items, electronic records and email, as well as structured data from systems such as Microsoft SharePoint® 2010 and SAP are all available in this release. Support for Apple iPad is now available for WirelessDMS for eDOCS allowing users to access content from within eDOCS DM using the iPad device. http://www.opentext.com/
Category: Content management & strategy (Page 132 of 486)
This category includes editorial and news blog posts related to content management and content strategy. For older, long form reports, papers, and research on these topics see our Resources page.
Content management is a broad topic that refers to the management of unstructured or semi-structured content as a standalone system or a component of another system. Varieties of content management systems (CMS) include: web content management (WCM), enterprise content management (ECM), component content management (CCM), and digital asset management (DAM) systems. Content management systems are also now widely marketed as Digital Experience Management (DEM or DXM, DXP), and Customer Experience Management (CEM or CXM) systems or platforms, and may include additional marketing technology functions.
Content strategy topics include information architecture, content and information models, content globalization, and localization.
For some historical perspective see:
https://gilbane.com/gilbane-report-vol-8-num-8-what-is-content-management/
DotNetNuke Corp.,the Web Content Management Platform company, announced the release of the DotNetNuke Enterprise Edition. The Enterprise Edition includes the new DotNetNuke Content Staging feature that allows users to edit and approve content on a staging server prior to pushing the site to production. In addition, the DotNetNuke Web CMS includes a Content Localization feature that enables management of multi-language web sites. The Content Localization feature is included in all Editions of the platform including the Enterprise, Professional and Community Editions. Exclusive to the Enterprise Edition, Content Staging allows users to create a separate staging server where all intended production web site changes can be implemented and tested before being published publicly. It has features for organizations with many content contributors and tight restrictions on web site content publishing and review. The system will compare the staging server configuration to the production server and identify missing components and provides a detailed view of all planned changes. Other features include: An audit tool that creates a record of all publishing events; A “white list” in which users can define which modules should push both their settings and content during publishing and which should push only the module settings; A secure publishing function which allows users to easily push their site from staging to production. All Editions of DotNetNuke including the Enterprise, Professional and Community Editions, now feature a new Content Localization capability that helps users manage translated versions of their web pages. This feature includes management and configuration-mapping tools to keep translated pages synchronized across a web site. With the introduction of the Enterprise Edition, DotNetNuke will no longer offer the Elite Edition, which will now comprise the Professional Edition plus Elite Support. The new Elite Support option – available for the Professional and Enterprise Editions – features extended support hours, faster guaranteed support, priority management of support tickets, installation upgrade assistance, and source code access to the proprietary Professional or Enterprise Edition modules. http://www.dotnetnuke.com
IBM announced the acquisition of Datacap Inc., a privately-held company based in Tarrytown, NY. Datacap is a provider of software that enables organizations to transform the way they capture, manage and automate the flow of business information to improve business processes, reduce paper costs or manual errors and meet compliance mandates. Financial terms were not disclosed. The acquisition strengthens IBM’s ability to help organizations digitize, manage and automate their information assets, particularly in paper-intensive industries such as healthcare, insurance, government and finance. Additionally, regulations such as HIPAA and Sarbanes-Oxley have demanded new standards and now legislation is encouraging the adoption of new records management solutions, including scanning and capture to increase accuracy, lower costs and speed business processes to meet these regulations. http://ibm.com http://www.datacap.com/
Yesterday, it was announced that another CMS poster child of the late 90’s is to be acquired as Adobe Systems Incorporated and Day Software Holding AG announced the two companies have entered into a definitive agreement for Adobe to acquire all of the publicly held registered shares of Day Software in a transaction worth approximates US$240 million.
This follows Adobe’s acquisition of Omniture late last year and clearly demonstrates their intent in entering the web experience management (WEM) market place that we cover with interest here at Gilbane – as we anticipate they bring together the audience insight gained through the web analytics of Omniture and Day’s CRX content platform.
This will presumably add momentum to Day’s own move into the WEM space with their recent product marketing strategy, as they have reinvented themselves to be closer to the marketer with recent attention paid to functionality such as personalization, analytics, variant testing and messaging around using their repository for marketing campaigns and asset management. We await with interest firm integration plans.
In addition Day are a longtime advocate of CMS repository standards (JCR and CMIS), something that is also close to our heart at Gilbane. This announcement has also sent tremors through the Open Source community, as they wonder about Adobe’s commitment to the Apache projects like Sling and Jackrabbit that Day have been so supportive of.
Whilst Adobe and Day have been very quick to state that they will maintain Day’s commitment to these community projects, it’s hard not think that this commitment inside Day is cultural and we wonder whether this can realistically be maintained as the acquisition matures and Day is brought into the fold.
The acquisition also raises questions about what this means for Alfresco’s two year relationship with Adobe that runs pretty deep with OEM integration to Adobe LiveCycle – and Erik Larson (Senior Director of Product Management at Adobe) has publically stated the intention to integrate Day and LifeCycle to create a ‘full suite of enterprise technologies’. It will be important for the Adobe customers that have adopted the Alfresco based integration, to understand how this will affect them going forward.
One other area that I am sure my colleagues here at Gilbane in the Publishing Technologies practice will be watching with interest is the impact this will have on Adobe’s digital publishing offering.
As we’ve seen with previous acquisitions, it’s best to be cautious over what the future might hold. From a WEM product strategy perspective bringing Ominture and Day together makes a great deal of sense to us. The commitment to standards and open source projects is probably safe for now, it has been a part of the Day identity and value proposition for as long as I can remember and one of the most exciting things could be what this acquisition means for digital publishing.
Let’s wait and see…
Suggested further reading:
- Adobe Press Release
- Day Software FAQ
- CMSWire – Perspectives: What the Adobe + Day Software Deal Means
- Real Story Group – Adobe To Acquire Day – First Take ECM Perspective
- Adobe Buys ECM Vendor (and Apache Contributor) Day Software
Adobe Systems Incorporated and Day Software Holding AG announced the two companies have entered into a definitive agreement for Adobe to launch a public tender offer to acquire all of the publicly held registered shares of Day Software, for about $240 million. Adobe’s acquisition of Day will strengthen the company’s enterprise software solutions with Web Content Management (WCM), Digital Asset Management and Social Collaboration offerings. Day’s lweb solutions combined with Adobe’s existing enterprise portfolio will enable customers to better integrate their global web presence and business applications, unlocking value across their marketing, sales and service processes. In addition, Day customers will be able to leverage more interactive application and document capabilities from Adobe AIR, Adobe Flash, Flex, Adobe LiveCycle and PDF. http://www.adobe.com/ http://www.day.com
memoQ 4.2, by Kilgray, was integrated into XTRF 2.0, the management system for translation companies and corporate translation departments. XTRF supports the work of translation departments in three fields: management and administration of all company activities, management of workflow and of the production process, as well as management of the translation process. The integration of memoQ enables managing complete translation projects including from the very beginning until the translation is finished. http://www.xtrf.eu/ http://www.kilgray.com
TransPerfect, a large privately held language services and software provider, announced that it has completed a merger with AD-COM, a Montreal-based provider of technical translation services. The transaction expands TransPerfect’s presence in Canada, adding a Montreal production hub to the company’s three existing Canadian locations. AD-COM will become a division of TransPerfect and will continue to be led by Founder and President Claudia Cieri, who will join the TransPerfect senior management team. Cieri is a 20-year veteran of the translation and localization industry. http://www.transperfect.com/ http://www.ad-com.ca/
Recently I wrote an article for my blog – Taking the W out of CMS – exploring content management and content delivery as separate disciplines and this is a follow up to that article.
To summarize that article – firstly, to know me professionally, is to know that when it comes to the tribes of CMS folks, I am firmly in the WCM tepee.
Secondly, I disagreed the first time this discussion rolled around, as the millennium clicked over – we were all going to use portal platforms and content management functionality would be in our application server infrastructure (we don’t and it didn’t).
Thirdly, the difference between the systems we are building for tomorrow and then – our digital engagement activities were single threaded following a website groove and the end was very much the driver for the means.
For the mainstream CMS industry it was a web site centric world and in most projects and applications the term ‘CMS’ was interchangeable with ‘WCM’. Today we have a fragmented communication channel; it’s the age of the ‘splinternet’ (in this context, a term coined by Josh Bierhoff), delivering relevant content consistently to multiple places.
This not just devices – our websites are less the single and only web destination, folks consume information about our products and services from other web destinations like Facebook and Twitter (to name two). Plus, of course the needs of customer, consumer and citizen engagement means that we can chuck in multiple touch points, in e-mail, call centres and real life.
We used to get ourselves worked up about ‘baking’ or ‘frying’ content management/delivery applications, about decoupled systems that produce pages and dynamic content – but (as I said in response to a comment on my original blog post) today’s consumer wants super dynamic content fresh caught that day, prepared their way, hot off the griddle – Teppanyaki served to share – family style.
So, we have a new level of complexity and requirements for our systems to support our digital marketers and communicators. A level of complexity of requirements that sits between our content repository and our consumer, which used to be the section of the RFP that simply said “must produce compliant HTML”.
When talking about delivery of content, this is typically where our requirement starts to gain some uniqueness between projects.
The question is, so you have your well-ordered, neatly filed, approved content – but what are you going to use it for?
A requirement for an approval process supported by workflow is fairly ubiquitous – but if you are a membership organisation that engages its audience over email or a consumer packaged goods company with fifty products and a YouTube channel – your Engagement Tier requirements are going to be quite diverse.
This diversity in requirements means two things to me.
1. As an industry we are very good at understanding, defining and capturing CMS requirements – but how are we at identifying, understanding and communicating an organisations engagement needs?
2. If there are diverse requirements, then there are different solutions – and right now it’s is a blend of dynamic web content delivery, marketing automation, campaign management, email, web analytics (etc. etc.) – There is no silver vendor bullet – no leader, no wave, no magic quadrant – its different strokes for different folks.
It’s this that I want to explore, how do we define those needs and how do we compare tools?
So, into the Engagement Tier – my colleagues here at Gilbane challenged me to draw it. Hmm.. right now it’s a box of content, a big arrow and then the consumer.
I am going to need to work on that…
Subscribe to the Gilbane Advisor
