Don’t miss the AIIM Social Business Virtual Conference on September 8th, 2011. Get answers to these questions: What types of business processes can benefit from using social technologies? Are records and information managers able to achieve meaningful governance in a social world, or are they just getting in the way? Will conventional content and process management applications be able to adapt to a new generation of always on, always connected information workers? How can you develop an effective social business strategy? Registration More than 30 sessions to choose from. Pick the tracks that fit you the best: strategies — Get strategies for engaging customers and empowering staff. View list of sessions > use cases — Learn from the experience of early adopters and visionaries. View list of sessions > governance — Learn how to manage social processes and technologies. View list of sessions >

[As is the case with our 8 things series, the opinions expressed in the 5 myths guest columns are those of the guest contributor and not necessarily mine or AIIM's. This guest post is by Jeff Carr, Senior Consultant and Information Architect, and Seth Earley, CEO of Earley & Associates, Inc. As usual, contra perspectives welcome.] Many organizations are finding that leveraging the full suite of capabilities SharePoint offers requires introduction of a new requirement – that of dealing with, managing and exploiting taxonomies. Of course taxonomies are not new, but there is some confusion about where managed metadata services and the term store end and true taxonomy management begins. There are also some misconceptions about the process of deriving and applying taxonomies in SharePoint. The following are five areas of confusion that we have seen in our engagements and research. Myth #1: SharePoint now has taxonomy management Reality — The term store management tool is not a taxonomy management system. It is called a term store and not the taxonomy manager for a reason. True taxonomy management allows for various types of relationships beyond the parent child (kudos to the SharePoint product team for addressing the lack of hierarchy…

[As is the case with our 8 things series, the opinions expressed in the 5 myths guest columns are those of the guest contributor and not necessarily mine or AIIM's. This guest post is by Northern Light's CEO C. David Seuss. As usual, contra perspectives welcome.] Myth #1 — SharePoint was not developed by a secret team of Microsoft Tribbles. Reality — Actually, I believe it was. Many companies today are discovering that SharePoint has led to a rapid and uncontrolled spawning of user-created portals, just like that cute but pesky first pair of tribbles that spawned so many offspring so quickly that they almost overwhelmed the starship Enterprise. I have heard many companies report to their astonishment that after deploying SharePoint they had thousands of SharePoint sites thrown up by employees. One company recently told me, as they tried to work through a degree of shock that suggested the need for professional therapeutic intervention, that they had determined just that morning that there were 30,000 SharePoint sites on their network. Surely a team of programming tribbles produced such an application. Myth #2 — You can share stuff with SharePoint. Reality — You cry out, “How can this be a…

A primary goal in the specification of CMIS is to protect past investments of both customers and software vendors. This will not lead to technological perfection but will help customers to unlock the hidden value of information by breaking down the information silos.