I’ve recently set up my home office and it was quite an experience. There were quite a few checklists on the web but they were really not suitable for Indian conditions (are we the only ones who use a UPS? ). So here’s what worked for me. Your mileage may be different.

1. Laptop and/or desktop: I use two – a Mac and a PC. What are the challenges I faced in migrating from a PC to Mac and why do i still use both is a topic of another post. I bought my Mac from Unicorn in Malviya Nagar. They gave me a good price.
2. A printer: There are quite a few out there. I do a lot of research and print quite a bit. I also do a lot of scanning for expense proofs and so on. So I bought a slightly bigger printer – HP Officejet 8500. It’s an all in one MFD. Although I’m not very happy with the performance but i think that’s probably only my piece. It’s also got Ethernet connectivity and so I don’t need to keep my laptop connected to it. I can even print photographs directly from my mobile phone.   This model also has a wireless variation but I didn’t go for that because I figured that unlike my laptop, i’m not going to carry around the printer. I bought it from Nehru Place, which btw is an amazing place for such gadgets.
3. An Internet connection with unlimited bandwidth and reasonably high speed connection. The maximum speed for a reasonable price I got in Noida was from Airtel.  BSNL is just too much of a pain to get. Again, the connection quality is not too good (skype calls drop, downloads break) but their service is good and I don’t have another option.
4. A backup internet connection. I’ve been struggling with this but haven’t found anything good yet. I have experimented with mobile broadband cards (Tata photon plus as well as BSNL EVDO). Both of them suck big time and i’ve heard Reliance is not too different. But frankly I haven’t tried that yet and they are not ready to give me a demo at my place. I also took MTNL 3g but that doesn’t work at many places even in Delhi plus recharge coupons for 3g are not available yet. I am not sure what’s up with our 3g policy – private operators are not allowed to offer 3g and public sector operators have no clue in life. So for now,  i’m still experimenting.
5. Data plan for checking emails or surfing on mobile. You need blackberry services or a GPRS data plan which most operators provide. I use Vodafone (have also experimented with MTNL 3g as mentioned above).
6. Telephone connection (mobile as well as landline). I use airtel for my land line. For mobile connections, there are just too many options and frankly speaking there’s not much of a difference. I use airtel for my personal mobile and vodafone for my official mobile. I got vodafone primarily because of a good deal i got for an unlimited data plan.
7. If you have to interact with folks abroad, you need a less expensive way of calling. I use skype as well as Vodafone calling cards. The quality of audio is usually much better with Skype  but as i mentioned above, the connection drops occasionally and so I generally prefer phone calls over skype calls. Most other operators provide these phone cards as well.
8. A good noise canceling headset
9. Phones – both land line as well as a mobile phone. There are quite a few options there, especially for mobiles – from blackberry to iphone to cheap chinese imitations. I use a Nokia E71 and a micromax dual SIM phone. My Nokia has a SIP phone built in and so i can make skype calls using that but I think that’s only for academic satisfaction though as the quality is not too good. You can also buy one of those skype phones (some of which can also double up as land line phones) from Nehru Place.
10. A Wireless router (or modem). I have an old netgear but i’m quite happy with it. I can connect my two laptops, printer as well as mobile phone
11. Office furniture. If you’re going to spend a reasonable amount of time working, this is probably the most important aspect for your office. I bought a large L-shaped table and a chair from Home Town in Noida. I was very particular about the chair because I wanted something comfortable enough to discourage me from working on my bean bag.
12. Stationery (printer paper, staplers, pen, file boxes, ……)
13. An uninterrupted power supply (UPS). Although, my apartment complex has a generator backup but when power goes off, it always takes about 30 seconds for the generator to take over.  You need a UPS so that at least the modem and routers don’t restart in the event of power shutdown.
14. An external drive to keep your backups. I bought a seagate 1 TB drive (again from Nehru place). I’m also experimenting with online backup and sync services (like dropbox, microsoft live and some others).
15. A warranty and service plan for all the stuff above – laptop, desktop, printer etc. Don’t underestimate the importance of this and try to get something that covers onsite visits as well.
16. A coffee/tea maker, AC, heater etc but I guess if you need these you probably already have them.
17. Lots of different cables!. But don’t worry about it too much as every device you buy will come with required cables.
18. Next on my list is an external monitor and keyboard. I haven’t bought these yet but since I spend a lot of time on my Mac, I think these will improve my productivity.
19. I also moved my treadmill to my office in the hope that i’d use it more often for the purpose it was bought for!

