The first example is about a database that allows users to enter a course title, referred to as Catalog Names into a Louts Notes database (Learning). However, as real life experiences show, having many users causes duplication of course titles.  This is the intent of the change. this short story is the tale of the Replication Gremlin as it recks havoc with Catalog Names.

Remeber that for this type of change, the timeliness of the process is not based on the human element, but the configuration and location of the participants relative to the Notes server that the approver is working on or from (Notes database locations).