TopBraid Teamworks Framework
Simplest and fastest way to create data editing applications that keep an audit trail of changes
The Teamworks Framework is part of the core technology infrastructure underlying TopBraid EDG. The framework has two distinct features:
Change Management with complete audit trail and support for working copies or sand-boxed versions
Model-specific Applications – ability to associate different editing applications, reports, export, imports and other features with different model types.
Change Management with Teamworks
- The master graph that contains the actual data
- The TCH (or team) graph containing the audit trail, available working copies, user permissions and comments.
As users make changes, audit trail of changes is automatically written into TCH graph. Master graph is also changed accordingly, unless a user is using working copies. A working copy is a Teamworks feature for managing a collection of changes in a sandbox, without writing them to the master graph. All changes are stored only in the TCH graphs making the working copy a virtual construct that is computed on demand.
Teamworks Support for Graph-specific Applications
The best way to understand this feature is by examining TopBraid EDG. It is shipped with many predefined graph or asset collection types. Each asset collection type has a declared editing application as well as declared reporting, import/export and other features. For example:
- Taxonomies – these asset collections use an editing application that is optimized for using SKOS. They have unique import, export and report options such is import from MultiTes and hierarchy export.
- Ontologies – these asset collections have editing UI designed for working with schemas – classes, properties, shapes and rules
- Data Asset Collections – these asset collections are using a tabular editing application targeted to cataloging data assets. Specialized import options enable ingesting metadata from data sources.
TopBraid EDG customers can define their own custom types of asset collections. Internally, they are called “EDG project types”. For example, a new collection type may be focused on capturing information about a decomposition of engineering assets or about business process flows.
When a new type of collection is created, it will show up as a new link in the EDG navigation bar – on the same level as asset collection types shipped with EDG such as Taxonomies, Ontologies and Data Assets. With the new type established, users can define an edit application specific to the new type and specify other type-specific options such as imports or data transformations. All these definitions are made declaratively as part of the knowledge graph.
Ready to get started?
Get in touch today to learn how to improve semantic data governance for your enterprise.