Okay so this should be a good start. I will add to it as and when I remember more. If you think i’ve missed out something, please leave a comment and i’ll add that to the list.

Happy New Year everyone. Here’s wishing you a great twenty-ten.

I have renamed this blog to just “Random Thoughts”. Of course, i’d still be writing about Content Technologies but on the CMS Watch blog now.

In fact, I’ve been enjoying my work at CMS Watch, where I cover Portals, Enterprise Content Management and Web Content Management marketplaces. I haven’t been able to post to this blog for a while but I’ve written a few on the CMS Watch blog:

• A Tale of Two Portals – Part 2
• Do you really need in-context content editing?
• What to make of the next big release of TeamSite?
• SharePoint — What’s Ahead?

An important component of our research is based on feedback from actual users of technologies we cover. So i’m always interested in hearing your experiences (both good and bad). If you would like to share something, please leave a comment here or send me an email at adurga (at) cmswatch (dot) com.

I will hopefully be writing more often from now on on this blog as well as CMS Watch.

Well, like all good things, my vacation is over. However, for a change, I am actually looking forward to next week - I am joining CMS Watch and would be starting work on Monday, October 12th.

I have been a fan of CMS Watch since its inception and owe much of my current thinking & knowledge to CMS Watch. So it’s been like a ”dream come true” for me

I have blogged occassionaly at the CMS Watch blog before but would be doing it more frequently now. So what happens to this blog? Frankly, I don’t know. Hopefully, I will be able to keep it alive  and make it a more general technology blog.

Wish me luck!

Today was my last day in Wipro.

I’ve had pretty good time working with a great group (Portals and Content Management or the PCM practice)  - got opportunities to play multiple roles, worked with some cool people, made many good friends, worked with great managers and learned a lot in the process.

However, it was time to explore something different – explore new worlds; to seek out new life and new civilizations (thanks Munish and Star Trek for that).

I am grateful to everyone who I worked with at Wipro and wish everyone all the best.

So what’s next? Well that’s the Real Story that I will post in my next blog as soon as I get some time. For now, I am looking forward to a vacation in Nainital, a nice little hill station near Delhi. I don’t recall if i’ve taken a vacation before when I did not have to check office email .

Whether one is implementing a new system or moving from one system to another, content migration is always an important aspect. Each situation is unique and so each migration scenario will have its own roadmap. However, there are some common factors that are present in each migration and can determine how long will the migration last. I’m listing down a few. If you think there are other factors as well, please feel free to comment.

In order to take stock of these factors, one needs to follow a good migration approach and spend decent amount of time in analysis. I will not go into details of such an approach - There are quite a number of good articles on these approaches and in particular I like this one by James Robertson. This post is also not about the importance of content analysis, governance and other best practices 

So here are some factors. At this point in time, these are only high level thoughts and I will probably expand these as and when I get time. So Feedback most welcome.

Source(s) of Content

Where and how the original content lives is probably the most important factor defining migration. It could be in a flat file system, database, another content management system, another application or somewhere else. It is important to understand whether it is stored in a proprietary format or not and how easy is it to access it. Obviously content stored in a table in a relational database is easier  to access as compared to something that is stored in a proprietary format.

Type of Content

Content Type could be Media (Images, Video, Audio), Documents (DOC, XLS, PDFs), text (html, xml), database or something else. Migration time lines are hugely dependent on this – migrating X-RAY images where each file could be couple of MBs or more has different challenges than migrating small text files. And when done across multiple environments, the effort only multiplies.

Closely related to this is what the content actually contains? So for example, do you need to migrate multiple languages, encodings and charactersets?

Quality of content

Pranshu gave me this example on twitter the other day. He was involved in a migration scenario in which the headlines of news articles were actually images. So even though migration of body and other fields could be automated, there was a good amount of manual intervention required to convert image headlines to text headlines for destination. Some other examples could be:

• do all html files follow a template?
• content with inconsistent metadata (like Male/Female Vs M/F)
• content with missing metadata that could be mandatory on destination system
• How much of the content is still relevant?

Amount of Content

Amount as well as the size of files is very relevant. In case of document scenarios, it is important because huge files take time to move across and in case of web content scenarios, it is important especially when things need manual intervention.

Destination System

Is the target system a content management system or is it something else? Does it support the fields that you require or do you need workarounds? Does it provide some mechanism to ingest content? Does it support your metadata and permissioning requirements?

