Data Models for Collaboration and Approvals

Routes

This graphic shows the data model for routes.

People and Organizations

This graphic shows the data model for people and organizations.

This graphic shows the organization type hierarchy.

This graphic shows the skill management data model associated with people.

Issues

This graphic shows the data model for issues.

Document Management

These data models reflect document management:

Uploading/Checking In Files
File Version
Revising With Files
Revising Without Files
Deleting Files

Document Data Model

This graphic shows the data model for documents:

Uploading/Checking In Files

When a user uploads one or more files (for example, into a Book in the case of IP Classification), the system creates a Document business object and uploads files into it (that is, a root or holder object for all the files being uploaded). For each file being uploaded, it creates a Document business object with the "Is Version Object" attribute set to true and the "Title" attribute set to the name of the file. These Document objects are connected to the root Document object with the Latest Version and Active Version relationships. These relations both have a 1:N cardinality. In this graphic example, the names of the Document types are auto-generated.

File Version

To create a version of a file, a user checks out the file from the Document object by locking it, makes changes and checks it back in. Since the root Document object is not locked, other users can work on the remaining files concurrently.

When the new version is checked in, the system revises (using the core revisioning mechanism) the corresponding Document (Version) object and updates meta data like "Description" and "Title." Files in the Master are moved to the earlier version of the Document (Version) and the latest file version is checked into the Master object since the Latest Version, Active Version relationships are floated on revision at the Document (Version) end. The core handles relationship connects and disconnects.

Revising With Files

When the user chooses this option, the system revises the root Document object, clones the connected Document (Version) objects (using Active Version relationship) and connects them to the revised Document.

Revising Without Files

When the user chooses this option, the system revises the root Document object and does not bring forward (clone and connect) the Version objects.

Deleting Files

Users with proper access can delete active file versions. In this case, the system deletes the file from the Document object and moves the latest version of the file into the Document object (from previous Version object). Also, it deletes the corresponding Version object and connects the previous Document (Version) object with Latest Version and Active Version relationships.

This process can be done using a JPO trigger.