One of the major issues for authors with Documentum, Alfresco or Hadoop has always been checking in a document from a browser based interface. We have recently completed adding Office 365 integration to our High Performance Interface (HPI) to allow clients to checkin and checkout without requiring Office on their device. This post will share the approach as well as present a video of the capabilities.
Hadoop, a leading technology disruptor from the Big Data movement, is a massively scalable architecture capable of dealing with terabytes+ of unstructured data. As the cost of storage, memory and CPU continues to move toward almost free, we are seeing the clients looking to move away from traditional legacy ECM tools for the newer architecture and cost savings by managing their documents with Hadoop. On major advantage of Hadoop versus traditional vendors is the ability to add attributes “on the fly”. This post is will describe an ECM content model for Hadoop and walk through the process of add and remove attributes “on the fly” based on our experience from Hadoop ECM clients.
The Hadoop Distributed File System (HDFS) provides the ability to store an enormous quantity of files with redundancy. In our first release of OpenContent for Hadoop, we have included the ability to annotate PDF documents with OpenAnnotate and store and retrieve the PDF layers in Hadoop. This post will describe the integration with Hadoop as the ECM repository, as well as highlight some benefits of using an annotation tool that uses open specifications.
Many of our ECM clients often develop their own Web Services layer to isolate their applications from the back-end repository as well as provide a vehicle to add in their own services to talk to other non-ECM systems. OpenContent was developed as part of our Documentum practice to give clients a standard web services architecture with an open source approach. OpenContent is now available for the Hadoop NoSQL database, HBase. This post will detail the web services available in our first release with examples and explanations.
As we have discussed in our Hadoop Series, more and more companies are considering Hadoop for storage and management of documents and files. Just like our ECM clients, companies storing documents or scanned files in Hadoop want to provide PDF renditions of documents for easy viewing and other PDF capabilities. This post will discuss how Adlib can be leveraged with Solr/Lucene behind TSG’s OpenContent layer to provide robust ECM capabilities for your Hadoop repository.
In our series exploring the use of Hadoop for ECM, the best practice from our years of ECM experience tells us is that documents should be stored in both their native content as well as a PDF rendition of the content. Storing a PDF rendition allows consumers quick access to view the content, as well as being able to watermark and control the content to prevent consumers from altering the documents. This post will explore TSG’s partnership with Adlib and how we are using Adlib’s PDF conversion suite to transform documents being stored in Hadoop.
We had a good conversation yesterday with a long-time and innovative TSG client. The client has a mix of technical and business skills that make him a visionary in a highly regulated industry in regards to Enterprise Content Management. In addition to our normal catch-up discussions about plans for the year and what are we seeing other clients do, we also talked about Hadoop and how it could disrupt traditional Relational Databases (RDBMS). This post will present highlights of that discussion from a business perspective.
Open Source Hadoop becoming increasing popular for ECM customers
Chicago, IL. – February 4, 2015 – Technology Services Group, Inc. (TSG), an open-source enterprise content management (ECM) solution provider, today announced the creation of a new practice area specifically focused on Hadoop and related technologies.
The first step in supporting all of the TSG products on Hadoop is building our OpenContent REST Web Services layer to access Hadoop in the same manner we access Documentum, Alfresco and other content management systems. This post will present our plans and timelines for OpenContent along with associated TSG solutions.