Transformation or Value Add required

In my opinion, this is the factor that is probably the most important. The amount of transformation required between source and destination can actually define how much automation is possible and how much manual intervention is required. If you were to do an “as is” migration, things would possibly be trivial. So for example:

• Title field in Source needs to be mapped to headline field in destination
• Do all source fields need to be migrated?
• Is there a need to define additional fields?
• Is there a need to transform fields based on constraints (for example an ID in the source CMS would be stored as “123-45-6789” where as in the new CMS, “-” would not be permitted and it needs to be stored as “123.45.6789”)
• Data cleansing
• Do you need other value adds (like SEO, copyrighting and so on)?
• Do you need to repurpose the same content for say delivery to mobile devices?
• Are there links between files that need to be preserved? (like an XLS embedded within a Doc)
• Do you want to migrate only the latest version or all versions? what happens to content that is part of an incomplete workflow?

Users and Roles

The difference in how users, roles and the whole permissioning system works in source as compared to destination also plays an important role. This is dependent on capabilities of the system as well as how comprehensively your organization has defined these. In some cases, just like data mapping, you might also need to map these for permissions etc. Read permission in source could be mapped to view permission in Destination. There would also be cases when there is no one to one mapping of permissions between source and destination.

Amount of automation possible

Based on some of the above factors, you will have an idea of how much of the migration can be automated. The extent of automation is dependent on source as well as destination systems:

• Does source allow export of content?
• Does destination allow import of content?
• Are 3rd party products for analysis and migration being used?
• Do these products allow ETL kind of activities?
• etc

Roll out

How you want to roll out the new system also impacts your time lines. In scenarios where there are multiple geographies or multiple business units involved, it could be tricky. The reasons for these are more organizational and less related to technology. So whether you do a big bang roll out or do a phased roll out impacts the migration process.

Parallel Run

This is in some way related to the point above. Will Source and Destination systems be required to run in parallel? If yes, content will have to reside possible at both places and if users continue to modify content during the migration, you have to consider doing multiple iterations.

Infrastructure and Connectivity

The speed at which content can be moved across, exported, imported or ingested is also dependent on the connectivity between source, destination, databases etc.

So do you have similar experiences? Are there any other factors that can impact migration time lines?

(Thanks to @pranshuj, @rikang and @lokeshpant for inputs)

Forrester recently named Fatwire a Leader in their WCM for external Sites Quadrant. And the folks at Fatwire have already called two of their fellow-quads (for the lack of a better term), Interwoven and Vignette as legacy WCM products! Incidentally, Interwoven sits nicely in the Leader quadrant in the same report and was also named the fastest growing ecm vendor by rival analyst firm Gartner. (Yeah, yeah I know -  the report by Forrester is on WCM and the other one by Gartner is on ECM).

On a more serious note though, Fatwire has been making some news in recent times. Among other things, recently they announced a rescue program for “legacy” Interwoven and Vignette customers – an offer to move to Fatwire at no license cost (only the support costs). They have announced this offering in partnership with Vamosa and Kapow. Vamosa and Kapow both have content migration offerings and compete in this space. Fatwire says they both add value to this proposition. I suspect they have partnered with both because Vamosa, along with expertise in many aspects of content migration, has connectors for Interwoven and Vignette while Kapow has connectors for Fatwire. Any content migration scenario will require both set of connectors – one set that exports from interwoven or vignette and one set that imports into Fatwire. You could obviously roll up your own migration scripts by publishing from Interwoven/Vignette as XML and then using Fatwire’s XMLPost or BulkLoader to import into Fatwire. But then the offer for free licenses wouldn’t be free or would it?

BTW, even though Fatwire’s release mentions these as partners, neither of these two have issued their press release nor have mentioned it on their respective sites. I think that’s natural because they probably have partnerships with those “legacy” vendors

This is an interesting and I’d say an aggressive move by Fatwire. After all there are only few niche WCM vendors remaining and they are one of them. There is a clear divergence happening in the marketplace - On the one hand, there are more web oriented scenarios (Web Content Management, Site Management, Portals, Web Sites and so on) and on the other hand are more repository/management oriented scenarios (Document Management, Records Management). The requirements, challenges as well as decision makers (and stake holders) for both these areas are usually different. Fatwire for one has been focusing on and targeting the needs of interactive marketers which usually fall under the former category of web oriented scenarios (or Web Experience Management, as they like to call it). While many other products have been diversifying horizontally. Call it vertical Vs horizontal diversification if you will.

