Bob Mixon

SharePoint IA: Store Information Close to the Point of Ownership

Bob Mixon — Sat, 27 Jun 2009 07:09:40 PDT

When its all said and done, users of a document management system typically have many places they can contribute content. In many implementations, these points of contribution can be so scattered it promotes confusion and future administration/maintenance problems.

For the purposes of this article, I want to focus on the Business Operations Content. This is typically the content that is important to the day-to-day operations of a business, content lifecycle is managed and user interaction is governed. Meaning, the intent is to provide a structured approach to the contribution and management of content so we can produce a level of trustability and findability.

The "Single Site" Approach to Storing a Specific Type of Content (Grouped by Topic)

Sending contributors to a specific location to store a specific type of content is very common in Intranet designs. An example of this would be to have a site titled "Corporate Policies"; every user in the organization who has the appropriate permissions can contribute to this site and manage their corporate policy documents.

Storing Information Grouped by Topic

I believe the thought process behind this design approach is to satisfy 2 user needs; 1 place for the contribution of information and 1 place for consumers to view a holistic list of all corporate policies.

While this approach may sound like the best solution, I contest its a bad idea. Let me provide an explanation.

The first problem with this approach is the model will expand to many, many sites (content topics) of different types. Users will ultimately have so many different places to contribute content, it will become confusing and difficult. This problem could be overcome by providing a dynamically and/or automatically updated list of "My Contribution Sites" on their My Site. However, this could also be cumbersome for the user as the list grows and grows.

The second, and more important, problem with this approach is the management of security. The only way to truly maintain a level of trustable content, you will be required to utilize item-level permissions; allowing contributors to manage only their own corporate policies. This model then becomes and administration nightmare for the team who has to manage all of this. This approach is also very error-prone. If you don't provide this level of security, ultimately someone will change another's corporate policy; causing a level of confusion and distrust.

The third problem with this approach is the amount of metadata that is managed for each corporate policy entry will increase; metadata columns for owning department and so on. Which is an unnecessary burden for the contributors; and also error-prone.

A Different (better): Store Information Close to the Point of Ownership

An approach, I use very often, is to store information (content) as close to the point of ownership as possible. This may sound like a crazy idea; let me explain the model, thought process and why it works so well...

I recommend, for operational business content, a site structure that closely resembles your organizational structure be used. This type of site structure can be used to solve the above problems; and ultimately begins to reduce the question "Where do I store/manage my content".

Users, who work in operational departments, typically understand some-level of organizational structure. They most certainly understand the department they work in. Directing them to a departmental site to perform their day-to-day work is an easy concept for them to understand. Performing their work in their departmental site can almost be second nature.

So, in their departmental site (and sub-sites where needed) provide them with the structured content place-holders (sites, lists and libraries) to manage all of their content. To summarize, an employee of the Human Resources Department will go to their Human Resources Departmental site (structure) on the Intranet to accomplish all of their day-to-day operational business content/document management.

Lets review how this implementation approach solves the problems listed above.

Users will still have the same amount of content to contribute and manage, regardless of where they do that work. However, providing them with a single point of entry for doing this work will ultimate be easier for them to navigate, use and manage.

The second problem above, security, becomes a moot point and is no longer an issue. Using this approach, we can set and manage security at a much higher (macro) level and not have have to deal with the headaches associated with item-level security. In essence, specific employees (roles) can be given permissions to manage their own content; feeling confident that no others in the organization can ever alter their work.

Now lets talk about metadata; aren't your users tired of managing all that metadata? Anything we can do to ease that burden, will improve your chances of the culture adopting your intranet solution. I know this may sound trival to you, but even the reduction of a single metadata column can improve ease of use, trustability and accuracy of content. In the model described above, it was necessary for the user to select an associated or owned department for each Corporate Policy; and this will grow as the number of repositories grow. In the model I recommend, this isn't necessary. The owning department is already implied in the site structure.

One question you may have might be "how do I produce the All Corporate Policies view for our consumers?"... Thats a great question! If you architect your information in such a manner so the content of type Corporate Policy is known, it is quite simple to query all corporate policies across the departmental sites where they are being managed.

