Following on the theme of common sense, I’d like to provide some additional guidance and best practices around jumpstarting your SharePoint governance.
“How many content types should you have?” This is the question that came up in a conference call on SharePoint architecture.
Guest Author: Marc D. Anderson
http://mdasblog.wordpress.com
So I’ve been going on about how wonderful this jQuery Library for SharePoint Web Services stuff is, but you may have wondered if I ever actually use the library in real world situations. You bet I do, and it lets me build some pretty nice solutions [...]
In this article I’ll describe some of the ways that SharePoint can reduce the effort to create, manage and retrieve documents and increase their value, as smart documents, to both your firm and its clients.
SharePoint Saturday: The Challenge of Unstructured Content, Concepts and Terminologies, Taxonomy and ECM Adoption Techniques, Why should Taxonomy matter to me
A common topic that is asked about in SharePoint, is how to roll up information from sub-sites to a top level site, and just generally how to show data from one site on another site. There are different methods and 3rd party tools that can be used, but here is a simple way to create a roll-up, that you can do yourself, using the data view web part, and a tiny bit of code. I’m not a developer, I swear! In this 5 minute screencast, I’ll show you the fundamentals behind creating your own rollup.
What goes into a Document Workshop? Well, the first thing would be the raw materials. In the case of documents, that would be templates. Sure, you can tie templates to Content Types but that might be overkill – this is a workshop, not an assembly line. I like attaching templates to a Custom List item that explains the purpose of the template. The other thing we might put in that list is instructions to help a new person create this type of document. Then we put up a list of contacts but not just the people on the project team; we include the people the team might need to reach out to for advice and help. We are also finding that interactive parts like discussions and wikis are useful for exploring ideas and developing content.
What goes into a Document Workshop? Well, the first thing would be the raw materials. In the case of documents, that would be templates. Sure, you can tie templates to Content Types but that might be overkill – this is a workshop, not an assembly line. I like attaching templates to a Custom List item that explains the purpose of the template. The other thing we might put in that list is instructions to help a new person create this type of document. Then we put up a list of contacts but not just the people on the project team; we include the people the team might need to reach out to for advice and help. We are also finding that interactive parts like discussions and wikis are useful for exploring ideas and developing content.
I describe a problem whereby document libraries having multiple content types use the default content type when documents are saved regardless of the selected content type.
This is yet another blog post on comparing dates in XSL in a data view web part.
