http://jopx.blogspot.com/2010/03/folksonomy-and-taxonomy-do-you-have-to.html

http://community.zevenseas.com/Blogs/Robin/Lists/Posts/ViewPost.aspx?ID=114
http://stsadm.blogspot.com/2007/09/more-site-navigation-settings-commands.html

http://sharepoint.mindsharpblogs.com/Bill/archive/2009/10/08/What-Does-It-Take-to-Implement-a-Company%5Bdash%5DWide-Taxonomy%5Bques%5D.aspx

http://www.itconsult.it/sala_stampa/eventi/det.asp?ID=75

http://www.cmswatch.com/Trends/1219-Thoughts-on-SharePoint-and-Fast-Search

http://blogs.msdn.com/gregmcb/archive/2008/03/05/think-about-your-sharepoint-taxonomy-before-deployment.aspx

http://blogs.msdn.com/opal/archive/2008/02/17/next-steps-of-sharepoint-search-enhancement-and.aspx

http://blogs.msdn.com/opal/archive/2008/01/23/faceted-search-2-0-for-sharepoint-search-server.aspx

http://blogs.msdn.com/sharepoint/archive/2008/01/30/open-source-faceted-search-for-moss-2007-and-microsoft-search-server-2008-part-1-of-2.aspx

http://blogs.msdn.com/enterprisesearch/archive/2007/11/24/how-to-enable-faceted-search-in-search-server-2008-and-sharepoint-server-2007-search.aspx

http://blogs.msdn.com/sharepoint/archive/2008/01/30/open-source-faceted-search-for-moss-2007-and-microsoft-search-server-2008-part-1-of-2.aspx

Allows you to retrive all changes form a site ... would be nice to put this as a RSS feed ;-)

http://www.lamontharringtonsblog.com/2007/10/27/SharePointObjectModelHiddenGems.aspx

Autonomy to supply IDOL software for Microsoft's SharePoint Server 2007

http://blogs.msdn.com/sharepoint/archive/2007/01/22/taxonomy-tagging-starter-kit-for-sharepoint-server.aspx

As Web 2.0 could mean chaos determined by consumers disseminating content without limits, an Intranet will need some form of control over users and content, therefore will be somewhat Web 1.5 - 1.75.

Sharepoint gives the right balance of user control (with security, policies, logging, auditing etc etc), business processes (workflow), but also allows users to create new sites, subsites and content(docs, wiki, blogs) so to create no impediment. Therefore I believe the way to Web 2.0 for Sharepoint 2007 it is one of "software configuration" rather the software capabilities.

What is still missing in Sharepoint ? -

Time - Tracking - to do PSA: (Professional Services Automation) - time tracking, billing .... even a basic object would be fine -

Posts on Time Tracking for Sharepoint

http://thorprojects.com/blog/archive/2005/10/13/240.aspx
http://www.andrewdothay.net/default,month,2005-08.aspx

Org Chart Wizard: most customers don't know how to structure a Sharepoint installation, most often they don' t have all the needed info in Active Directory. Therefore having some sort of wizard to create an org chart - will all business units, departments and "workgrups" which generates a structure within MOSS would be ideal, especially when done and validated by a HR person

Anything else?

Sharepoint Taxonomy

Sharepoint offers a duplex solution for companies: IT both allows flexibility in users interacting on collaboration and content creation(like blogs, wikis), but also imposes policies to take care of content(classification with content types, RM, auditing, security).

Il post seguente rispecchiano le mie personali esperienze con Sharepoint, di quello che puo' fare e di quello che fa meglio. Dunque, Sharepoint puo' essere utile in quasi tutto, tranne che essere il repository di file "inutili" alla knowledge aziendale. Esempi sono i file enormi di decine o centinaia di MB di musica (MP3) e video, file di log, immagini ISO e simili dove la conoscenza rinchiusa ha bassa importanza aziendale e che non conviene immettere in un database.

http://blogs.msdn.com/joelo/archive/2007/01/12/file-servers-and-sharepoint-doc-libraries-tough-questions.aspx

Sharepoint 2007 rispetto alla versione Sharepoint 2003  e' piu' facilmente customizzabile, avendo frallaltro anche rilasciato il codice di ASPMenu, il menu controllo di navigazione di WSS-MOSS 2007.

Decatec propone un area navigation menu web part per Sharepoint Portal Server 2003

http://www.graphicalwonder.com/?p=627
http://www.sharepointblogs.com/helloitsliam/archive/2006/08/30/11723.aspx
http://www.graphicalwonder.com/?p=393
http://blogs.msdn.com/sharepoint/archive/2006/12/02/customizing-the-wss-3-0-moss-2007-menu-control.aspx
http://weblogs.asp.net/soever/archive/2006/07/24/SharePoint-2007-navigation-_2D00_-part-2.aspx
http://weblog.vb-tech.com/nick/archive/2006/12/11/1987.aspx
http://blogs.msdn.com/ecm/archive/2006/12/02/customizing-the-wss-3-0-moss-2007-menu-control-mossmenu-source-code-released.aspx

Alcuni posts sull' argomento fileserver vs Sharepoint:

http://www.mikeysgblog.com/Lists/Posts/Post.aspx?ID=573
http://blogs.msdn.com/sharepoint/archive/2007/01/02/is-the-file-server-dead.aspx

Sharepoint is such as useful tool, every company should install it to keep a tab on all the content floating around. Where is the pooper?

As ggod as Sharepoint is in itself it lacks some sort of configuration wizard to set up a company with as little effort as possible: So what should such a wizard do?

Create a Taxonomy, ie. organize things along company hierarchies, business units, departments, teams and cross working groups.

Wizard Steps:

Create Business Units sites

Create Departments sites

Create (Project) Team Sites within Departments/BU

Create Cross Company Teams/Working Groups

With such a simple (Web based Wizard) the setup would be a breeze and organizations deploying it would be most confortable.