Storing Information Grouped by Ownership

Conclusion

There are many approaches you can use to ease the pains associated with the storing and managing content. It is my hope the approach described above provides you with another option and tool for your bag of tricks!

Until next time...

SUGDC: Kick Off

Bob Mixon — Fri, 26 Jun 2009 08:21:05 PDT

The Washington DC Regional SharePoint Conference started off this morning by yours-truely delivering the keynote. How cool is that! I delivered a session on Enterprise Information Architecture and the SharePoint platform. Seems it went well, lots of great questions...

I had many people ask me for a copy of the presentation. I have made it available for download from our Mastering SharePoint community site.
http://masteringsharepoint.com/media/p/1253.aspx
You will need to register on the site before downloading; everything is free!

If you have any questions about the presentation or specific topics, please don't hesitate to contact me!

Colligo is Releasing Contributor v4.0 - Attend the Product Launch Webinar and Learn More!

Bob Mixon — Thu, 11 Jun 2009 01:59:00 PDT

My friends at Colligo are releasing Contributor v4.0; lots of great new features! If you are a Colligo fan as I am, attend this webinar and learn more about this exiciting product release...

Click the link to learn more and register!

https://www2.gotomeeting.com/register/716823802

/nsoftware - Bringing PowerShell to the Web, SharePoint, ASP.NET, ADO.NET, and more!

Bob Mixon — Mon, 01 Jun 2009 16:00:00 PDT

I received this e-mail and really think this is cool stuff.

Introducing PowerShellToys (www.powershelltoys.com), a new, independent product division of /n software specializing in providing extensions and enhancements to Windows PowerShell technologies!

Featuring cool ‘toys’ for PowerShell enthusiasts, the latest releases bridge the gap between PowerShell scripting and other Microsoft technologies, making PowerShell easily accessible to Web Developers, Desktop Application Developers, DBA’s, IT Administrators, and more.

Visit www.powershelltoys.com for more product details, or to download a free trial.

Check out the latest PowerShellToys Products:

· PowerShell ASP - http://www.powershelltoys.com/powershellasp.aspx

Build Dynamic Web Content with Windows PowerShell! PowerShellASP is an ASP-like template language for Web applications, templates consist of markup (HTML, XML, etc.) and inline PowerShell code.

· PowerShell WebPart [BETA] - http://www.powershelltoys.com/powershellwebpart.aspx

Generate Dynamic SharePoint Content with Windows PowerShell! PowerShellWebPart brings PowerShellASP to SharePoint Pages through a standard SharePoint Web Part.

· PowerShell RSS [BETA] - http://www.powershelltoys.com/powershellrss.aspx

Serve Dynamic RSS Feeds with Windows PowerShell! PowerShellRSS executes PowerShell scripts and easily formats the pipeline object result as an RSS feed.

· PowerShell ADO [BETA] - http://www.powershelltoys.com/powershellado.aspx

Windows PowerShell as a Database! PowerShellADO allows you to treat any PowerShell script as an ADO.NET data source, opening up entirely new possibilities for .NET developers.

· PowerShell Panel [BETA] - http://www.powershelltoys.com/powershellpanel.aspx

A PowerShell-Powered ASP.NET Panel Control! PowerShellPanel is an ASP.NET Control that enables you to include dynamic PowerShellASP in any ASP.NET web page, bringing live PowerShell content to ASP.NET.

Coming soon:

· PowerShell Adapter (BizTalk) …

· PowerShell Activity (SharePoint) …

· PowerShell SSIS (SQL Server) …

Are you a PowerShell Enthusiast? Take advantage of FREE community licensing for all PowerShellToys products for any projects that benefit the PowerShell community!

Your feedback is very important to us, and we are particularly interested in feedback and suggestions on this new release. If you have comments or questions, please email us at support@powershelltoys.com.

Myths about 2000-item Limits in Lists and Libraries

Bob Mixon — Mon, 01 Jun 2009 15:36:00 PDT

I have had many discussions and written about this topic in the past and still receive questions about it. Microsoft does recommend you not have any more than 2000 items in any single list or library; however, this can be overcome by using simple techniques. Lists and libraries are stored in SQL so there really isn't a 2000 item limitation from that perspective. The limitation really is around the user interface and API access techniques. One has to think, even if you could display 10,000 items in a browser UI quickly and efficiently, how useful would that be to a user? When I have encountered situations where there are large number of items in a list or library, the customization is at the UI level to improve the user experience. In these situations, you may want to consider a search, or filter, interface that returns a maximum of 200 (or so) items.

Chris Even recently write a blog post about this topic:

http://sharepointsearch.com/cs/blogs/notorioustech/archive/2009/04/08/best-practices-for-large-sharepoint-lists-and-documents-libraries.aspx

Quest Virtual Expo for SharePoint 2009

Bob Mixon — Mon, 01 Jun 2009 15:16:00 PDT

Wednesday June 10

8 a.m. to 4 p.m. EDT

http://www.quest.com/SPVirtualExpo09_MichaelNoel

During this free online event, you can interact with our SharePoint experts and partners to learn how best to migrate to -- and manage -- this essential collaboration platform. Join us for live webcasts on topics such as governance and recovery, and visit the booths to download white papers, gather product information or chat with a technology specialist. This event is accessible via any web-connected computer.

Live webcasts include:

· SharePoint Governance: 10 Steps to Successful Deployments (Joel Oleson; 10 a.m. EDT)

· Leveraging SharePoint and Performance Point as a Business Intelligence Platform (Tim Beamer, Dell; 11 a.m. EDT)

· Ask the Experts: Live SharePoint Q&A (Joel Oleson, Mike Watson, Michael Noel, and Bob Mixon; noon EDT)

· A Simple Game Plan to Master SharePoint Recovery (Doug Davis, Mike Watson; 1 p.m. EDT)

· Finally: A Pain-Free Way to Take Your SharePoint Sites to the Next Level (Doug Davis; 2 p.m. EDT)

· Maximize Your SharePoint Environment with NetApp Storage Solutions (Claude Steinmayer, NetApp; 3 p.m. EDT)

Plus, by attending you can:

· Enter to win prizes throughout the day including SharePoint books, gift cards and more!

· Interact with your peers and SharePoint experts in the "Networking Lounge"

· View on-demand webcasts and read white papers to learn more about your areas of interest, such as:

o Migration tools and best practices

o Administration and auditing

o Recovery from your existing backups

o Developing robust applications on SharePoint with no coding

o Managing SQL Server

Sponsored by Dell, ePlus, NetApp, Orangutech, PointBridge, SharePoint Reviews, TechRepublic and WindowsITPro.

SharePoint Conference Washington DC

Bob Mixon — Mon, 01 Jun 2009 14:54:00 PDT

I have been asked to deliver the keynote at the Washington DC Regional SharePoint Conference in June 26-27; what an honor this is. If you live in the DC area, or near, this looks like it is winding-up to be a great regional conference.

Hosted by the SharePoint User Group of Washington DC

Not only am I honored to be opening this conference as the keynote speaker, I will be speaking alongside top-notch industry experts. The lineup of speakers includes Brad Smith, Aaron Rafus, Gary Vaughan, Tony Lanni, Gary Blatt, Paul Galvin, Zach Wahl, Susan Hanley, Ron Simmons, Sahil Malik and many, many more. You can see the conference agenda here.

Conference Resources

My opening keynote will cover the following:

SharePoint Enterprise Architecture: Harnessing the Power of Microsoft SharePoint

Often referred to as the Swiss Army Knife of Portals, Microsoft Office SharePoint Server is the hottest and most powerful enterprise technology in the world today. However, harnessing this power and making it an effective part of day-to-day business operations can be a daunting task. It requires a careful balance of planning, governance, architecture, design and development to drive SharePoint throughout your business culture with increasing value. This presentation will focus on taxonomies, the role they play in find-ability, and provide you with some crucial keys to SharePoint implementation success!

