Author: Jeff Potts

Google Mini gets more capacity

Google Adds More Capacity to Google Mini Search Appliance. Google Inc. announced that the Google Mini has twice the search capacity at a more affordable price. The Google Mini can now search up to 100,000 documents for a lower price of $2,995. The Google Mini is an integrated hardware/software search appliance that indexes all content within a company’s intranet or public website…The entry-level Google Search Appliance now offers search of up to 500,000 documents (more than three times the previous search capacity), for $30,000 including hardware, software, and two years of customer support. Other versions of the Search Appliance can index 15 million documents or more in a single collection. The Search Appliance provides enterprise-wide search across corporate web sites, intranets, databases, business applications and content management systems. http://www.google.com/enterprise [Gilbane Report News]

The future of portals

“Technology” is one of the three converging forces. Under that heading, Charlie notes how blogs and CMS/Portals are converging.

Technology: the perfect storm for portals?. Charlie Wood has written a blog entry on the uncertain future of portals. To quote: The enterprise portal industry stands squarely in the path of three converging forces, any one of which could be devastating. Together, they might be fatal…. [Column Two]

WDK 5 Reporting Component

WDK 5 Reporting Component. This WDK 5 component allows you to run reports from within Webtop. The reports are specified using an XML file which contains a DQL query and formatting instructions. The Developer Program team will make use of this component to create administrative reports which will be released in the Component Exchange. UPDATED April 11, 2005: Added a new feature to export results to a tab separated file that can be opened in Microsoft Excel. [EMC Documentum Developer Program – New Content]

Recent Reads

Sea of Glory: America’s Voyage of Discovery, the U.S. Exploring Expedition, 1838-1842, by Nathaniel Philbrick.
This is the story of America’s first trans-oceanic expedition. The story is very interesting but I felt like the book really wallowed too much into the mundane detail. I found myself really pushing to finish it. The detail behind Wilkes’ leadership, however, is a great anti-pattern (an example of what not to do), particularly when compared to the outstanding performance of Shackleton.

Shackleton’s Way: Leadership Lessons from the Great Antarctic Explorer, by Margot Morrell, Stephanie Capparell.
The explicit leadership advice is mostly common sense but it does offer insight into Shackleton’s thought process as well as additional biographical and historical details not found in the Lansing text. It definitely inspired me to (1) think about Shackleton’s leadership style and attempt to apply it day-to-day and (2) read more about the Shackleton story. The rich depth and detail provided in some of the books anecdotes is illustrative of the partiular point they are trying to make, but I want to learn the whole story at that level of detail rather than the segments that suited the authors needs. (That’s not a dig on the book at all).

The Cruelest Miles: The Heroic Story of Dogs and Men in a Race Against an Epidemic, by Gay Salisbury, Laney Salisbury
I gave this as a gift to someone who then lent it back to me. It completed a hat-trick of ice cold adventure tales. Cruelest Miles is the story of the race to save Nome, Alaska during a diptheria outbreak in the early 1900’s. The story of the dog sled relay to get the serum to Nome is actually short enough to be covered in a long magazine article, but the authors expand it to book-length by detailing the history of Alaska’s frontier days, the evolution and technical details behind dog sledding, and biographical details on the significant people involved in the drama. The details grew tedious at times but overall it was exciting and interesting.

EContent open source CMS article

Open Source CMS Article in EContent Magazine.

There is a good article on open source content management systems in the latest (January/February) issue of EContent Magazine. Here are some key points: Frank Gilbane, of the Gilbane Report, is quoted: “If you have a spectrum where you build a CMS yourself on one end and commercial solutions at the other end, open source can sit in the middle.” I like this way of describing the role of open

By noemail@noemail.org (Seth). [Enter Content Here]

Corporate blogs and wikis

Corporate Use of Blogs and Wikis.

Lauren Wood, of The Gilbane Report has an excellent introductory article on the corporate use of Blogs and Wikis (factoid: did you know that “Wiki” is a Hawaiian word for “hurry” or “quick”?). The article gives real world examples of companies using blogs and Wiki’s for internal and external communication purposes. I agree with Lauren that these tools have great potential in the enterprise.

By noemail@noemail.org (Seth). [Enter Content Here]

Documentum desert island skills

My post on general ECM skills reminded me of an internal post on Documentum consulting skills. I thought I’d cross post it here in case anyone found it helpful. I’ve made minor edits to expand acronyms, clarify product names, or clear up other ambiguities but the post is pretty much intact.
 
What makes a great Documentum consultant?
 
So, what makes a great Documentum consultant? I think there are desert island skills that every one must have or that you’d really want to have if you were alone on a desert island facing some sort of Documentum project. There are also fringe skills that add value and could be critical depending on the project.
 
