Comments on: How we did it: Tag driven Information Architecture using MOSS http://www.sharepointconfig.com/2008/01/how-we-did-it-tag-driven-information-architecture-using-moss/ Ari Bakker's thoughts on customising and configuring SharePoint 2007 and 2010 Fri, 27 Aug 2010 20:13:14 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: David Potter http://www.sharepointconfig.com/2008/01/how-we-did-it-tag-driven-information-architecture-using-moss/comment-page-1/#comment-167 David Potter Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=46#comment-167 Your article has been life-changing for me. I was headed down this line of thinking and now have built an interface along the same lines as expressed in your article. At last, out of tree-heirarchy driven menu systems. At last, discoverability for users is a reality. I have added one more element. I set up a search scope on the relevant library and added a Search box web part/ search results page to the system to allow users both the Browse/filter mechanism and Search. Thanks for the inspiration. Your article has been life-changing for me. I was headed down this line of thinking and now have built an interface along the same lines as expressed in your article. At last, out of tree-heirarchy driven menu systems. At last, discoverability for users is a reality. I have added one more element. I set up a search scope on the relevant library and added a Search box web part/ search results page to the system to allow users both the Browse/filter mechanism and Search.

Thanks for the inspiration.

]]> By: Ari Bakker http://www.sharepointconfig.com/2008/01/how-we-did-it-tag-driven-information-architecture-using-moss/comment-page-1/#comment-168 Ari Bakker Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=46#comment-168 The filtered view of the content shown in the "Tag based navigation" section is a standard document library view web-part, with filters applied. This does not aggregate content from other libraries in the site, but draws data from a single document library within the "Tools and Resources" site. Other sites have similar filtered views of documents, and searching is used to find data across all the sites within the intranet. The filtered view of the content shown in the "Tag based navigation" section is a standard document library view web-part, with filters applied. This does not aggregate content from other libraries in the site, but draws data from a single document library within the "Tools and Resources" site. Other sites have similar filtered views of documents, and searching is used to find data across all the sites within the intranet.

]]> By: Dmitriy http://www.sharepointconfig.com/2008/01/how-we-did-it-tag-driven-information-architecture-using-moss/comment-page-1/#comment-169 Dmitriy Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=46#comment-169 Thank you for the insightful article! I was wondering, how did you implement the filtered view of the content in the site (shown on screenshot in "Tag based navigation")? It looks like a document library view web-part, but AFAIK you cannot aggregate content from different libraries with one of those. Is all site data stored in a single library? Thank you for the insightful article!
I was wondering, how did you implement the filtered view of the content in the site (shown on screenshot in "Tag based navigation")? It looks like a document library view web-part, but AFAIK you cannot aggregate content from different libraries with one of those. Is all site data stored in a single library?

]]> By: Kevin http://www.sharepointconfig.com/2008/01/how-we-did-it-tag-driven-information-architecture-using-moss/comment-page-1/#comment-170 Kevin Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=46#comment-170 Great work! I've been pushing metadata based site listings, but you've taken it even further to be tag based on EVERYTHING. Great work! I've been pushing metadata based site listings, but you've taken it even further to be tag based on EVERYTHING.

]]>