Modifying Built-in Content Types in SharePoint

Bob Mixon — Sat, 30 May 2009 09:48:00 PDT

I received an interesting e-mail today; an individual asking me to site documentation indicating whether or not it was okay to change the built-in SharePoint Content Types. There was a second part to their question, I will get to that in a moment.

As for the first question, changing built-in SharePoint Content Types; such as the Item or Document Content Types. It is a best practice to not change any built-in Content Type or Metadata Column. Microsoft does reserve the right to overwrite these (or make updates to them) with service pack releases/updates.

I also feel it is a bad idea for a completely different reason. Consider modifying the built-in Document Content Type; adding a metadata column. I personally find it hard to believe that you will have any single metadata column that will be applied to all documents in your environment. Adding metadata columns such as Line of Business, Department, Classification, Keywords, etc. for all documents is a bad idea and I believe the result of a company not wishing to architect their information correctly. These types of base-document metadata columns are typically the result of either someone not understanding how to architect information/systems, don't understand what trustability, findability and ease of use really mean or a company who simply wants to get SharePoint installed/running quickly with little effort; or a combination of all the above.

Additional Reference Information:
• Plan Content Types (Microsoft Technet)

The second part of the question was about specifically adding a Classification metadata column to the base Document Content Type (discussed somewhat above). I wanted to elaborate a bit more on why I feel this is a bad idea. Lets assume the Classification metadata column is a multi-select list; allowing the user to select zero to many values. Following are the problems I feel you can have with this:

You will need to have someone update the metadata column each time the need arises. Or, set security so anyone who can store documents in that Site Collection can update it; which is a really bad idea because people think about classifications differently.
The list will likely grow so large:
1. From a user interface perspective, it will become unusable. The result will be to write custom code to overcome the user interface issues.
2. From a usability perspective, users will stop classifying their information correctly. Even if there is only 20 to 30 choices in the list, users won't want to look through this list and select the correct classifications every time they upload a document. This is a waste of their time.
3. Once users stop correctly classifying their documents; aggregation and search based on classification will become untrustworthy and eventually unusable.
Why put classification options in front of a user when they don't make sense within the context of their current document needs. For example, if you have a hierarchical classification of Products -> Special Widget, why even make that a selection when a user is uploading a corporate policy document; it doesn't make sense to do this.

The idea of a large classification list is quite unusable in most organizations. Even if this list is organized in a hierarchical manner, it can become large and unusable. This type of document classification may be needed for a subset of documents but I couldn't ever see using the same classification for all documents in an organization.

I'll expand this concept in a later article; but think about this… Store your content as close to the point of ownership as possible. This will solve many different problems you may be currently encountering with security, overuse of metadata and contributor confusion.

Speaking at the SharePoint Technology Conference 2009 - Boston (June 22-24)

Bob Mixon — Wed, 13 May 2009 23:14:00 PDT

I have been asked by BZ Media to, once again, speak at the next SharePoint Technology Conference; being held at the Hyatt Regency Cambridge (Boston) hotel this June 22 through 24.

Before I dive in to the topics I will be covering, I would like to thank BZ Media for this opportunity!

I will be delivering 3 sessions at this conference:

Monday, June 22, 8:30am - 5:00pm
Delivering Content to Users within the Scope and Context of their Needs
“Findability” describes the way information is made available to those who require it. Providing agility regarding the scope and context of information can be a monumental task. In this workshop, you will discover various ways of working with users to determine their specific needs and learn how to fulfill those needs using SharePoint. It’s all about agile information aggregation, dissemination and search—come see how to make it work.

Tuesday, June 23, 11:15am - 12:30pm
How SharePoint Search Services Work And How to Optimize Them
Microsoft Enterprise Search Services are very powerful. However, tuning these services to deliver relevant information to your users is a complex science and art. Join Bob in this session and discover configuring scopes, faceted (metadata) filtering, techniques for customizing the user interface, and how the Microsoft Enterprise Search Services work.