A consistent “why do you like working with DCTM” answer from the people we’ve interviewed is that people get to work with a wide variety of technologies. Looking at this list shows why. There aren’t many people that can fit this bill. It’s also important to note that someone broad enough to score well against these categories could actually be a great fit for non-Documentum projects.
 
Desert Island Documentum Skills (In no particular order)
  • Core consulting skills (project management, written & verbal communication, client management, selling, teamwork, confidence)
  • People-centric application experience (Collaboration, process, workflow)
  • Document-centric application experience
  • Documentum fundamentals: Workflow, Security, Object Model, Documentum Foundation Classes (DFC)
  • Basic Documentum administrative tasks (repository care-and-feeding, best practices, installing content server, creating a repository) 
  • Documentum Query Language, Basic SQL
  • Basic XML/XSLT
  • Basic operating system (starting/stopping processes, navigating the Documentum installation folder hierarchy, running programs/scripts, editing files, changing permissions/owners of files, setting environment variables, using XServer (for UNIX), administering users and groups)
  • Basic Relational Database (relational concepts, minimal SQL, ability to speak somewhat intelligently with a DBA)
  • Basic Java (knows what a classpath is, can write and compile a class, can leverage Javadocs)
  • Basic BASIC
  • Basic Web Development Kit (WDK)
  • Basic application server
  • HTML, JavaScript, CSS
  • Ability to negotiate IT processes and human resources
  • Troubleshooting and debugging
Fringe/Value-add Documentum Skills (In no particular order)
  • Intermediate to Advanced WDK, Business Objects Framework (BOF)
  • Java Server Faces, Struts, other frameworks
  • JSP, servlets, JDBC, EJB
  • Web services
  • All other Documentum products such as Web Publisher, InputAccel, Content Rendition Services, WebCache, Site Delivery Services, Content Intelligence Services, Digital Asset Manager/Rich Media Services, Business Process, Reporting Gateway, JDBC Services, Manager/FormsBuilder
  • Documentum federations, replication
  • High availability/high performance, load testing
  • Enterprise architecture
  • Identity management (Netegrity, Oblix)
  • Portals in general, Documentum WDK for Portals
  • Imaging, COLD, fixed asset management
  • Structured authoring tools (Epic, Framemaker, XMetal)
  • Web Services
  • Advanced XSLT, FOSI, SGML, Schema/DTD
  • Apache FOP
  • Enterprise Integration
  • Industry-specific or horizontal solutions (Collaboration/eRoom, Records Management, SarbOx, Aerospace, Pharma, Oil&Gas, Manufacturing)

So, a “great” Documentum consultant would have all of the “Desert Island Documentum Skills” nailed as well as the “Fringe/Value-Add Documentum Skills” applicable to the project at-hand.

Thoughts on skills for ECM professionals

Ann Rockley recently posed a question to the CMPros listserv about the skills needed for a successful Enterprise Content Management professional. Here’s my reply:

To really drill down on this topic, you have to be specific about what the ECM professional is trying to do. As we’ve discussed ad nauseum in other threads, the definition of “ECM”, “CM”, and “DM”, etc., mean different things to different people and often are umbrella terms–particularly with ECM–for different types of activities that require different skillsets.

As someone who’s done a fair amount of recruiting in this space, I can tell you there are many ECM professionals who spend many years working only in very specific ECM niches with very little exposure to the entire ECM spectrum of solutions.

So, my thoughts to Ann are from the perspective of a technical ECM consultant working on large implementations of packaged ECM offerings, primarily around WCM and document-centric workflows, with moderate amounts of customization.

Soft skills

Change management. The ability to anticipate and smooth out issues related to the substantial amount of change created by the implementation of ECM initiatives is critical.

Communication/leadership. Another key skill is the ability to sell the value of the ECM initiative to executive leaders, build consensus, recruit a champion, etc. Communication skills also play a part in crafting, sharing, and selling a vision of ECM at all levels of an organization.

Business process analysis. Most ECM initiatives include workflow. An ECM professional needs to know how to understand and possibly improve the business processes related to the content being managed.

Subject area expertise. It helps if a professional understands one or more CM “sub-disciplines” or horizontals such as technical publishing, WCM, imaging, compliance, etc. There may also be vertical industry niches in areas such as pharmaceuticals, energy, manufacturing, health care, etc. that professionals may choose to specialize in.

Technical skills:

 – XML/XSL
 – Java or .Net as well as one or more scripting languages
 – Application server platforms
 – Packaged content server offerings
 – Information architecture
 – Scanning hardware, storage solutions, etc.

Regarding academic curricula

As far as academic offerings, using what’s available today it seems like a computer science/library science double major would get you close. Obviously, a purpose-built curriculum incorporating relevant offerings from computer science, library science, and business administration would seem like the most optimal.