If there was any time to go aggressive, this was possibly it when the two other big ones have been acquired. Interwoven and Vignette, though can by no means be called ”Legacy”, even though they have been acquired. There are probably a few customers out there who are not convinced about Interwoven’s and Vignette’s future after their acquisition by Autonomy and OpenText respectively. But then, as Forrester’s Tim Walters says on his blog, there are many customers out there, including Fatwire customers who are unhappy with their current implementation. So nothing stops the other vendors to come out with this kind of offer for existing Fatwire customers. In fact, as Tony Byrne says, there’s nothing new in these kind of Competitive upgrades.

If you indeed take up this offer, remember that even though there is no license cost, there are quite a few other costs apart from the support costs that you would have paid to Vignette or Interwoven. Here’s Irina’s post on real costs of implementation.

For one, you will have to work with Fatwire’s “proven migration tools and services” which probably means you will need to work with Fatwire, Vamosa and Kapow’s professional services. All the three products (Interwoven, Vignette and Fatwire) have decent mechanisms for importing and exporting content. So content migration per se is certainly not the most challenging aspect. In particular, when you migrate from Interwoven to Fatwire, there are many other challenges depending on what version of TeamSite you are using. TeamSite’s delivery templates are totally different from those of Fatwire’s. If you are using the Perl based PTs (Presentation Templates) and doing a static publishing, your challenges are even bigger. There are many other issues as well – different ways of defining assets, all the complex customizations, different storage (XML Vs Database), workflows and so on.  Vignette, although more similar to Fatwire than Interwoven in terms of architecture, will also have similar challenges. Apart from technical challenges, any content management implementation and content migration has its own sets of challenges in terms of user training, ensuring content quality (Vamosa has some useful offerings here as well), different skill sets and so on. Here’s a nice take on different issues by Jon

I could write a big article on just the differences between Fatwire and Vignette/Interwoven and resulting challenges but the point is that don’t assume it is only about ”content” migration. You will need to budget for many other things as well.

These are some observations, in no particular order. I will possibly post some “more sensible” posts on specific topics later.

• It was first time for me at EMC World and I thought the focus was much more on storage and infrastructure as compared to content management. They did certainly much better though in terms of integrating CMA (Content Management and Archival) with the overall EMC World. A lot of people who I talked to thought it was actually much better than that in the past when CMA folks felt quite out of place.
• A big theme at the conference was about building social communities. Joe Tucci, the EMC Chairman started his key note with some statistics on tweets about the EMC World. He spoke about how EMC is working to give its customers more choice, better control and improved efficiencies. There was a dedicated blogger’s lounge, set up by Len Devanna and his team, which provided a great informal environment for bloggers and tweeps to come together and socialize. I am glad I was able to meet Laurence (pie), Len and Stu. There were other lounges on similar lines and in particular, the Momentum lounge provided a good place for Documentum users to meet.
• Then there was CMA president Mark Lewis’ key note. He talked of ROI as return on information.
• I was particularly interested in EMC’s initiatives around Customer Communication Management (or rather around their xPression product which came via the acquisition of Doc Sciences). Although, there were a few (and good) sessions on this, I was hoping for a bigger presence. They had a small, not so prominent booth within a large EMC booth.
• Another interesting announcement (although this was done a couple of days before EMC World) was about free availability of the developer edition of Documentum. I think this is a great move to increase usage and acceptance of Documentum. EMC claims it takes 23 minutes to get up and running with Documentum, although i suspect it will take much more to download it – It is almost a 2 GB download and has steep RAM requirements (recommended 4 GB although 3 GB would work too) and so it would not be as easy to run it (on a laptop) as it is with some other products.This will essentially enable developers to get their hands dirty which in turn will help in more spreading of Documentum.  The developer edition comes bundled with Jboss and SQL Server Express database.
• Some claimed that there were 7000 attendees but I felt the number was lower. I also think that number of customers, especially those interested in content management were far less than previous times. Although there were quite a few partners, the big partners were noticeable by their absence.
• CMIS was reasonably covered. There was a dedicated session by Laurence and Karin Ondricek as well as Victor Spivak covered it in his session on D 6.5 architecture. Laurence demoed the federated CMIS sample application and according to him, the fact that Alfresco and Nuxeo allowed their servers to be up for Documentum conference showed the high amount of cooperation happening on CMIS.
• Victor was quite clear about the scope of CMIS and more importantly what it is not. According to him, “I” is the most important letter in the acronym and in that sense, the objective is to provide interoperability and not implement more sophisticated features. And so the focus is only on basic services, mashup type of applications and not real business applications which are best handled by proprietary APIs (like DFS) or CMS specific features. He also said If you were to describe 6.5 release in 1 sentence, it would be “high volume services”.
• There were quite a few sessions on WCM and more “Delivery oriented” aspects like Dynamic delivery, site management, Web 2.0, RIAs and so on. EMC has also latched on to the term Web Experience Management (WEM), something that Vignette and Fatwire have been using for some time. Web Publisher is not yet as sophisticated a platform for WCM and it remains to be seen how they do it.
• Most of the sessions were EMC specific and by EMC and I think the number of independent sessions should be increased. I attended the one by Jeetu Patel of Doculabs in which he talked about different type of ROI modeling for ECM projects.
• There were quite a few sessions on CenterStage. Victor talked about the philosophy behind center stage and that was to separate front end completely from business logic and backend because front end technologies have been changing quite often. I think this is an obvious way and wonder why this was not done in Webtop. He also explained the increasing support for restful apis etc. (See Pie’s post here ).
• There were also few discussions around Lucene replacing FAST search in EMC’s products.

