McDataJournal Object
    
 
Description

Manages and exposes the data of objects in a session.

Object Model




Remarks

Provides the following features:

* Exposes, organizes and relates user-interface level data for a session.
The user-level data hierarchy uses the same interface as the data stored in a database to provide a heterogeneous data access method. The user chooses the data items of opened objects to be exposed in the Journal. This data may be viewed, searched, reorganized, deleted or edited. In most cases the exposed data will be synchronized to the opened object or possibly reside in the object itself.

To summarize the Journal flow of data:
1. The object is opened with its custom mechanism to expose data and usually automation.
2. The user defines the data of interest for the Journal exposure of this object.
3. An object add-on driver called a McDataHandler is used to expose the information for the Journal.
4. The information collected by the Journal may be viewed, searched, organized and edited.
5. The Journal information may optionally be stored to a database or retained temporarily by the Journal's Database.

* Automatically provides semi-persistent behaviour for session and daily data and activities.
Historic folders automatically store the content and retains the information for a specified time period. The data may be copied to a database or file at any time. The McDataJournal uses its own database to persist the data during the timed retension.

* Provides a implemention to store data to a database.
The data structures used to expose the Journal data are the compatible with the structures used by the the McDBDatabase. The Journal has implemented a mechanism to save its content to disk based database. Issues such as multi-user database volatility, security, uncompatible destination McDBNode attribute set definitions database configuration problems and soon asynch. storing have already been addressed.

* Exposes relationships between database, file, displayed/opened objects and Journal objects.
A Journal Entry is created for each object visiblied opened object and its data hierarchy.

* Centralized data dictionary defining data types with user defined attributes.
The types attributes may be edited by the user. The dictionary will publish the definition of a database type when a node is added to a database with a non-existent type (in target database). The Journal will 'collect' type information from external databases without overwriting existing type definitions.

The dictionary provides an easy mechanism to build search criteria for a query
since it collects information about searchable attributes.

Notes
DataManager exposes the one and only McDataJournal at a time.

PROGID McAddInData.McDataJournal
ObjectFlags None

Members

Methods
AddFileLink Adds a new McDBNode to the Journal's History Folder for the contents of a File.
AddNodeLink Adds a visibly opened McDBNode to the Journal.
AddObject Adds a new McDBNode to the Journal's HistoryFolder with the contents of the supplied COM object.
CreateNode Add a link in the HistoryFolder to a McDBNode.
DatabaseToJournal Returns a Journal McDBNode for an opened Database McDBNode.
DatabaseToObject Returns a reference to the open automation object of the Journal for a opened Database McDBNode.
FileToJournal Finds a Journal McDBNode for a specified file path.
GetHistoryFolder Returns McDBNode reference to a requested history folder in the identities journal database.
GetJournalType Returns a McDBType for a given Type Name configured for the current identity.
GetQueryResultsFolder Returns McDBNode reference to a specified query history folder in the identities journal database.
IsAJournalDatabasePath Returns True when a given file path contains a journal database path.
IsHistoryFolder Returns True when the given McDBNode is a valid History Folder McDBNode.
IsJournalDatabase Returns True when the given McDBDatabase is the current identity Journal Database.
IsJournalNode Returns True when the given McDBNode is a valid Journal McDBNode.
JournalHasDatabase Determines whether a Journal McDBNode object is linked to a database object without finding the database object.
JournalToDatabase Returns the Database McDBNode associated with the specified McDBNode in the Journal.
JournalToObject Returns the Object that is associated with a Journal Historic McDBNode.
JournalValue Returns a value from a Journal Object or its related objects.
MakeQuery Performs a query and creates a query results child folder in the journal with the resultant nodes.
MakeTypeExist Creates or Returns a McDBType in a specified database.
Nodes Returns an single dimension 0 based array of Journal McDBNode references.
ObjectClipboardData Returns the clipboard data for a visible object.
ObjectClose Close and/or release an opened COM object.
ObjectGetActive Returns the Active Object for a Localized Command.
ObjectHasDatabase Determines whether a visible object is linked to a database object without finding the database object.
ObjectOpen Close and/or Release a COM object.
ObjectToDatabase Returns a reference to a Database McDBNode for a visible object.
ObjectToJournalReturns the Journal McDBNode instance representing a given COM object.
ObjectToJournalValueName Returns the Journal Attribute name for an Object and its Value Name.
ObjectUpdateJournal Find and updates the Journal Node associated with the Object.
ObjectUpdateThumbnail Updates the icons of the McDBNode returned by ObjectToJournal McDBNode and Source Database McDBNode from a live COM object.
UpdateDatabaseNode Find and updates the Database Node associated with the Journal Node.

Properties
ApplicationRead-only property The Root of the Application Object Model.
DatabaseRead-only property The McDBDatabase reference for the identities Journal database.
DatabaseNameRead-only property The logical name of the identity Journal McDBDatabase.
HistoryFolderRead-only property The McDBNode reference to current history folder in the identities journal database.
HistoryFolderAgeLimitRead-write property The limit in age of days of history folders to keep in the journal.
HistoryFolderPathRead-only property The database path to current history folder in the identities journal database.
JournalContentRead-write property Identifies the content level of the Journal objects.
JournalPathRead-only property The file-system folder path for the parent of the journal databases.
JournalTitleRead-only property The language specific name for the identities Journal database.
NameRead-only property The name for this object instance once initialized.
ParentRead-only property The Object that created this instance.
QueryResultsFolderRead-only property Returns a reference to current query history folder in the identities journal database.
QueryResultsFolderPathRead-only property The database path to current query history folder in the identities journal database.