OpenText Content Server (Formerly LiveLink) has been around for a while.

A common use of DIFS is migrating content (normally documents and emails) from Content Server into SharePoint / Office 365.

Content Server stores all the meta data in a SQL Server database and all the content files on a file share(s).

Content Server has quite a complicated database schema, the document file path, categories etc, and meta data are all stored in different tables.

The secret is to create a set of SQL Queries that creates a single table that contains;

To do this nicely in SQL you can make use of;

The example below will point you in the correct direction.

https://1drv.ms/u/s!AkOe8mAm9c7Ta8ORWwfB7Ij5Kq8

Working with LiveLink you will soon get used to the idea of subtypes. Try the link below for more information

https://www.bing.com/search?q=opextext+subtype