Box.net announced new integration with Google Docs. Box users can now create, edit and concurrently edit with Google Docs. In the announcing blog post, doubt was expressed by Box.net over Microsoft opening Office 365 to 3rd party developers like themselves, and thus implies that this integration with Google will be the focus of the Box.net platform for the foreseeable future. http://www.box.net/
May 12, 2010 / NewsShark / Comments Off on Office 2010, SharePoint 2010 Available for Business Customers Today
Microsoft has announced that the 2010 release of Office, SharePoint, Visio and Project are available to business customers worldwide. 2010 Releases are Available to Businesses after Record Beta Adoption: The beta programs for Office 2010 and SharePoint 2010 were the largest in the products’ history, reaching three times the size of prior Office beta programs. As a result, 8.6 million people are already using Office 2010 and related products. In addition, more than 1,000 partners are already building solutions for the 2010 set of products. Office, Project and Visio will be generally available online and in retail outlets in the U.S. on June 15th. Microsoft’s Office Web applications will be available to all Office volume licensing customers, offering productivity technologies in the cloud. In addition, customers will be able to purchase a subscription to Office Web Apps as part of Microsoft Online Services, Microsoft’s cloud-based applications. Office 2010 and SharePoint 2010 are available in 14 languages, and over the next few months, 80 more languages will be added. A live webcast further detailing this release can be viewed at 11 AM EST 5/12/10. www.the2010event.com
In a move to strengthen reach in the Asian market, Adeptol announced that it has signed a partnership agreement with VersaPAC, a solution provider of information management systems and reseller of HP TRIM records management software. With the partnership VersaPAC is moving from a legacy viewing system to Adeptol’s document viewing technology embedded in its Saffron web front-end application for HP TRIM. Saffron is available through VersaPAC resellers in Australia, Malaysia, New Zealand, North America, and the United Kingdom. The integration allows Saffron to support viewing of over 300 file formats including documents from Microsoft Office, OpenOffice, various image files, and Adobe PDF. Users will have access to the latest features such as document search, annotations, and document conversion to PDF – all from the viewer. Adeptol Document Viewer is a web-based viewer using Ajax technology, and is a built-in Information Rights Management (IRM) module that allows users to protect content by assigning policies to control the viewing, printing, navigating and saving of documents. http://www.ajaxdocumentviewer.com/http://www.versapac.com.my/
I spent a couple of days at the SharePoint conference two weeks ago with about 8000 others. Many attendees were customers, but the majority seemed to be Microsoft partners. It would be difficult to overstate the enthusiasm of the attendees. The partners especially, since they make their living off SharePoint. There has been a lot of useful reporting and commentary on the conference and what was announced as part of SharePoint 2010, which you can find on the web, #spc09 is also still active on Twitter, and videos of the keynotes are still available at: http://www.mssharepointconference.com.
As the conference program and commentary illustrate, SharePoint 2010 is a major release in terms of functionality. But the messaging surrounding the release provides some important insights into Microsoft’s strategy. Those of you who were at Gilbane San Francisco last June got an early taste of Microsoft’s plans to push beyond the firewall with SharePoint – and that is the big story. It is big because it is a way for Microsoft to accelerate an already rapidly growing SharePoint business. It is big for a large number of enterprises (as well as the SharePoint developer/partner ecosystem) because it is a way for them to leverage some of their existing investment in SharePoint for building competitively critical internet applications – leverage in expertise, financial investment, and data.
The numbers are telling. According to an IDC report Microsoft Office and SharePoint Traction: An Updated Look at Customer Adoption and Future Plans, IDC # 220237, October 2009, of “262 American corporate IT users, just 8% of respondents said they were using SharePoint for their Web sites, compared to 36% using it for internal portals and 51% using it for collaborative team sites.” (the report isn’t free, but ComputerWorld published some of the numbers).
Can Microsoft increase the use of SharePoint for Web sites from 8% to 36% or 51% or more? Whether they can or not, it is too big an opportunity for them to ignore, and you can expect the market for web applications like content management to look a little different as a result. Of course SharePoint won’t be the right solution for every web application, but Microsoft needs scale, not feature or market niche dominance.
There are more pieces to this, especially integration with Office 2010, which will have a major impact on the scale of penetration. We’ll look at that issue in another post.
You can see why SharePoint is a major topic at Gilbane Boston this year. Join us next month to continue the discussion and learn more.
Microsoft has a lot to lose if they are unable to coax customers to continue to use and invest in Office. Google is trying to woo people away by providing a complete online experience with Google Docs, Email, and Wave. Microsoft is taking a different tact. They are easing Office users into a Web 2.0-like experience by creating a hybrid environment, in which people can continue to use the rich Office tools they know and love, and mix this with a browser experience. I use the term Web 2.0 here to mean that users can contribute important content to the site.
SharePoint leverages Office to allow users to create, modify, and display “deep” content, while leveraging the browser to navigate, view, discover, and modify “shallow” content. SharePoint is not limited to this narrow hybrid feature set, but in this post I examine and illustrate how Microsoft is focusing its attention on the Office users. The feature set that I concentrate on in this post is referred to as the “Collaboration” portion of SharePoint. This is depicted in Microsoft’s canonical six segmented wheel shown in Figure 1. This is the most mature part of SharePoint and works quite well, as long as the client machine requirements outlined below are met.
Figure 1: The canonical SharePoint Marketing Tool – Today’s post focuses on the Collaboration Segment
Preliminaries: Client Machine Requirements
SharePoint out-of-the-box works well if all client machines adhere to the following constraints:
The client machines must be running Windows OS (XP, Vista, or WIndows 7) NOTE: The experience for users who are using MAC OS, Linux, iPhones, and Google phones is poor. 
The only truly supported browser is Internet Explorer (7 and 8.)  NOTE: Firefox, Safari, and Opera can be used, but the experience is poor.
The client machines need to have Office installed, and as implied by bullet 1 above, the MAC version of Office doesn’t work well with SharePoint 2007.
All the clients should have the same version of Office. Office 2007 is optimal, but Office 2003 can be used. A mixed version of Office can cause issues.
A number of tweaks need to be made to the security settings of the browser so that the client machine works seamlessly with SharePoint.
I refer to this as a “Microsoft Friendly Client Environment.”
Some consequences of these constraints are:
SharePoint is not a good choice for a publicly facing Web 2.0 environment (More on this below)
SharePoint can be okay for a publicly facing brochureware site, but it wouldn’t be my first choice.
SharePoint works well as an extranet environment, if all the users are in a Microsoft Friendly Client Environment, and significant attention has been paid to securing the site.
A key take-away of these constraints is that a polished end user experience relies on:
A carefully managed computing environment for end users (Microsoft Friendly Client Environment) and / or
A great deal of customization to SharePoint.
This is not to say that one cannot deploy a publicly facing site with SharePoint. In fact, Microsoft has made a point of showcasing numerous publicly facing SharePoint sites .
What you should know about these SharePoint sites is:
A nice looking publicly facing SharePoint site that works well on multiple Operating Systems and browsers has been carefully tuned with custom CSS files and master pages. This type of work tends to be expensive, because it is difficult to find people who have a good eye for aesthetics, understand CSS, and understand SharePoint master pages and publishing.
A publicly facing SharePoint site that provides rich Web 2.0 functionality requires a good deal of custom .NET code and probably some third party vendor software. This can add up to considerably more costs than originally budgeted.
An important consideration, before investing in custom UI (CSS & master pages) , third party tools, and custom .NET code is that they will most likely be painful to migrate when the underlying SharePoint platform is upgraded to the next version, SharePoint 2010. 
By the sound of these introductory paragraphs, you might get the wrong idea that I am opposed to using SharePoint. I actually think SharePoint can be a very useful tool, assuming that one applies it to the appropriate business problems. In this post I will describe how Microsoft is transitioning people from a pure Office environment to an integrated Office and browser (SharePoint) environment.
So, What is SharePoint Good at?
When SharePoint is coupled closely with a Microsoft Friendly Client Environment, non-technical users can increase their productivity significantly by leveraging the Web 2.0 additive nature of SharePoint to their Office documents.
Two big problems exist with the deep content stored inside Office documents (Word, Excel, PowerPoint, and Access,)
Hidden Content: Office documents can pack a great deal of complex content in them. Accessing the content can be done by opening each file individually or by executing a well formulated search. This is an issue! The former is human intensive, and the latter is not guaranteed to show consistent results.
Many Versions of the Truth: There are many versions of the same files floating around. It is difficult if not impossible to know which file represents the “truth.”
SharePoint 2007 can make a significant impact on these issues.
Go into any organization with more than 5 people, and chances are there will be a shared drive with thousands of files, Microsoft and non-Microsoft format, (Word, Excel, Acrobat, PowerPoint, Illustrator, JPEG, InfoPath etc..) that have important content. Yet the content is difficult to discover as well as extract in an aggregate fashion. For example, a folder that contains sales documents, may contain a number of key pieces of information that would be nice to have in a report:
Date of sale
Total Sale in $’s
Categorizing documents by these attributes is often referred to as defining a taxonomy. SharePoint provides a spectrum of ways to associate taxonomies with documents. I mention spectrum here, because non-microsoft file formats can have this information loosely coupled, while some Office 2007 file formats can have this information bound tightly to the contents of the document. This is a deep subject, and it is not my goal to provide a tutorial, but I will shine some light on the topic.
SharePoint uses the term “Document Library” to be a metaphor for a folder on a shared drive. It was Microsoft’s intent that a business user should be able to create a document library and add a taxonomy for important contents. In the vernacular of SharePoint, the taxonomy is stored in “columns” and they allow users to extract important information from files that reside inside the library. For example, “Customer”, “Date of Sale,” or “Total Sale in $’s” in the previous example. The document library can then be sorted or filtered based on values that are present in these columns. One can even provide aggregate computations based the column values, for example total sales can be added for a specific date or customer.
The reason I carefully worded this as a “spectrum” is because the quality of the solution that Microsoft offers is dependent upon the document file format and its associated application. The solution is most elegant for Word 2007 and InfoPath 2007, less so for Excel and PowerPoint 2007 formats, and even less for the remainder of the formats that are non-Microsoft products.. The degree to which the taxonomy can be bound to actual file contents is not SharePoint dependent, rather it is dependent upon how well the application has implemented the SharePoint standard around “file properties.”
I believe that Microsoft had intended for the solution to be deployed equally well for all the Office applications, but time ran out for the Office team. I expect to see a much better implementation when Office 2010 arrives. As mentioned above, the implementation is best for Word 2007. It is possible to tag any content inside a Word document or template as one that should “bleed” through to the SharePoint taxonomy. Thus key pieces of content in Word 2007 documents can actually be viewed in aggregate by users without having to open individual Word documents.
It seems clear that Microsoft had the same intention for the other Office products, because the product documentation states that you can do the same for most Office products. However, my own research into this shows that only Word 2007 works. A surprising work-around for Excel is that if one sticks to the Excel 2003 file format, then one can also get the same functionality to work!
The next level of the spectrum operates as designed for all Office 2007 applications. In this case, all columns that are added as part of the SharePoint taxonomy can penetrate through to a panel of the office application. Thus users can be forced to fill in information about the document before saving the document. Figure 2 illustrates this. Microsoft refers to this as the “Document Information Panel” (DIP). Figure 3 shows how a mixture of document formats (Word, Excel, and PowerPoint) have all the columns populated with information. The disadvantage of this type of content binding is that a user must explicitly fill out the information in the DIP, instead of the information being bound and automatically populating based on the content available inside the document.
Figure 2: Illustrates the “Document Information Panel” that is visible in PowerPoint. This panel shows up because there are three columns that have been setup in the Document library: Title, testText, and testNum. testText and testNum have been populated by the user and can be seen in the Document Library, see figure 3.
Figure 3: Illustrates that the SharePoint Document Library showing the data from the Document Information Panel (DIP) “bleeding through.” For example the PowerPoint document has testText = fifty eight, testNum = 58.
Finally the last level on the taxonomy feature spectrum is for Non-Microsoft documents. SharePoint allows one to associate column values with any kind of document. For example, a jpeg file can have SharePoint metadata that indicates who the copyright owner is of the jpeg. However this metadata is not embedded in the document itself. Thus if the file is moved to another document library or downloaded from SharePoint, the metadata is lost.
A Single Version of the Truth
This is the feature set that SharePoint implements the best. A key issue in organizations is that files are often emailed around and no one knows where the truly current version is and what the history of a file was. SharePoint Document libraries allow organizations to improve this process significantly by making it easy for a user to email a link to a document, rather than email the actual document. (See figure 4.)
Figure 4: Illustrates how easy it is to send someone a link to the document, instead of the document itself.
In addition to supporting good practices around reducing content proliferation, SharePoint also promotes good versioning practices. As figure 5 illustrates any document library can easily be setup to handle file versions and file locking. Thus it is easy to ensure that only one person is modifying a file at a time and that the there is only one true version of the file.
Figure 5: Illustrates how one can look at the version history of a document in a SharePoint Document Library..
In this post I focus on the feature set of SharePoint that Microsoft uses to motivate Office users to migrate to SharePoint. These features are often termed the “Collaboration” features in the six segmented MOSS wheel. (See figure 1) The collaboration features of MOSS are the most mature part of SharePoint and thus the most . Another key take-away is the “Microsoft Friendly Client Environment.” I have worked with numerous clients that were taken by surprise, when they realized the tight restrictions on the client machines.
Finally, on a positive note, the features that I have discussed in this post are all available in the free version of SharePoint (WSS), no need to buy MOSS. In future posts, I will elaborate on MOSS only features.
 The terms “deep” and “shallow” are my creation, and not a standard. By “deep” content I am referring to the complex content such as a Word documents (contracts, manuscripts) or Excel documents (complex mathematical models, actuarial models, etc…)
 Microsoft has addressed this by stating that SharePoint 2010 would support some of these environments. I am somewhat skeptical.
 Public Facing internet sItes on MOSS, http://blogs.microsoft.nl/blogs/bartwe/archive/2007/12/12/public-facing-internet-sites-on-moss.aspx
 Microsoft has stated frequently that as long as one adheres to best practices, the migration to SharePoint 2010 will not be bad. However, Microsoft does not have a good track record on this account for the SharePoint 2003 to 2007 upgrade, as well as many other products.
