Livelink or Content Server is a proprietary offering by OT.Many of its core DMS tables are known in public sites ,however OT protects it by IP concerns.The schema is available to any customer who has a contract with OT free of charge.More than that livelink software does not react well to anybody updating schema.This is because the many relations in the DB is enforced by code or callback or event subscribers.So if you update a table without knowing all the other relation sit is almost certain that you would have put the software in a unsteady state.
As of writing this today here are a few ways you can make changes to the livelink application and its database
By developing with a standard language(C#,Java) that understands webservices
By developing with a standard language that understands LAPI(C#,Java,C,C++,VB.NET).LAPI is getting deprecated in favor of webservices
By purchasing an expensive package called WebReports.Reporting as well as changes can be instilled
By purchasing an package called ObjectImporter.Programmers provide XML instructions which are mostly low effort programming uinsg VBA,perl or any ascii editor
Ultimately almost any of the software can be enhanced /changed by the language of its IDE called Oscript.OT is coming up with a Eclipse plugin called Oclipse which will replace the IDE which we oscripters call the builder.This is also a very high debugger