Connecting Twitter to Jaiku
Monthly Archives: September 2007
A different view on Apple
If you are an Apple fan like me, you will not enjoy reading this article:
http://www.pcworld.com/article/id,136949-c,companynews/article.html
On the other hand, it will make you think about the way large companies are doing business. Is Apple really “Thinking different“?
Custom 404 error page in SharePoint
Last week, I was looking for some info on our portal. I used a bookmark that I created, to quickly access the team site I was looking for, but all I got was: 404 file not found. Afterwards, I found out that somebody reorganised the portal and moved the site to another URL.
Two reflections on this:
- Should you really delete sites in a SharePoint portal? Should you not at least leave a web part page with a message that the information moved to another location?
This is a common practice in web content management (redirect pages, even better!), why not in a SharePoint portal? - Is there a way to have a “friendly” 404 error page? I found out there is a way to have custom error pages, but it is not a very easy procedure to perform, as it even involves some Visual Studio: http://support.microsoft.com/kb/941329
If you are looking for inspiration on what should be on your custom error page, have a look at http://www.theinternetdigest.net/archive/custom-error-pages.html
Content Types – end user experience
I tried to figure out on our portal how the Content Types and their corresponding templates behave, when using Office 2003 and Office 2007. There are 2 main factors that determine the behaviour when a user selects a content type from the “New” button in a document library: the file format of the template and the version of the Office client:
| File format: 2003 | File format: 2007 | |
| Client: Office 2003 | - client app opens with document based on template- user saves the document- user needs to select the correct content type- user needs to fill in the correct metadata | - not supported |
| Client: Office 2007 | - client app opens new document based on template- user saves the document- user needs to select the correct content type- user needs to fill in the correct metadata via the document information panel, if metadata is required. Otherwise: NO metadata!(*) | - client app opens new document based on template- document information pannel shows metadata immediately after opening the document- user can fill in metadata in dip and save the doc in one move |
(*) You can optimise this via the document information panel settings of the content type: check Always show Document Information Panel on document open and initial save for this content type.
Conclusion is that the user experience is only optimal when using Office 2007 with templates in the Office 2007 format (or what did you expect…)
Note: Interesting to know that the “Content type” is stored IN the properties of a document template file. If you use a document template file with such information as a template for an OTHER content type, things get very confusing, as MOSS will still prompt you for the metadata attached to the OLD content type!