Connector

What connectors are planned for future integration?

The following systems are currently on the roadmap for future integration via TI Connectors:

  • EvidentIQ (EDC)
  • Medrio (EDC)
  • Castor (EDC)
  • Workday LMS
  • Dayforce LMS

Is re-validation required when new TI platform versions are released?

No. All connectors are built on standardized APIs and operate independently of the core TI platform. Therefore, re-validation is not required after each platform release. TI monitors upstream vendor changes and coordinates updates as needed.

Have any solutions been implemented from your own company or other vendors? What is the preferred approach to handle infrequent, batch, near real-time, and real-time (synchronous) interactions, and what typical data volumes and transaction loads do you handle?

We have integrated with many different systems through a combination of our enterprise API and our connector platform, which provides pub-sub capability to other provider APIs that TransPerfect maintains. For the enterprise API, we prefer near real-time interaction, and the API connects directly to our internal enterprise service bus (ESB) and application-level queues. Through our connector platform, we can support any preferred synchronization approach and have found that infrequent and batch approaches often suffice for most integrations using our serverless connector architecture. Typical volume depends on the customer; however, we have customers who regularly send thousands or tens of thousands of data points and documents daily.

Can TI integrate with a data lake, such as Denodo or Teradata?

Yes. Through our connector framework, we have integrated with several data lakes, including Teradata.

What services/utilities are available for bulk load and bulk export to support archival, legal discovery, and mergers, acquisitions, or divestitures?

Multiple approaches are supported. The TI reporting framework is built on denormalized domains from the platform applications, using an Extract, Transform, and Load (ETL) process that runs every hour. These domains can be exported to AWS Athena and accessed through multiple methods. We also support exporting these domains to flat files on SFTP sites, as well as a direct connection to AWS S3.

How does TI merge data elements based on metadata?

Our connector framework mirrors the endpoint API in its data model and translates data elements to the TI ESB data model using GraphQL, which supports one-to-one, one-to-many, and many-to-many relationships.

How do you abstract the solution interfaces from the data model?

We use GraphQL to support interface abstraction.