Cross Repository Notification

Showing results for 
Search instead for 
Did you mean: 

Cross Repository Notification

0 0 1,088

Obsolete Pages{{Obsolete}}

The official documentation is at:

Cross Repository Concepts


This is the notification of events from one or more repository. A user registers for notification of a change in a specific piece of content, a content container, or a qualification of a piece of content. The principal actor is the user who is interested in the changed content and the system that registers the event and notifies the user.

Most systems can probably handle individual update requests. Updates to containers such as folders are also probably supported. Creation of objects can potentially be registered by type or location. Direct location can probably be supported much more easily than recursively. Observation by general query and arbitrary predicate can be very difficult to implement and requires a specialized reverse query mechanism.


User Goal


  1. User � user interested in a specific content item
  2. Content System � content repository as a notification can only be placed on a specific repository (or should it � can this be aggregated? Can this be an Enterprise Service Bus function?)
  3. Messaging System � Email, Message Queue, or Instant Messaging system used to deliver notification


  1. User registers interest in content object by query and specifying the event or events to be observed. This can allow specification by ID, by path or by ad hoc query.
  2. Content System accepts notification registration
  3. Content System detects change events that matches one or more registration
  4. Content System propagates event messages to Message System
  5. Message System delivers event message to user