Mark Logic Corporation released the MarkLogic Toolkit for Excel. This new offering provides users a free way to integrate Microsoft Office Excel 2007 with MarkLogic Server. Earlier this year, Mark Logic delivered a Toolkit for Word and a Connector for SharePoint. Together, these offerings allow users to extend the functionality of Microsoft Office products and build applications leveraging the native document format, Office Open XML (OOXML). Distributed under an open source model, MarkLogic Toolkit for Excel comes with an Excel add-in that allows users to deploy information applications into Excel, comprehensive libraries for managing and manipulating Excel data, and a sample application that leverages best practices. The MarkLogic Toolkit for Excel offers greater search functionality, allowing organizations to search across their Excel files for worksheets, cells, and formulas. Search results can be imported directly into the workbooks that users are actively authoring. Workbooks, worksheets, formulas, and cells can be exported directly from active Excel documents to MarkLogic Server for immediate use by queries and applications. The Toolkit for Excel allows customers to easily create new Excel workbooks from existing XML documents. Users can now manipulate and re-use workbooks stored in the repository with a built-in XQuery library. For instance, a financial services firm can replace the manual process of cutting-and-pasting information from XBRL documents to create reports in Excel with an automated system. Utilizing Toolkit for Excel, this streamlined process extracts relevant sections of XBRL reports, combines them, and saves them as an Excel file. The Toolkit also allows users to add and edit multiple custom metadata documents across workbooks. This improves the ability for users to discover and reuse information contained in Excel spreadsheets. To download MarkLogic Toolkit for Excel, visit the Mark Logic Developer Workshop located at http://developer.marklogic.com/code/, http://www.marklogic.com
April 28, 2009 / NewsShark / Comments Off on Microsoft Releases Service Pack 2 (SP2) for the 2007 Microsoft Office system
Microsoft announced the availability of Service Pack 2 (SP2) for the 2007 Microsoft Office system. The service pack includes major performance enhancements for Office applications, most notably Microsoft Office Outlook, as well as Microsoft Office SharePoint Server. With SP2, Office 2007 now has built-in support for Open XML, ODF and PDF, along with the dozen or so other formats that were already supported in Office 2007. In addition to the support for additional file formats, SP2 also includes the Open XML Format External File Converter. This allows developers to make any third-party document format a first-class citizen in Office. This means Office will support most government-preferred formats, and can easily be made to support any others that come along. This release offers enhanced stability for Outlook, calendaring reliability, and more improvements to applications that run on both PCs and servers. Users should notice the improved performance and stability of Outlook, better charting functionality in Excel, and more control over the appearance of SmartArt graphics. On the server side, IT professionals will notice several enhancements to the security and performance of SharePoint Server 2007, including support for read-only content databases, improvements to forms-based authentication, and an STSADM command-line utility that enables administrators to scan sites that use the variations feature for errors. SharePoint Server will also feature better support for newer versions of the Firefox browser. Customers can download SP2 right away. In addition, Microsoft will release SP2 via Microsoft Update’s automatic update mechanism no sooner than three months from now, and with at least 30 days notice. http://support.microsoft.com/kb/968170
Microsoft Corp. released a public beta of Microsoft Exchange Server 2010, part of Microsoft’s unified communications family. Exchange 2010 is part of the next wave of Microsoft Office-related products and is the first server in a new generation of Microsoft server technology built from the ground up to work on-premises and as an online service. This release of Exchange 2010 introduces an integrated e-mail archive and features to help reduce costs and improve the user experience. The next wave, which includes Microsoft Office 2010, Microsoft SharePoint Server 2010, Microsoft Visio 2010 and Microsoft Project 2010, is designed to give people a consistent experience across devices, making it easier to create and edit documents and collaborate from any location. In addition, to help businesses reduce costs, the next wave will introduce new delivery and licensing models, improve deployment and management options for IT professionals, and provide developers with an expanded platform on which to create applications. Exchange Server 2010 will become available in the second half of 2009. Additional Office products including Microsoft Office 2010, Microsoft SharePoint Server 2010, Microsoft Visio 2010 and Microsoft Project 2010 are scheduled to enter technical preview in the third quarter of 2009 and release to manufacturing in the first half of 2010. A public beta of the server is available for download starting today at http://www.microsoft.com/exchange/2010