Wednesday, June 24, 10:30am - 11:45am
Why Taxonomies Are the Most Important Part of Document Management Systems, Part I
Structuring information in such a way that it lends itself to various Scope and Contextual needs can be a daunting task. Many SharePoint failures are the direct result of the implementation not taking Scope and Context into consideration. In this session, Bob will present a case that will help thoroughly understand why taxonomies are so important, teach you how to implement them in SharePoint, and how to get started in your environment. Join Bob and learn more about data, site, navigation, topical, functional and task-based taxonomies in SharePoint.

Wednesday, June 24, 12:45pm - 2:00pm
Why Taxonomies Are the Most Important Part of Document Management Systems, Part 2
A continuation of the above session on taxonomies!

For more information about this conference, please visit their web site.

If you haven't done so already, please register!

Mixon Consulting Seeking a Sr. Information Analyst

Bob Mixon — Thu, 07 May 2009 15:06:00 PDT

Job Duties

This is one of the more critical roles on the implementation project team. They assist in the development and maintenance of document management strategies and implementation programs for multiple customers. Collaborate with business units to formulate a process for effective content assessment. Select, refine or create a taxonomy framework that will take corporate structure and culture and instantiate it within distinct business units. This role assists in the process of refining corporate template with business-specific terminology while maintaining a tie to the corporate vocabulary. They participate in research and recommend tools and technology to aid in the administration of resulting repositories, integrating with line-of-business applications, and client-based tools for managing documents in the new controlled environment. This role is on a track to become an Enterprise Information Architect.

Functional Responsibilities:

Participates in developing taxonomies and thesauri for organizing information assets that enables enterprise search and compliance with corporate retention policies.
Establishes controlled business vocabularies.
Creates documentation for managing and maintaining taxonomies and associated thesauri.
Researches, evaluates, and recommends process improvements, including automated systems for knowledge capture, transformation, and presentation.
Implement technology framework for integrating document management functionality into traditional online applications.
Develops requirements for new content management tools and processes.

Job qualifications

Required Skills

Minimum of three (3) years experience in library science, information architecture, knowledge/content management, or related technical discipline.
Experience with developing and implementing strategies for business-specific taxonomy development and deployment.
Successful track record of integrating taxonomies with information systems.
Strong understanding of concepts, practices and trends in the areas of information architecture, digital asset management and library science.
Experience developing and managing business-specific, controlled vocabularies and metadata schemas for organizing information assets.
Understanding of advancements and developing trends in the library science
Strong organizational skills that support documenting, categorizing, and prioritizing requirements.
Strong problem solving and conceptual thinking abilities.
Hands on experience with best practice taxonomy and thesaurus automation software.
Able to work independently and deliver high quality results when given a set of objective requirements.
Outstanding written and verbal communication skills, both technical and business focused.

Preferred Skills

Experience implementing taxonomies in enterprise content management systems or portal solutions.
Experience with taxonomy and thesauri management software.
Experience with machine-aided indexing tools.

Education

Bachelor of Science degree in Information Science or related field or equivalent work experience required.

Additional Information

Typical Deliverables

Methodology and workflow for document staging
Documented current and desired states
Template for business unit transition plans

Additionally the analyst will be responsible for all daily tasks associated with creating, delivering and managing the above artifacts.

For more information email jobs@mixonconsulting.com or call 1-866-837-5323
and review www.mixonconsulting.com

SharePoint E-Mail Integration and E-Mail Archival Webinar: Q&A

Bob Mixon — Wed, 29 Apr 2009 23:19:00 PDT

As promised, following are my answers to the questions I received during the webinar today.

Colligo SharePoint E-Mail Integration and E-Mail Archiving Webinar

Questions and Answers

If you have a hierarchy of folders with email in each folder, can the whole hierarchy be transferred into SharePoint?

If you are referring to a hierarchy of folders in Outlook, I am not aware of a program that provides the ability to pick that structure up and moves it in to a SharePoint Discussion List or Library. However, I do believe it would be a fairly trivial task to write a small program that could accomplish this for you.

If you are referring to a hierarchy of folders on a drive, this can be accomplished by simply connecting to a Document Library in SharePoint with Windows File Explorer. Once connected, you can use normal drag-and-drop features to move those folders to SharePoint.

