Glossary

• Content Repos - Any CMS or Content System Impulse will connect to

• Connector - A connector is how Impulse can connect to a repository. Connectors are used with an endpoint to allow the job to perform the sync. They allow Impulse to pickup content from a repository, transform it into Motation, transform from Motation into raw data, and then sync that transformed content to the destination repository.

• Local ID - In an effort to make Impulse as efficient as possible, Impulse tries to only get content it needs. This means not getting content that Impulse already has Motation for, and not delivering content that was already delivered.

  • The Local ID is sometimes referred to as an Immutable Version ID

  • Immutable Version ID - This is a version ID for a content that will not change. Meaning, if the content changes, the version ID would return different.

    • This can be a problem with some CMSes for example in dotCMS it uses inode as it’s versionID but those inodes are mutable. So, the dotCMS Adapter will actually create its own version ID that can solve this problem. Most systems have the concept of an Immutable Version ID for Content.

• Destination - A destination is any Content Repo Impulse SENDS data to

• Endpoint - A source or destination is an endpoint. It is a Content Repo with a URL or IP. In this case, it could be a cluster of Content Repos, but to Impulse would be a single Endpoint, a single Source or Destination. It is possible to have many Impulse Endpoints (Sources and Destinations) of the same Content Repo and Version but with different URLs/IPs ie… A Prod, Auth, Testing ….

• Job - An Impulse Job is a predefined sequence. It specifies allowed Sources and Destinations and filters of what to move. When a request comes in, it will reference a predefined Job. Jobs can be manual meaning they run only when asked to be run or automatic meaning they have a trigger ie.. time or some other defined event

• Motation - A format for storing a SINGLE piece of Content with everything needed to create that Content in any Destination. Motation extends the JSON format with requirements specific to Content Repos. Motation is intended to be an agnostic format for storing Content, see docs

• Motation ID - In the future, we see the need for other IDs around Motation (IE… Structure ID, Taxonomy ID, and Path) The primary Motation ID is a checksum of the actual data.

• Source - A source is any Content Repo Impulse CONSUMES data from.

• Taxi - A microservice which is responsible for picking up and dropping off content.

• Transaction - Each Sync Process has its own Sync Transaction. It is one transaction per Sync Process. The same transaction will be used through the entire process. This transaction will be used for everything from status to auditing to helping the Sync Manager properly manage and control the Sync Sequence

• Adapter - A process to connect to Content Repositories allowing the read and write of data, these Adapters are part of what a connector is.

• Adapter Read - A part of what a source connector is, which handles the reading of data from the Content Repo.

• Adapter Write - A part of what a destination connector is, which handles the writing of data to the Content Repo.

• Transform - The idea of converting ANY content from ANY Source into an agnostic format (Motation) and later being able to transform the Motation file into Content for any Destination, this process could be both ways, Motation to Content, or Content to Motation.

• Transformer - A process which handles transforming, these transformers are part of what a connector is.

• Transformer In - A part of what a source connector is, which handles transforming from the Content Repo data to Motation.

• Transformer Out - A part of what a destination connector is, which handles transforming from Motation to the Content Repo data.