A fair amount of work goes into the role of a SharePoint Information Architect. And every architect should have his tools, right? What does Microsoft provide out of the box, to design, deploy and manage an information architecture in SharePoint? Let’s have a look.
Enter the SharePoint IA
No matter how you get started, an IA from scratch or a modification of something already existing, the role of the Information Architect is a challenging one. And that means you need a knowledgeable SharePoint IA helping you out. Yes, you still need your Business Architect who understands how the business needs to work, but you also need that SharePoint knowledge to help you figure out how to make it fit.
A SharePoint IA is going to help you identify things such as:
- Site collections and site structure
- Content modeling and content types
- Metadata and taxonomy development
- Search integration
A SharePoint IA will document the existing structure, and map it to a new SharePoint 2010 structure. Then he will manage that structure ongoing. Now there’s a fair amount of documenting happening there -- documenting existing structures from either your SharePoint 2003 or SharePoint 2007 implementation, or from another source (like your file share). And when it comes to documenting anything, the quicker you can do it, the better. Keeping that documentation up to date is just as important. All this means is a SharePoint IA needs some tools. Unfortunately Microsoft hasn’t yet delivered an IA toolkit.
Defining IA in SharePoint: Mostly a Manual Process
For the most part, if you want to document your SharePoint implementation you are looking at a very manual, time consuming process. You can use Microsoft Visio to create your design documents, which is fine if you want to maintain a static view of your SharePoint environment. Visio is primarily used to create workflows for SharePoint, which makes it a great companion tool for SharePoint developers. You could also leverage SharePoint Designer to develop and implement content types and workflows. Designer is a great tool for non-technical power users to build sites, composite apps.
In neither case, however, can you get a high level view of your environment and how everything fits together. In addition, neither product provides the ability to make changes to the SharePoint environment that not only add new content types, workflows and information policies changes, but also move your existing content around to the new structure and clean out the ones you no longer want/need.
To give you an example of how manual the Information Architecture process will be without a third party toolset, let’s examine how we would document content types and metadata.
Documenting Your Content Types in SharePoint
If you want to know what your content types are in your current SharePoint implementation, then you have a manual task ahead of you. This task requires that you manually click through every site collection and site you have to document the content types and their columns. As you document, you get a picture of the relationship between existing content types and the overlapping of columns (metadata) between collections and site.
Here are the basic steps:
Select your site and go to Site Actions, Site Settings.
In the Galleries section, select Site Content Types (below we show a subset of existing content types):
To view all the details of the content type, simply click on it. In the view below, you see a list of the content columns used for that content type. But you aren’t finished yet. You need to know if that content type was created from scratch or selected from a list of existing content types -- you are trying to map the current structure right?
So you have to click on each column in the list.
Depending on whether it’s a custom one you created for this content type or one you inherited from an existing content type column, you get two different views:
A defined column
A custom created column
Congratulations, you have documented your first content type. Now go do that for every content type you have in this site. Then go to the next site and do the same thing. Don’t stop until you have it all documented. Once it’s documented, put it into a visual that makes it easier to see the relationships between content types and associated columns. Visio would work here. Note that you’ll also need to document any associated workflows, templates used and information policies applied.
But Wait, Your IA Isn’t Done Yet
What you have done so far is document your existing information architecture (again assuming you are currently using some version of SharePoint). Now you need to map it to a new, improved IA that works with SharePoint 2010. This includes identifying collection level content types that can be used throughout different sites, defining standard metadata to use in your content type columns, and more.
What tool does Microsoft provide to do redesign your structure quickly and easily? Again you could use Visio here. But keep in mind it’s a read only design. Once you finalize it, then it needs to actually be implemented in the SharePoint environment -- again, another manual process that can be tedious and take a lot of time.
And then what happens if you implement this new information architecture and need to change it? Well, you’ll have to look at all your existing IA documents, note where all the appropriate changes need to be made (and in what order), update the documentation and then head over to SharePoint to implement the changes.
The Ideal SharePoint Information Architecture Tool
I’m tired just writing that process.
A SharePoint Information Architect has better things to do then spend his time doing manual tasks that, with the right tool, he wouldn’t have to do. Here we are talking quickly document and visualize the existing environment in real-time, make any changes necessary and automatically have the SharePoint 2010 environment updated and content migrated over. And when a change needs to happen, just open up that living documentation, make the required changes and tell the tool to implement them -- no manual SharePoint task required.
Now that’s the tool I would want as a SharePoint IA. Wouldn’t you?
Editor's Note: You may also be interested in reading: