|
|
|
|
|
|
|
|
|
|
|
|
|
|
BUSINESS PARTNERS SPEAK OUT
If I ruled Lotus…
By Jeffrey R. Burrows
Like me, you'll need your IT systems to be oriented around the business of your clients. Presently, Domino is database-oriented, not data oriented. That might seem a slight distinction, but it isn't when your clients want to see data from multiple databases in the same views, and can't understand the technical limitations that currently make this nearly impossible. And from a designer's perspective, I don't like to duplicate the same documents across databases to work around that database-centricity.
Time for a revolution In my opinion, Domino requires a structural revolution, turning folders and views from being internal components of databases to being situated above databases. For simple systems, the database as container is sufficient. However, for both enterprise systems and the enmeshing of small systems into an integrated intranet, this approach is limited. Users don't care about databases, they see views and folders. Lotus has already achieved this with search, supplementing the existing internal database search function with the server-wide Site Search database.
The structure of the databases themselves must be a purely technical matter, to be optimized by an experienced designer or administrator but transparent to the ordinary business users, like the tablespaces of Oracle. Folders within Notes, at present, are simply a collection of document IDs. Extending this to be full IDs (i.e. replica ID + document ID) or even URLs is technically evolutionary but radical for usability.
Directory direction Another area where database integration is lacking is the Domino Directory. Other vendors (such as Microsoft with Active Directory and Novell with NDS) are developing large, hierarchic directories that contain everything. However, Domino persists in having the handling of its objects split between a Public Address Book (servers, users, domains, users' mail files and mail-in databases), Catalog (all databases except where manually excluded) and Library (manually included---published--databases). Some move in the right direction has been made with R5, where database catalogs become key and not an option for a methodical administrator. This needs to go further, so that there is a consistent manner of addressing any object on a Notes network, and also to shift from server-centric networks to a single, smooth network of objects, which is one of the main functions of a global directory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
Find unused Lotus Notes groups and clean up your address book
Have you ever wanted to get rid of old Lotus Notes groups that were cluttering up your address book, but you weren't sure if they were used? Find Unused Groups can help.
Find Unused Groups will check your ACL, mail, multi purpose and server groups to help you determine if they are used, and who uses them.
Learn how to easily clean up your address book. |
-- Advertisement --
Teamstudio Edition 25 has shipped
It's finally here! Now that Teamstudio Edition 25 has shipped, listen to our latest Tool Time audio program to find out what's changed. Updates to all your favorite Teamstudio tools will be discussed.
Plus, you'll get an introduction to Teamstudio Undo (formerly known as Teamstudio Snapper).
Tap here to get started! |
|
|
|
|
|
|
|
|
|
|