Integration services systems, methods and computer program products for ECM-independent ETL tools

A system, comprising:

• a processor;
• a non-transitory computer-readable medium;
• and
• instructions stored on the non-transitory computer-readable medium and translatable by the processor for:
• responsive to a request from an application to access a repository storing objects of repository-specific types, starting up a repository-specific connector to connect the application with the repository,
• wherein the starting up comprises importing, from the repository, a definition of a repository feature of the repository as a secondary type definition for a secondary type object type,
• wherein the importing comprises making an application programming interface (API) call to the repository using a repository-specific API,
• wherein the definition is created by a user,
• wherein the repository-specific connector imports the definition created by the user, and
• wherein the secondary type definition defines properties that can be dynamically added to or removed from content management interoperability services (CMIS) objects;
• and
• sending the secondary type definition to the application such that the application, responsive to an instruction to create a document of the secondary type object type, associates the document with the properties from the secondary type definition and displays the document on a user device.

A computer program product comprising a non-transitory computer-readable medium storing instructions translatable by a processor for:

• responsive to a request from an application to access a repository storing objects of repository-specific types, starting up a repository-specific connector to connect the application with the repository,
• wherein the starting up comprises importing, from the repository, a definition of a repository feature of the repository as a secondary type definition for a secondary type object type,
• wherein the importing comprises making an application programming interface (API) call to the repository using a repository-specific API,
• wherein the definition is created by a user,
• wherein the repository-specific connector imports the definition created by the user, and
• wherein the secondary type definition defines properties that can be dynamically added to or removed from content management interoperability services (CMIS) objects;
• and
• sending the secondary type definition to the application such that the application, responsive to an instruction to create a document of the secondary type object type, associates the document with the properties from the secondary type definition and displays the document on a user device.