Wednesday, June 30, 2010
Version 4.2 of Colligo Network’s Contributor for SharePoint family of products launched yesterday, with compatibility for Microsoft Office 2010 and for SharePoint 2010’s new features around enterprise content management.
According to the company, highlights of the release include support for Outlook 2010 for Contributor Pro, Add-In and Uploader customers; the support of Keyword Metadata fields within the Colligo metadata editor; and in-place records management.
The metadata editor lets users set, edit and modify terms in their “folksonomies, while in-place records management restricts access and use of items stored in SharePoint.
Further, Contributor 4.2 enables users to dowload document sets from the server for viewing or modification, and identify them with special icons. Also, optimizations to processing and synchronization of content with the Contributor SQL database have been built in to better performance.
Thursday, June 17, 2010
In SharePoint Server 2010 you’ll need to manually configure your sites to use SharePoint Server Search. You might be thinking to yourself that you already have search and that might be true, but out of the box most site collection templates are preconfigured to use the contextual search that only allows you to search for content from within a specific site or list.* The contextual search isn’t what most people think of when they think of the robust enterprise search capabilities of SharePoint Server search. Most people think of SharePoint Server Search as having the ability to search across site collections and web applications and return rich results that have a relevancy algorithm applied to it with the most relevant results floating to the top.
In SharePoint Server 2010 in order to get the robust features of SharePoint Server search working for your site there’s a few steps involved. The following example walks you through the steps of manually configuring SharePoint Server search and assumes you are using a Team Site template. However, the same steps should apply for any of the templates:
1. Assuming you are logged in as a site collection administrator, click on Site Actions > Site Settings and then click Site collection features from under the Site Collection Administration section.
2. If it isn’t already activated, press the Activate button for the Search Server Web Parts.
3. Create a new subsite by clicking Site Actions > New Site and then select the Basic Search Center template. If you choose to use the Enterprise Search Center template you’ll need to make sure the SharePoint Server Publishing Infrastructure feature is enabled or else you’ll get an error.
4. Once the site has been created, go back to the site settings page on the top level site in the site collection. Assuming you are logged in as a Site Collection Administrator (which you’ll need to be if you are not) click on the Search settings link under the Site Collection Administration section.
5. In the first section called Site Collection Search Center change the radio button to “Enable custom scopes” and specify to use the URL of the new search center you just created. Usually something like “/search” (without the quotations).
6. Then, change the option in the section for Site Collection Search Dropdown Mode to “Show and default to contextual scope.” Press OK.
If you did this from a Team Site, you’ll notice that you can now see the scopes drop down next to the search box. You’ll also now have the ability to use the All Sites scope (from the dropdown) which allows you to search across all sites that are associated with that particular search service application. In most environments this means you can search across site collections and even web application for all content that you have access to.
* There is one exception to this -- the Publishing Portal site collection template actually has a Search Center already created. SharePoint search is ready to go out of the box!
Thursday, June 10, 2010
One point that came to light in comments to the post is that folks who are firmly on SharePoint 2007 are concerned that conferences are simply presenting information on SharePoint 2010, because it is new, and perhaps more interesting for speakers to talk about.
I came to understand this in the fall of 2009 by attending SharePoint Saturday events and a Microsoft-sponsored event in New York City, at which most of the attendees indicated they were not even at the point of previewing 2010, let alone making plans to adopt it. This was reinforced at SPTechCon in February, when keynote speaker Tom Rizzo, former SharePoint honcho at Microsoft, asked for a show of hands of people moving to 2010, and very few went up.
We're quite conscious of this. Philosophically, we're not first movers, and we understand the reluctance of people whose software works just fine to move to something new. Without a provable business benefit -- and given Microsoft's history of first releases not being as solid as they might be -- standing pat is an important option for many.
So, at SPTechCon in February, when speakers were clamoring to be first to talk about the new features in 2010, we made sure we reserved a good 40 percent of the program for folks who were continuing on with MOSS 2007. And for SPTechCon in October, we again have made sure there are plenty of sessions that apply specifically to 2007, or to ALL the different versions of SharePoint. But of course, we will have the requisite sessions on migrating to 2010, and sessions that take a deeper look into the new pillars and features.
Check out the program for October's SPTechCon. Then, feel free to let me know if there are topics you would have preferred to see. That'll help us to make SPTechCon 2011 even more relevant to you!
Monday, June 7, 2010
Rick Pleczko, president and CEO of Idera, told the SPTechBlog that Idera had security reporting in its SharePoint admin toolset, but that customers wanted to know not only who can see what, but wanted the ability to audit and ensure security as well as administer changes to the security profile. "It makes the SharePoint security model very easy to manage," he said.
Today, the tool formerly known as iDevFactory's Universal SharePoint Manager is being made available as Idera SharePoint Security Manager, Pleczko said, with support for SharePoint 2010. It will sell for US$4,995. This addition gives Idera a broad portfolio of admininstration products that covers backup and recovery, migration, performance monitoring and security management, Pleczko noted.
To maintain product continuity, Pleczko said the enire iDevFactory team is joining Idera, located in Houston, Texas.
In fact, there was this interesting tweet recently:
"My I suggest, we appoint leadership to the #SharePoint #Community, & have a more organized effort helping one another through elected roles."
While truly an admirable goal, one thing I’ve learned in my years in newspapers, covering “communities,” is that there is never – EVER – one community. The fact is, too many people have their own view of the “community,” and their own interests, and often, those don’t mesh with someone else’s ideas.
At SD Times, our flagship newspaper for software developers, we cover what has become known as “the open-source community.” These are folks who advocate the free (as in beer) exchange of code with limited restrictions, where anyone can contribute to a project with the reward of knowing they’ve done something for a greater good.
Yet in looking closely, the so-called open-source community is really a collection of smaller, fractured communities. There’s the Eclipse community for folks working in Java; the Linux community for people working on that operating system kernel; the Hadoop project for handling huge volumes of data; and the list goes on and on.
It’s no different in SharePoint. While the software is the common banner under which we all work, some folks come at it from a developer standpoint, while others are administrators and still others are business users. Some people are designers, working on external Web sites; others are data managers, looking to keep information organized. In fact, on Facebook, there are discrete pages for SharePoint developers, architects, administrators, as well as Microsoft’s general SharePoint information page. They clearly see themselves are part of smaller communities under the SharePoint flag.
And that’s OK. The one true leader of the SharePoint community is Microsoft. The company gets to decide on new features, new directions and release dates. We can band together around the parts of SharePoint that are relevant to us, and that’s fine. But to suggest one group of leaders, one website or one type of training can serve -- or worse, GOVERN -- “the SharePoint community” is not the case. There’s a place for everyone within this community, and all of those voices can and should be heard.