IdeaJam(tm) feed for Dietmar Dumke

Domino Designer / : Better control over what gets displayed as possible values for Names fields

Mon, 03 Mar 2008 23:10:30 +0000

Author: Dietmar Dumke
Tags: Form Design
Idea:

To avoid user errors, give form designers control what types of addressbook entries will be selectable for a given Names/Readers/Authors field. E.g. to define that for a SendTo field should appear only entries which are mailable; in a field which controls document access should appear only entries which can control access.

re: Better control over what gets displayed as possible values for Names fields

Tue, 04 Mar 2008 05:01:06 +0000

Author: Rob Goudvis
Comment: This would imply that there will be other fieldtypes, like Servers or Groups

re: Better control over what gets displayed as possible values for Names fields

Tue, 04 Mar 2008 12:59:57 +0000

Author: Dietmar Dumke
Comment: Rob, I think no new field types are necessary. The field setting could apply as a filter to the dialog which appears after pressing the addressbook field helper button. Also, there already could be some hidden views in the directory, e.g. already filtering mailable respectively access controlling entries. Dependent from the field setting the field helper button displays the content from the one view or the other).
You already have some control over what should happen when pressing the button (e.g. displaying a custom view instead of the default addressbook view). But to implement this you had to build yourself some custom views into the directory. I believe this better could be out-of-the-box functionality. The goal is that there should appear only entries in the dialog which really are valid choices in the given field context.

Sametime / Administration: Make Sametime server work with Internet Site configuration documents

Fri, 07 Mar 2008 12:29:42 +0000

Author: Dietmar Dumke
Tags: sso
Idea:

Currently, Sametime is supported on Domino web server only in Web Configuration mode, not in Internet Site Documents mode. Because the LTPA Token documents for each mode are different, there is no SSO when you change the browser from an Internet Site controlled Domino web server to the Sametime server. You will have to reauthenticate. Server- to-server SSO would work if Sametime web server also could be configured to use Internet Site documents.

-- withdrawn because contained in another already existing idea in the Quickr idea space --

re: Make Sametime server work with Internet Site configuration documents

Fri, 07 Mar 2008 14:04:32 +0000

Author: Bruce Elgort
Comment: Dietmar - As Carl noted there is already an existing idea. May I suggest that you withdraw this idea by changing the status to "Withdrawn". Let me know if you have any questions.

re: Make Sametime server work with Internet Site configuration documents

Fri, 07 Mar 2008 13:31:01 +0000

Author: Carl Tyler
Comment: Existing idea:
{ Link }

Notes Client / Other: Ability to add custom search engines to Notes 8 search provider

Fri, 29 Aug 2008 10:39:44 +0000

Author: Dietmar Dumke
Tags: Advanced Search
Idea:

Make the Eclipse/Notes search provider work like in Firefox.

Notes Client / Other: Create view links by drag & drop

Fri, 13 Jun 2008 14:30:52 +0000

Author: Dietmar Dumke
Tags: client usability enhancement
Idea:

I can create a doc link by drag&dropping an opened document tab into a document's richtext field.

I can create a database link by drag&dropping an opened database tab into a document's richtext field.

However, I cannot create a view link that way. I'm limited to use the options in the Edit menu to create view links.

This I would call an inconsistent usability.

When dragging and dropping a database tab into a richtext field using the _left_ mouse button, when releasing the mouse button the client could insert a database link (default action).

When dragging and dropping a database tab into a richtext field using the _right_ mouse button, when releasing the mouse button the client could ask me whether I want to insert a database link, or a link to the view.

This behaviour would be almost similar to file dragging in common OS file managers.

Domino Server / Data Storage and Management: Catalog task should intercept database creations/deletions in realtime

Thu, 06 Nov 2008 14:10:33 +0000

Author: Dietmar Dumke
Tags: doclink catalog
Idea:

If you create a new database with replicas on other locations servers, and publish the new database by sending a doclink to the users at the same day, the doc/database link will always try to open the replica on the server the doclink was created from. This is because at this time does not yet exist database catalog entries for that new database. For that reason, the notes clients are not able to locate the "best" replica from the database catalog, and will try to open the new database from the "server hint" in the link which in many (most?) cases is not desired.

Solution: In addition to the usual nightly scheduled run, catalog task should also be resident in memory. This way, the catalog task could intercept database creation/deletion events, and (almost) immediately create/remove database catalog entries for the newly created database replica in the local catalog (or perhaps via AdminP).

Because now the catalog entries exist everywhere almost immediately after creation, db/doclinks sent at the same day always would open the "best" replica for a Notes client regardless of its location.

Sametime / Contact Management: Use 3:2 aspect ratio for person photos in business cards

Tue, 01 Sep 2009 14:54:33 +0000

Author: Dietmar Dumke
Tags: businesscard sametime
Idea:

Currently, the optimal photo aspect ratio the Sametime business card requires is 1:1. In most cases, this already results in unused space top and below the photo in the business card.

Moreover, the 1:1 aspect ratio is very uncommon for such (passport-like) photos. 15:10 (=3:2) is more common. To convert an existing 3:2 digital photo to the aspect ratio and max. size Sametime expects one needs to cut an 1:1 frame from the existing photo and add that to the person record in the directory, worst case one photo by one by hand. Considering all the person photos of a usual company, this is a very time consuming job.

Of course, you simply could add 3:2 aspect ratio photos, but this will result in wasting even more space (another third) because Sametime then adds even more unused space left and right of the photo to keep its aspect ratio intact. The final result is a business card with a very small photo which makes it unnecessary difficult to identify the person on it (yes I know one could hover over), along with much unused space left, right top and bottom of it.

If the optimal aspect ratio would be 3:2, one could automatically batch-convert many existing photos to the correct size in a single shot through usual freeware tools which potentially frees much time for less boring work.

re: Use 3:2 aspect ratio for person photos in business cards

Mon, 07 Sep 2009 12:31:38 +0000

Author: Dirk Stelloh
Comment: afaik the 1:1 format is very common in the web...

re: Catalog task should intercept database creations/deletions in realtime

Fri, 23 Oct 2009 13:04:21 +0000

Author: Bruce Lill
Comment: Thats why as an Admin, I always plan ahead. Emails get sent after the environment is configured.

I launch the catalog task on each server to force an update early if needed.

Running in real time would have an impact on performance while only giving marginal improvement in functionality.

re: Catalog task should intercept database creations/deletions in realtime

Fri, 23 Oct 2009 13:29:09 +0000

Author: Dietmar Dumke
Comment: Launching catalog task on each replica server just to add a single new database to the catalogs is not only boring admin work but also has an unnecessary load overhead on the servers, especially on servers with many databases.
"Plan ahead" means being forced to unnecessarily split a single task into 2 tasks, to be processed at different days. Day 1: Initiate replica creation, set a reminder for the next day. Day 2: Send a link message to the users notifying them.
I want to create replicas and then almost immediately send notifications to users. Not one day later, or - if almost immediately but after forcing catalog to run - for the cost of unnecessary server load.
The in-memory catalog task would hook into database creation events only, nothing else. That should not - if at all - impact performance so much.

re: Catalog task should intercept database creations/deletions in realtime

Fri, 14 Jan 2011 05:11:16 +0000

Author: Ralph Borcherds
Comment: In large installations this is not a possible. Way to much overhead and replication.