Create a mapped drive to SP library?

Yes! You can add a “Network Place” and/or map an unused drive to a SharePoint Document Library. WebDAV (web-based distributed authoring and versioning) is a technology used by Windows and SharePoint to communicate with each other. This is the technology used when Windows File Explorer is communicating with SharePoint.

The following article describes the process for creating a Network Place:

http://office.microsoft.com/en-us/sharepointtechnology/HA011544651033.aspx

Is SharePoint search is applicable on the attached email content in the document library?

Yes, SharePoint will search attachments.

Can we create custom workflow based on email on document library using metadata from and subject line...like Approved?

Absolutely! Now this depends on what workflow development tools you use; but most allow you to use metadata for conditional logic.

How does one create a document library in SharePoint with metadata columns such as sender, subject etc. so that people can sort on these columns within the document library? And is it possible in combination with the onsave metadata-prompt suppressed?

I answered this question on my blog in a separate post:

http://masteringsharepoint.com/blogs/bobmixon/archive/2009/04/30/sharepoint-e-mail-integration-how-do-i-support-from-sender-subject-as-metadata.aspx

We currently use Public Folders to store project information. Each project has its own. How easy is to move data from these public folders (for later getting rid of this feature MS no longer supports)?

There are a number of publically available 3^rd party products that can ease this process. If there isn’t too much e-mail too move, you would use Colligo Contributor; it’s a very inexpensive approach.

Is it possible to archive an email from Outlook into SharePoint and have it retain the 'Category' that it was assigned in Outlook?

Not that I am aware of.

Hi I have a selection of users who prefer using folders instead of metadata. Have tried to dissuade this practice; should we just leave them be or encourage use of metadata?

This really depends on the type of data, where it is being stored and how it is being used. I wrote an article back in November 2008 on this very topic. Instead of repeating its content here, you can read it online at:

http://www.endusersharepoint.com/?p=954

We are looking at moving exchange public folders to SharePoint. What is the best way to accomplish this? There are some third party products to do it: Quest, AvePoint, Tsunami. Any comments on the pros & cons of these products?

I have used all of these products for moving e-mail from Exchange to SharePoint and they all have their own approach, configuration, pros and cons. I recommend your specific requirements drive the product selection process and have each of them respond to those requirements specifically.

Will Colligo Contributor work and add custom metadata when a user sends an email to an email enabled SharePoint list. Our users have asked for that?

Absolutely, that is one of Colligo Contributor’s best features!

What kind of legal issues can come up by storing email in SharePoint? For example by storing email in SharePoint does that make SharePoint a legal discovery object?

SharePoint absolutely can be setup to manage files for legal discovery. SharePoint is a system that can manage the full lifecycle and control of documents; e-mail can be considered one of these controlled documents too.

Is there any limit while sending email to library?

There are limitations to the total size of the e-mail; including attachments. These limits can be set by your SharePoint administrator or can be reached with a timeout. However, it’s rarely a problem, typically e-mail attachments are limited to 1 to 3 meg in size and this won’t be a problem at all with SharePoint.

SharePoint E-Mail Integration: How Do I Support From, Sender, Subject as Metadata

Bob Mixon — Wed, 29 Apr 2009 22:15:00 PDT

This was a question posted as a result of the SharePoint E-Mail Integration and E-Mail Archiving (presented by Colligo) webinar I delivered today.

The attendee's question was:

"How do I create a document library in Sharepoint with metadata columns such as sender, subject etc. so that people can sort on these columns within the document library?
If I create a document library view with E-Mail From, E-Mail Sender, E-Mail Subject and E-Mail To in it."

This is a great question, and I get it often. This is not supported if you use the out-of-box SharePoint e-mail enabled Document Library approach. There are many ways to accomplish this; the most common approaches I see are to use an e-mail queue (workflow enabled Document Library) or Colligo Contributor. I don't say Colligo Contributor because that is who presented the webinar today; I say it because I use it every day for just these types of situations. If you want a more consistent, automated and scalable approach, I recommend using a SharePoint Document Library as a queue. Dropping e-mails in this library will trigger a workflow. The workflow can then categorize the e-mail, extract and set any metadata and so on.

