Showtime
My Blackberry Enterprise Server Push Utility for the Lotus Notes Client, allows you to create Jobs for individual Channel, Message, and Browser Content Pushes, as well as allows you to delete Pushed Channel Icons from defined recipient devices.
Contact Information
Blogger, podcaster, writer, and geek Chris Toohey covers topics from application development to the latest must-have-gadgets.
dominoGuru.com on Facebook
Latest Updates
Products & Applications
Time Tracker
The idea is simple. At the start of your day - upon completion of your first task - create an entry highlighting what you did and whether you feel it was an efficient or inefficient use of your time. Based on several requests, you can also select the priority, apply categories, or even align your time against a project.
For Lotus Notes Client v8.0 and above, you can use the Time Tracker Widget to make this process even easier!
Zephyr
My Configuration-based Rich Text Mail Merge and Emailing Utility, Zephyr allows you to create rich, data-driven emails to support automated workflow - all via Microsoft Word Mail Merge-like architecture. Dear <firstname> allows you to personalize each email message not only to the individual recipient, but also to the individual application workflow event!
xCopy
xCopy is a simple configurable xCopy client for the Lotus Notes client. By creating and defining xCopy Profiles, you can batch process your file backup or remote upload jobs. With the addition of the xCopy sidebar widget, you can easily kick-off these jobs, and modify both the xCopy Profiles and xCopy itself.
Community & Resources
Lotus Technical Information & Education Community
The Lotus Technical Information & Education community is comprised of IBM, business partner, and customer subject matter experts who use product wikis, published articles, white papers, community blogs and the latest in social media to build and share high quality technical content.
OpenNTF.org - Open Source Community for Lotus Notes Domino
OpenNTF is devoted to enabling groups of individuals all over the world to collaborate on IBM Lotus Notes/Domino applications and release them as open source.
developerWorks Lotus : Wikis
Share your deployment experiences and best practices in our wikis and help IBM to create scenarios for successful deployments. Contribute to the community by collaborating on shared content and leverage the shared knowledge from that community.
CMS: do I ask for a PRE/POST Body for each renderkit?
06/28/2009 08:33:16 PM by Chris Toohey
One of the projects that I'm working on requires the creation of a Lotus Notes Domino-based content management system. With this Lotus Notes Domino CMS, I plan on not only running the two project websites in question but also this site (www.dominoguru.com). All sites require some basic content management with a mind to incremental updates once the website "design" is finalized.
It's with that in mind that I'm using (what I'm referring to as) renderkits for the markup blocks within the application.
There are 2 main types of actual content NotesDocuments in my CMS at this time: documents and events.
Each of these NotesDocument types contain actual data, while the other types of NotesDocuments simply tell the CMS what to do with the data.
content NotesDocuments are used to create static blocks of content - such as the inclusion of Google Friend Connect or the PlanetLotus.org Blog Widget, which will be unique-keyed and can be used throughout the website.
The renderkits allow you to define a unique key, selection criteria, formula template, and count attributes - all of which will be used to create evaluated subsets of documents and events content markup.
An Agent runs against all active renderkits, using the search criteria to grab a NotesDocumentCollection against the CMS, and - using the Formula as a "template", does a simple Mail Merge-like meld of the NotesDocumentCollection content into the desired format... which is then saved en masse into the Body NotesItem for that given renderkit.
Pretty standard stuff as far as a CMS goes... but I had a simple question: should I allow for the definition of pre and post Body NotesItems in the renderkit; allowing the prefix and suffixing of content in the Body NotesItem?
My knee-jerk reaction was sure, why not!... but the more and more I think about it I'm not too sure.
See, for the intended usage scenarios, I will be using a Page NotesDocument to marry the content and the renderkit into the intended delivered content. I can define prefix and suffix information in the page as needed without worry.
Of course I imagine that there's no harm in adding it really... but that's where I turn to you:
And feel free to give your thoughts beyond the poll in the comments of this post (and thanks!).
|
Unless otherwise stated, this work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License. |
The pre/post are useful for people who don't have control over the content, only the look & feel. I don't think it's needed here.