I’d be traveling over next couple of weeks mainly to attend EMC World in Orlando and meet customers in the US. We have been working on some interesting concepts (Hosted Document Services, Factory Model and ECM Maturity Model) and I will take this opportunity to socialize these and get feedback from our customers.

This is my first time at EMC World and i’ve heard good things about it. I’m  especially looking forward to the Bloggers Lounge.

By the way, we (Wipro) also have a booth at the conference. So if you are there and want to say hello, do drop in.

After Autonomy/Interwoven and Oracle/Sun news, here comes the third big news of the year.

If Unilever can have multiple soaps and GM can have multiple car models, why can’t a Content Management vendor have multiple products? OT’s acquisition of Vignette points to this increasing “commoditization” of Content Management marketplace.

There may be a lot of overlaps in products across OT and Vignette but we all know that one size does not fit all and so why not have different products for different scenarios, different price points, different technology stacks and different requirements?  OT now has multiple options for Document Management, DAM, WCM etc plus a bonus portal server that they lacked before. They had a portal integration kit (PIK) that exposed LiveLink’s functionality as portlets that could be deployed on some of the portal servers (but not VAP and Sun as far as I know).

There’s some good analysis here and here.

On a side note, I think people who worked closely with Vignette knew it coming. A colleague of mine told me this:

One Singapore based vignette customer we were talking to  suddenly went quiet and our sales guy spotted him meeting OpenText. Another one who we were talking to, suddenly decided not to continue with Vignette and decided to migrate to Day communiqué. A senior person in Vignette Singapore joined OpenText about 2-3 months back – and was not replaced. There were many other signs in the way Vignette was handling people and partnerships that showed something is on.

I always considered Interwoven, Vignette and Fatwire (Open Market, Divine and FutureTense before that) as the leaders and pioneers in pure play Web Content space. With Interwoven and Vignette gone, what does this mean for the WCM marketplace? An end of the era?

Oracle announced it will acquire Sun.

Another big Portal/Content Management vendor is now an infrastructure vendor. Sometimes I wonder if  everything will soon become an appliance – you buy a Solaris box and it will come bundled not only with the OS (obviously) but also with WebCenter (or one of the numerous Oracle Portal type products), Content Server and so on. IBM, EMC and Microsoft can do this already in some sense.

Sun had open sourced its entire JES or Java ES (Java Enterprise System) sometime back and more recently dropped the JES Portal Server in favor of a partnership with Liferay. The result was WebSynergy, Sun’s branded portal based on Liferay’s codebase. It is not clear how Oracle will continue this partnership and frankly  they already have too many portal kind of offerings to continue with this. However, I think Liferay has a strong offering (and recently opened a new office in India) and will continue to be a good open source alternative whether or not Oracle continues this partnership.

The other component of JES that might have some relevant features is probably Sun Java Communications Suite which has features for collaboration  – things like calendar, messaging, Instant messenger as well as support for mobile communications. Some of these could be good additions to Oracle’s Fusion.

On a different note though, Janus had this to say on twitter:

Oracle buys sun – now Oracle has 5 enterprise portals! a new commercial for Larry: 5 out of 12 most significant portals are powered by ORCL

In spite of that, they had to resort to static pages!?