Tips and Tricks: SharePoint E-Mail Integration and E-Mail Archival Webinar (presented by Colligo)

Bob Mixon — Wed, 29 Apr 2009 22:08:00 PDT

I wanted to thank everyone who attended the webinar today; it was amazing. We had over 1,600 attendees online which has to be one of my all-time highest attendee count.

I was only able to answer a couple of the questions online, but have been sent the majority of thise that were targeted to me. I will do my best to answer them all over the next couple of days or so.

The webinar was recorded, so if you would like to see it, it is now available online:
http://tinyurl.com/chln8a

Mixon Consulting, Inc. is seeking a Senior SharePoint Information and Solution Architect

Bob Mixon — Wed, 22 Apr 2009 22:54:00 PDT

Responsibilities Include

Candidates should have more than five years experience with the Microsoft Development platform as well as experience with Windows SharePoint Services (WSS) and Office SharePoint Server (MOSS). In addition to possessing a strong technical background, the individual must demonstrate strong communications, business analysis and leadership skills.

Required Experience

1. Microsoft Office SharePoint Server (MOSS) and Windows SharePoint Services (WSS) design, architecture and solution implementation experience.

2. Development of custom SharePoint solutions; including, but not limited to, Site Definitions, Web Parts, Provisioning Solutions, Feature/Solution Packages, etc.

3. Experience consulting with clients on the design and business value of portal solutions.

4. Experience working with customer’s internal business processes and developing detailed analysis of how to effectively deploy SharePoint throughout an enterprise environment.

5. Excellent consulting skills and the ability to work effectively with clients and team members; or alone when necessary.

6. Must be proficient in full development lifecycle processes; specifically those that relate to enterprise-class SharePoint implementations.

Job Location

The individual selected for this position will have the luxury of working from the comforts of their home office. However, travel to customer sites will be required.

Position Type

Full-time/Regular

Please contact Mixon Consulting to submit your resume or for more details.

http://www.MixonConsulting.com

About Mixon Consulting, Inc.

Mixon Consulting, Inc. is a full-service SharePoint focused consultancy that has a proven methodology to optimize the power and flexibility of SharePoint solutions in the Enterprise.

We are the original Live Online Training Company with classes in Branding, Information Architecture and Design as well as InfoPath / SharePoint Designer Workflow.

With an emphasis on Planning, Information Architecture and Design, our consultants ensure that implementation team members confidently choose the right SharePoint components to match business needs and execute in a manner that promotes adoption.

With hundreds of clients in the US, Canada and the UK, Mixon Consulting has provided solutions in many industries from onsite education to custom integration services and everything in between. If you want it done right the first time, Mixon Consulting is your partner of choice.

Tips and Tricks for E-Mail Archiving with SharePoint

Bob Mixon — Wed, 22 Apr 2009 22:42:00 PDT

I have been asked to deliver a free webinar with Colligo and Symantec to help you better understand ways of integrating e-mail with SharePoint and archiving techniques.

The webinar will be delivered on Wednesday, April 29th, 2009 at 11am (EDT).

Register Now!

Summary Description of Webinar
As more organizations adopt SharePoint to manage emails and documents, understanding the architectural choices and developing best practices for archiving this content are becoming increasingly important. Factors such as findability of emails and attachments, compliance with eDiscovery and legal hold requirements, storage costs and end-user adoption make choosing the right SharePoint email archiving solution a critical part of an organization’s knowledge management strategy.

Join Bob Mixon, Microsoft SharePoint MVP and principal of Mixon Consulting and David Scott, Group Product Manager at Symantec in this important webinar designed to provide practical information and real world examples of how to implement an efficient and cost effective email archiving strategy with SharePoint.

In this webinar, you will learn:

If you are a CIO, CKO, IT Manager or SharePoint Administrator responsible for ensuring your email archiving strategy meets your organizations needs - register today!